What if our AI integration needs change because the model space moves?

The SOW pins implementation to a model and provider that meet acceptance criteria. If the client wants to migrate mid-build, written change order. If the chosen model fails acceptance criteria, migration is on the studio at no cost.

QuantaLynk / Services / Build engagement

Service 02 · Fixed scope

Build engagement.

Fixed scope, fixed price engineering. The studio takes ownership of a defined deliverable end to end. From the SOW through production handoff and a 30 day stabilization window. Two engagement shapes inside one umbrella, both priced before work starts. Agencies can also buy white-label sites at $1,500 each.

Engagement shapeFixed scope, fixed price

AI feature buildFrom $3,000

Full buildFixed price after scoping

Duration1 to 12 weeks

Payment50/50 under $5,000; 50/30/20 above

Capacity2 builds in flight at any time

Two shapes.

AI feature build.

From $3,000 · 1 to 4 weeks

Drop a working AI feature into an existing product. Common patterns: retrieval over your own documents, agentic workflows for an ops team, evaluation harness on a shipped feature, model migration off a vendor lock.

Full build.

Fixed price after scoping · 4 to 12 weeks

Greenfield product, platform modernization, or a feature your team has been blocked on for two quarters. Architecture, implementation, deployment, observability. Production ready handoff with documentation and runbooks.

What is included.

A free 30 minute call, then a written technical spec, milestone list, and one fixed price both sides sign. Larger builds get a paid scoping week, credited to the build.
Implementation through the milestones. Weekly written status, working software at each milestone.
Milestone payments: 50% at start and 50% on delivery under $5,000; 50% at SOW, 30% at production deploy and 20% after stabilization above that. The final payment waits for acceptance in production.
Production handoff: source repo, deployment configuration, environment variables documentation, runbooks for the operations the team will own.
30 day stabilization window after handoff. Bug fixes within the original scope at no additional cost.
Optional: 90 day support retainer after stabilization, priced separately.

What is not included.

Open ended scope creep. Changes after the SOW go through a written change order with a price delta.
Ongoing operations after the stabilization window. The team owns what was handed over.
Native iOS or Android apps as a primary deliverable. The studio ships web and React Native; bespoke native is referred out.
On-prem hardware deployments, embedded firmware, or anything outside a cloud or hybrid cloud target.

How a build runs.

01 · Scoping

SOW + price

A free 30 minute call, then a written spec, milestones, acceptance criteria, and a fixed price. Larger builds get a paid scoping week, credited to the build. If we cannot agree, the engagement ends here cleanly.

02 · Build through milestones

Working software each week

Milestones are anchored to working software, not to time spent. Weekly written status. Working demo at each milestone gate.

03 · Production handoff

Final milestone + final payment

Acceptance criteria checked in production. Repo, configuration, runbooks, and documentation handed over. Final payment released after the stabilization window.

04 · Stabilization

30 day window

Bug fixes within the original scope at no extra cost for 30 days after handoff. After that, support is a separate, optional retainer.

Common questions.

Why a fixed price instead of time and materials?

Fixed price puts the studio on the hook for delivery, not hours. Both sides agree the price before work starts, and the final payment waits for acceptance in production, which keeps the studio honest on the handoff. Time and materials creates incentive to drag; fixed price creates incentive to ship.

What happens if the scope changes mid-engagement?

Written change order. Spec gets updated, the price delta and timeline impact are agreed in writing, and work continues. Small adjustments inside the original spec are absorbed; meaningful new scope is priced.

What if we miss a milestone?

If the studio misses a milestone, a remediation plan is shared inside the milestone week and the timeline shifts at no cost to the client. If the client is the blocker (delayed approvals, missing access, blocking dependencies), the timeline shifts for that side.

Can we extend a build into ongoing development?

Yes. Common path is build engagement followed by a 90 day support retainer or a Fractional CTO retainer for the technical leadership seat. Both are priced separately.

Do you sign NDAs and DPAs?

Standard NDA: signed before scoping. DPA where personal data of EU residents is in scope: signed before the SOW. Both are templates the studio operates from; light redlines are routine, heavy redlines move to the lawyer's track.

What if our AI integration needs change mid-build because the model space moves?

The SOW pins the implementation to a model and provider that meet the acceptance criteria. If the model space shifts mid-build and the client wants to migrate, that is a written change order. If the chosen model fails to meet acceptance criteria, the migration is on the studio at no cost.

Have a build that needs shipping?

Send a paragraph about the system, the deadline, and the constraints. The first call is 30 minutes and free. Within a week of that call you have a written spec and a fixed price.

Book a 30 minute call →