Senior TypeScript/Next.js Team for AI-Powered PWA | December 2026 Launch

@bcosley

Hi, You're looking for a production-ready, mobile-first PWA with a guided flow, payments, AI integration, and a clean takeover of an inherited TS/Node monorepo for December 2026. We’ve delivered similar PWAs with guarded data, passwordless auth, and real-time validation in other projects, with careful handover to production teams. Execution approach: I'd start by validating the existing flow, reproducing critical paths, and mapping the evidence to a concrete takeover plan, then begin the M0 close-out with tight milestones and risk register. One technical risk: The AI integration must not recalculate deterministic engine outputs; I’ll enforce strict boundaries and validation. Two clarification questions: - What are the exact acceptance criteria for the takeover audit and M0 close-out? - What level of access and handover evidence will you require for the repository and test data during NDA? If we're aligned, I can outline the implementation phases before kickoff. Best regards, Brandon

@installerpoint

Hello, your inherited consumer-insights platform requires a disciplined takeover audit before committing to December production. I would begin by reproducing test evidence, reviewing the TypeScript/Node.js monorepo, deterministic calculation boundaries, PostgreSQL persistence, security posture, deployment readiness, and missing dependencies. I would then provide a costed plan covering M0 and each subsequent milestone, with explicit assumptions, acceptance criteria, and launch risks. The proposal should be finalized after NDA review so live-product references, named team roles, availability, exact contributions, and indicative milestone costs are accurate rather than overstated. A key improvement would be contract tests ensuring AI reporting can never alter calculated facts. I will personally own architecture and delivery governance. Check out my portfolio here:- https://www.freelancer.com/u/installerpoint Best Regards, Muhammad Adeel

@mayr81

Your project is a substantial production takeover, and the staged approach you describe is the right way to protect the December 2026 launch. We would begin with an evidence-led 1-2 week audit: reproduce the monorepo’s tests and deterministic outputs, inspect architecture and deployment configuration, trace PostgreSQL data ownership, review security and consent handling, and validate the assumptions behind image analysis, AI grounding, payments, localization, and PWA behavior. The result would be a costed takeover plan with explicit dependencies, acceptance criteria, and risks, not an assumption that the later milestones are already complete. Our delivery plan would separate takeover audit, M0 close-out, then five measurable milestones covering the guided PWA flow, accounts and entitlements, Airwallex payments, grounded AI/reporting, localization, production hardening, observability, testing, documentation, and handover. A named senior technical lead would personally own architecture, technical decisions, and delivery coordination from October through December, supported by frontend, backend, QA, and DevOps capacity. We would provide two live-product case studies with exact contributions, current production status, team availability, and an indicative milestone-by-milestone cost after reviewing the specification and repository under NDA. We would also raise schedule risks immediately, especially scope completeness, third-party integration readiness, image-analysis quality,

@CorporateRD

Good Day!! We are open to signing an NDA to review and dicuss the detailed specification, guided-flow designs, handover evidence and repository information in detail. Based on your requirements, I understand that you're looking to take an existing consumer-insights platform, independently verify the inherited calculation engine, and turn it into a production-ready mobile-first PWA. The scope includes real image analysis, grounded AI reporting, passwordless accounts, payments/subscriptions, localization, privacy, monitoring, and a polished guided user journey. - What percentage of the existing frontend, backend services, database schema, and calculation engine is currently production-ready versus test-only? - Which image-analysis provider/model and AI reporting approach are currently planned, and are the required API accounts/data-processing agreements already available? My approach would begin with a 1–2 week technical takeover audit to review the architecture, validate calculations, reproduce test evidence, identify gaps, and produce a costed M0 close-out plan. From there, I’d deliver the frontend, AI/image integrations, Airwallex payments, localization, security, QA, infrastructure, and production handover through clear milestones, while keeping the deterministic engine as the single source of truth. Let's connect for a brief chat or call to discuss your project in detail. **Budget and Duration are placeholders. Kind Regards, Royal Design M.S

@mughiraaa

Hello, I have already completed similar production web applications, PWAs, AI integrations, payment systems, and Node.js platforms, with strong experience in web development, APIs, and scalable software solutions. I can take over the TypeScript and Node.js monorepo, verify the calculation engine and PostgreSQL layer, then handle the PWA, image analysis, grounded AI reporting, Airwallex payments, accounts, localization, security, testing, and production deployment. How much of the inherited repository and test evidence can be shared during the initial audit so I can verify the current foundation before planning the remaining milestones? I can quickly understand the existing system, identify the key risks, and deliver exactly what is needed. Happy to discuss the takeover and delivery approach in a quick meeting. I will share my portfolio in chat I look forward to hear from you. Thanks Best Regards, Mughira

@manh2906

