Pricing

Clear scope first. Then a fixed quote.

A bounded diagnosis, a scoped build, or ongoing engineering leadership. Written scope, exclusions, milestones, and a fixed quote before work begins. The default first step is the Build Readiness Audit.

Send project detailsSee all plans

After kickoff, any change is written up with its price and its effect on the date. Nothing starts until you approve it in writing.

Every fixed-scope build lane, one price each

The default build once scope is defined

Fixed price, one surface, four weeks. The default build lane for defined scope.

A fixed-price, 4-week build of one production surface: scope lock, implementation, QA, deployment, and handoff.

Read Launch Build details

4 weeks

One production surface.

What it hands over

  • Rescue Sprint scope discipline, extended across the full build
  • Full-stack TypeScript build (Next.js + React)
  • Auth and payment flows for one surface
  • Production AI integration where scoped
  • CI/CD, monitoring, and error tracking setup
  • 30-day post-launch support included

3 decisions covering 5 plans, one accountable owner

The other two shapes, and what sits inside Ship.

The presentation is simple because the scoping work is not. Choose the decision you need now, then inspect the exact delivery lanes inside it.

01

Diagnose

1 week

100% of the fee credited toward Launch Build or Product Build if signed within 60 days

Get the decision right before committing build budget.

A bounded technical audit for teams that need architecture, risk, and sequencing clarity before choosing a delivery lane.

  • A ranked list of what to fix first
  • Plain notes on the big technical choices
  • Written next-lane recommendation
Build Readiness AuditClarity, credited toward the buildRead Build Readiness Audit details See a sample report
02

Ship

2 to 8 weeks after scope lock

This is a planning range across three fixed delivery lanes. The written scope selects one fixed fee before work begins.

Scope the smallest build that can reach production responsibly.

One blocked workflow, one production surface, or multiple connected surfaces. The route changes with the system, not with a sales target.

  • Acceptance criteria before implementation
  • Weekly proof of shipped work
  • Deployment and handoff documentation
Rescue SprintUnblock one workflow fastRead Rescue Sprint details
Launch BuildOne surface, fixed priceRead Launch Build details
Product BuildMulti-surfaceRead Product Build details
03

Continue

$12,000 / month3-month minimum

Monthly capacity, decision rights, and response expectations are written into the retainer scope before kickoff.

Keep senior engineering judgment after the build.

Ongoing architecture, roadmap, hiring, and execution support for prior ThynkQ clients or teams introduced through a warm referral.

  • Weekly decision cadence
  • Architecture and code-quality oversight
  • Defined monthly capacity and boundaries
Engineering RetainerGated accessRead Engineering Retainer details

How the quote is formed

The number follows the delivery risk.

These are planning prices, not a menu designed to push buyers upward. Unusual integration scope is quoted after a free scoping call.

  • Number of product surfaces and connected workflows
  • Existing architecture and rebuild depth
  • Authentication, billing, integrations, and data migration
  • Security, privacy, and compliance requirements
  • Deadline, launch risk, and approval path

Ongoing, not a build

A live product needs upkeep, not another quote.

Requests are worked one at a time, in the order received. A request is one defect fix, one small improvement, or one dependency and security patch batch, and each targets a 72-hour turnaround from the day work starts.

Start ThynkQ Care · $490/moSee ThynkQ Care plans and one-off fixes

$490

per month, 72 hours target turnaround.

How a request works

  • One request in progress at a time. A second issue found along the way is queued, never smuggled in.
  • Unused turnaround time does not roll over; it is capacity, not credits.
  • The 72-hour turnaround is a target, not a guarantee, and sits inside the studio's two-engagement capacity.
  • Month to month, with no minimum term.
  • If a request cannot be fixed, that cycle is refunded in full.

Specialist review

MCP Risk Review: 48 hours from access, $3,000

A bounded decision for teams connecting tool servers to sensitive AI workflows and needing a clear go, fix, or escalate recommendation.

Findings that need fixing move into a scoped $15,000 remediation engagement (2 weeks, priced on the existing Rescue Sprint shape), never an open-ended follow-on.

$3,000

48 hours from access

Review MCP risk

For people who want the full comparison

A fixed fee only works when the edges stay visible.

Open a lane to see its included artifacts, exclusions, and responsible next step.

Build Readiness Audit1 week

Choose this when scope or architecture is unclear and you need risk visibility before committing build budget.

Included

  • A ranked list: what is broken, what it costs to fix, and in what order
  • Plain notes on the big technical choices, with the options we weighed
  • Security and performance problems found, with what to fix first
  • A short summary you can share with partners or investors

Outside this lane

  • Implementation work, this audit diagnoses and sequences it
  • Multi-week delivery or production deployment
  • A stand-in for Launch Build or Product Build when launch is already urgent

Next step: Move to Launch Build or Product Build once scope is clear

Read Build Readiness Audit details
Rescue Sprint2 weeks

