Pricing in public

Two engagement shapes. Public prices. No hidden tiers.

QuantaLynk publishes its prices because a quote form sorts buyers by patience, not by fit. Below is what every engagement starts at. Scope inside a shape moves the price within its band. A different scope moves to a different shape.

Effective 4 May 2026  ·  Reviewed quarterly
€8K
Fractional CTO floor /mo
€25K
AI integration build floor
€60K
Hard cap, every build
3 to 4
Engagements per quarter
€0€15K€30K€45K€60K+
Fractional CTO retainerPer month
€8K /mo
4 week pilotOne-off, before retainer
€10K
AI integrationFixed scope, 4 to 8 weeks
€25K to 55K
Full buildFixed scope, 6 to 12 weeks
€30K to 60K
Effective May 2026. Bands reviewed quarterly. Engagements signed at one price are honored at that price for the SOW duration. Below the floor or above the cap, the studio refers out with names.
01 Retainer

Fractional CTO retainer.

Senior technical leadership for founders or heads of engineering who do not need a full time CTO. Architecture, hiring, scaling, vendor selection, board prep.

Retainer

From €8K per month
6 month minimum after pilot · 4 week pilot from €10K · 2 retainers held at any time

What is included

  • Weekly 1:1 with the founder, 60 to 90 minutes
  • Monthly architecture and roadmap review, written
  • Hiring support: JDs, screens, panel interviews
  • Investor and board prep on the technical narrative
  • Vendor and tooling evaluations
  • One on-site or co-located week per quarter, expenses at cost

What is not included

  • Heads-down code authorship (use Build engagement)
  • Line management of engineers
  • Always-on availability
  • Implementation of recommendations (the team executes)
Read the full retainer detail →
02 Fixed scope

Build engagement.

Fixed scope, fixed price engineering. Two shapes share one umbrella, both priced before work starts.

AI integration.

From €25K
4 to 8 weeks · Fixed scope at SOW · 20% milestone holdback

What is included

  • Scoping week, written spec, fixed price
  • RAG, agentic workflow, evaluation harness, or model migration
  • Production handoff with documentation and runbooks
  • 30 day stabilization window after handoff at no extra cost
  • Cost controls and failure path engineering

What is not included

  • Open ended scope creep (written change orders required)
  • Ongoing operations after stabilization (separate retainer)
  • Native iOS / Android as primary deliverable
  • On-prem hardware deployments
Read the full build detail →

Full build.

From €30K, capped €60K
6 to 12 weeks · Greenfield, modernization, or unblocking work · 20% milestone holdback

What is included

  • Scoping week, written spec, fixed price
  • End to end implementation through milestones
  • Working software at each milestone gate
  • Production handoff with documentation and runbooks
  • 30 day stabilization window after handoff at no extra cost

What is not included

  • Twelve plus week scopes (refer to peer studio)
  • Native mobile as primary deliverable
  • Ongoing operations after stabilization
  • Pre-product founder discovery (different shape)
Read the full build detail →
03 Operating principles

How the prices hold.

Five operating principles keep the published prices honest across engagements.

Three to four engagements per quarter, hard cap.

Across both shapes combined. The throttle stays on even when the calendar is empty. Above the cap, the studio refers out with names, not a waitlist.

20% milestone holdback at the final acceptance gate.

Released only after the agreed acceptance criteria are met in production, not in staging. Eliminates the "demo works, production does not" failure mode.

Fixed scope, written change orders.

Scope is locked at the SOW. Material new scope is priced as a written change order with a price delta and timeline impact agreed before work resumes.

Below the floor, refer out with names.

If the budget does not fit a QuantaLynk engagement, the studio names peer studios at lower price points it trusts to take the work. A bad fit for the studio does not have to be a dead end for the buyer.

Above the cap, refer out too.

Projects requiring more than €60K of senior engineering need an org chart, which is not the studio's shape. The studio refers projects above the cap to peers who can staff them.

Public price, quarterly review.

Prices on this page are reviewed every quarter and dated at the top. Engagements signed at one price are honored at that price for the duration of the SOW, regardless of subsequent changes.

04 Common questions

On publishing prices.

Why publish pricing instead of using a quote form?

A quote form sorts buyers by patience, not by fit. A public price sorts by both. The studio loses time on calls with buyers whose budget does not match the engagement shape. Public pricing solves that for both sides.

Are these prices negotiable?

The starting point is fixed. The scope is negotiable inside the price band. A larger scope inside the same shape moves the price within its band. A different scope moves to a different shape. The studio does not run a "if you sign this week, we can do 20% off" pattern.

Why is the build engagement capped at €60K?

The cap is the point above which a senior solo + AI delivery shape stops compounding. A project that needs more than €60K of senior engineering also needs an org chart, which is not the studio's shape. Above the cap, the studio refers projects to peer studios who can staff them.

Do you discount for non-profits or early-stage founders?

Not on the list price. The studio occasionally takes on a fourth quarterly engagement at reduced scope and reduced price for a specific class of work. This is decided case by case and is not advertised.

What if our budget is below the floor?

The studio refers out with names. There is a network of peer studios at lower price points that the studio trusts. A bad fit for the studio does not have to be a dead end for the buyer.

What if our timeline is shorter than the engagement window?

Same answer as above. The studio does not compress fixed-scope work below its honest delivery window because rushed scope is the most common cause of post-handoff regret on the buyer side.

Have an engagement that fits.

Send a paragraph about the system, the deadline, and the constraints. The first call is 30 minutes. Reply within one business day during EU hours.

Start a project →