Hi - I am Manh. "SEO-FRIENDLY MULTI-SERVICE WEBSITE + AI BOOKING" - you need one website where customers choose a service, enter the right job details, and have that information captured and delivered to your scheduling workflow. I would build the landing page around the three current service paths, with a flexible structure so new services and variables can be added later without rebuilding the site. Each path would collect the required customer and booking information, validate the fields, store the submission, generate the required Word document, and send the details by email. For SEO, I would build clean page structure, URLs, headings, metadata, internal linking, schema where appropriate, image optimization, sitemap, and technical foundations that can support future content and backlink campaigns. I would keep the site fast and mobile-friendly rather than adding unnecessary plugins. For the AI option, I would use a controlled booking assistant that collects defined information and writes structured data to the database, with clear fallback to a normal form when the AI cannot confidently handle a request. What are the three service categories and the exact information each one needs to collect? Looking forward to working with you.

@ZenDevelop

Your December launch depends less on adding features quickly and more on proving what you inherited before the new team builds on top of it. I would make the first 1–2 weeks a hard verification gate. I’d reproduce the current tests from a clean environment, trace the deterministic engine against versioned JSON and PostgreSQL output, inspect architecture and deployment assumptions, then return a risk register, dependency map and costed M0–M5 plan. The architectural call I’d keep firm is yours: calculated facts come only from the deterministic engine. Image analysis and AI can explain or structure those facts, but never silently recalculate them. The immediate risks I’d raise are Airwallex entitlement flows, image-analysis accuracy, AI grounding, launch-market localization/currency rules, inherited test coverage and December acceptance time. Indicative delivery: - Audit: 1–2 weeks, $1,000 - M0 close-out: $1,200 - M1–M5: $1,260 each, through December Before you spend the later milestone budget, the audit gives you reproduced evidence and a go/no-go plan. After NDA access, is M0 allowed to change the scope or sequencing of M1–M5 if the inherited evidence does not reproduce? Best, Ryan.

@Visharaa2024

Hi, I can take over the existing Node.js monorepo and lead the platform through audit, M0 close-out, product development, testing, and production launch. Our approach would start with a 1–2 week technical audit: review the monorepo architecture, reproduce existing tests and calculation outputs, inspect PostgreSQL/data models, verify the deterministic engine, identify gaps/dependencies, and produce a clear costed takeover plan before committing to the later milestones. For the product build, we can work with React, TypeScript, Node.js, PostgreSQL, PWA, Airwallex, and grounded AI integrations. The deterministic engine will remain the source of truth, with AI restricted to interpreting verified outputs. We’ll also cover password less authentication, purchases/subscriptions, localization, privacy/consent, security, monitoring, automated testing and production deployment. A few questions before we scope accurately: Can you share the current repository/test evidence after NDA? How many senior developers are currently available on your side for knowledge transfer? Is the Airwallex account and payment flow already configured? Which AI/image-analysis providers are currently planned? Do you already have the detailed milestone specifications and acceptance criteria? After reviewing the inherited code, I can provide a realistic takeover cost, M0 estimate, five-milestone timeline, dependencies and December launch risks rather than making assumptions. Best Regards, VD Infotech

@drishinfotech

We’ve carefully reviewed your requirements and fully ✅ understand this is a production takeover not an MVPand that the first priority is independently validating the inherited TypeScript/Node.js foundation before committing to December. Our team has 15+ years of experience delivering web, mobile, PWA, payment, API and AI-enabled platforms. Relevant Experience • The Rave: Android/iOS/PWA event-ticketing platform with global third-party integrations. • TIFAC: Android + web diagnostics platform integrating computer-vision AI with backend services and devices. The capabilities document does not provide verified public URLs or individual contribution details, so we won’t fabricate them; these can be shared where permitted after NDA. Takeover & Delivery ⚡ Week 1–2: Audit architecture, dependencies, database, tests and deterministic outputs. ⚡ Reproduce evidence, review security, consent, image handling and deployment. ⚡ Deliver a risk/gap report and costed implementation plan. Then: M1 PWA + guided flow → M2 accounts/payments → M3 image analysis + grounded AI → M4 localization/subscriptions → M5 QA, security, deployment & handover. Indicatively: 2-week takeover + 8–10 weeks product delivery, subject to repository quality, Airwallex, AI providers, designs and launch scope. Estimated $8,000–$10,000, refined after M0. A senior technical lead will own architecture, reviews and delivery throughout.

@najamulilsam

Hey, I understand you need a senior team to take over and independently validate an existing TypeScript/Node.js consumer-insights platform, then turn it into a production-ready, mobile-first PWA with AI reporting, payments, localization, privacy controls, and a December 2026 launch. We’d begin with a structured 1–2 week technical takeover audit covering the monorepo, deterministic engine, PostgreSQL schema, tests, architecture, security, deployment readiness, and inherited evidence, followed by a costed remediation/M0 plan. Questions: For the image-analysis component, has the client already selected a provider/model, or are we expected to evaluate and recommend the production solution? For Airwallex, are the merchant account, payment flows, subscription products, and launch-country requirements already configured, or would these need to be established during delivery? What are the five defined product/launch milestones and their acceptance criteria in the detailed specification? I would love to schedule a meeting or have a detailed conversation about the project to clarify some concerns about the project, this way I can demonstrate my capabilities perfectly and suggest the best result possible. Kind Regards, Najam Budget and Duration are TBD