Choose this when one workflow is the blocker and speed matters more than a rebuild.

Included

  • Scoped outcome and acceptance criteria
  • Implemented workflow or integration
  • QA proof and responsive checks where UI is involved
  • Deployment or launch-readiness notes

Outside this lane

  • A new platform, rebuild, or multi-surface launch
  • Open-ended discovery on scope too unclear to fit two weeks
  • Ongoing leadership after the workflow ships

Next step: Move to Launch Build or Product Build if scope expands beyond one workflow

Read Rescue Sprint details
Launch Build4 weeks

Choose this when one production surface is defined and you need it live this quarter.

Included

  • Written scope with acceptance criteria by milestone
  • Weekly proof updates with shipped deltas and next decisions
  • Production deployment checklist and launch report
  • Handoff docs covering architecture, operations, and support path

Outside this lane

  • Multiple connected surfaces, that is Product Build
  • One-off blocker fixes, that is Rescue Sprint
  • Discovery for teams still deciding whether to build

Next step: Move to Product Build if scope grows to multiple surfaces

Read Launch Build details
Product Build8 weeks

Choose this when scope spans more than one connected surface or workflow.

Included

  • Written scope with acceptance criteria by milestone
  • Weekly proof updates with shipped deltas and next decisions
  • Production deployment checklist and launch report
  • Handoff docs covering architecture, operations, and support path

Outside this lane

  • One-off blocker fixes, that is Rescue Sprint
  • A single defined surface, that is Launch Build
  • Open-ended monthly advisory with no near-term launch target

Next step: Continue with the Engineering Retainer for ongoing leadership

Read Product Build details
Engineering Retainer3-month minimum

Available only after a completed ThynkQ build or a warm referral, not as a cold booking.

Included

  • Decision support on architecture, roadmap, and trade-offs
  • Code quality and system health oversight
  • Hiring loops, technical calibration, and team-structure guidance
  • Monthly leadership continuity and execution risk reduction

Outside this lane

  • Cold self-serve booking
  • A replacement for a one-time launch build
  • A single urgent workflow fix, that is Rescue Sprint

Next step: Available after a completed build or a warm referral

Read Engineering Retainer details

What fixed means

  • The written scope selects one fixed fee, agreed in writing before work begins.
  • The written scope sets what the fee covers. Anything outside it is quoted, never smuggled in. Any change after kickoff is written up with its price and its effect on the date, and nothing starts until you approve it in writing.
  • The deposit is fully refundable if you cancel before kickoff begins. Once kickoff begins, the deposit is non-refundable. No work starts before the deposit clears.
How stopping early works

Before you decide

Questions buyers ask before the first call.

How do I choose the right engagement?

Start with the Build Readiness Audit if scope is unclear. Use Rescue Sprint for one blocked workflow. Choose Launch Build for one production surface in 4 weeks, or Product Build for multiple connected surfaces in 8 weeks. The Engineering Retainer opens after a completed build or a warm referral.

When is Launch Build the default?

If your core workflow is defined and you need one production surface live this quarter, Launch Build is the default fixed-price lane. Multi-surface scope moves into Product Build.

What does a first production build cost, and which lane fits?

Fixed-scope build engagements run $7,500 to $60,000. Most teams start with the Build Readiness Audit ($7,500) for clarity first, or Launch Build ($30,000) for one production surface. Product Build ($60,000) covers multiple connected surfaces. The MCP Risk Review is a separate $3,000 lane, with a written decision 48 hours from access.

What can Rescue Sprint fix in 2 weeks?

Rescue Sprint focuses on one blocked or broken workflow: an AI integration, dashboard, onboarding flow, payment path, or internal automation. If more than one workflow is in scope, move to Launch Build or Product Build.

How does payment work?

50/50 on everything up to $59,999. Three milestones (40/30/30) on $60,000+ engagements. The deposit is fully refundable if you cancel before kickoff begins, and non-refundable once kickoff begins. No work starts before the deposit clears.

How do I get access to the Engineering Retainer?

The Engineering Retainer opens after a completed ThynkQ build or a warm referral. It is not a cold booking, and it is not listed as a self-serve option in the public pricing flow.

How do you prevent scope drift during builds?

Every engagement runs on milestone boundaries, weekly proof updates, and written acceptance criteria. Any change after kickoff is written up with its price and its effect on the date, and nothing starts until you approve it in writing.

Do I work directly with Rodolf?

Yes. You work directly with Rodolf from scoping through handoff. No relay chain and no hidden junior substitution.

What happens after launch?

Launch Build and Product Build both include 30 days of post-launch support. After that, you can continue with the Engineering Retainer or run ad-hoc support as needed.

The responsible next step

Send the system, the constraint, and the timing.

The reply will name the smallest responsible engagement or say directly if the work is not a fit.

Send project detailsBook a free callrodolf@thynkq.com

Payment terms

  • 50/50 on everything up to $59,999.
  • Three milestones on $60,000+ engagements: 40/30/30.