Tampa · Working worldwide

Production builds

From $135,000

Medium profile

From $260,000

Before production

Approved Build Definition

Scope and rights

Set by your signed agreement

Build scope and handover

Know what your build includes before you commit.

When you commission a product, you need a clear account of what will be built, how it will be accepted and what you will receive. Here is how Turwin defines that work, who is accountable for it and what the handover includes.

See the build deliverables

Stage

Input

A signed Build Definition

Output

Seven deliverables

Condition

Medium profile from $260,000

What the fee covers

Seven deliverables, defined around your product.

A standard production build takes the agreed product from its written definition through application development, testing, deployment and handover. For a medium-profile product, the starting investment is $260,000. The signed scope records the product definition, delivery window, acceptance conditions and client rights before production begins.

See all starting-price bands

What we build · 7 deliverables

D01
Product definition
The buyer, the job the product will do, its boundaries, the commercial offer and the written conditions for acceptance.
D02
Working application
The interface and product workflow for the people who will use it, built to the agreed scope.
D03
AI system
The models, data, memory and integrations required by the signed product scope.
D04
Operating controls
Permissions, review points, logging, safeguards and failure handling for the agreed use.
D05
Test record
Functional tests and an evaluation record tied to the product's written acceptance conditions.
D06
Production deployment
A live cloud environment with monitoring, recovery instructions and launch support.
D07
Owner handover
The codebase, operating documents, runbooks and ownership rights stated in the agreement.

One build · two outcomes

What you keep · owner handover · solid line

H01
Codebase
The source repository and the instructions needed to build and release the product.
Transfers
H02
Live product
The deployed application and its agreed cloud configuration.
Transfers
H03
System record
The data contracts, integrations, permissions and operating boundaries.
Transfers
H04
Acceptance record
The tests and evaluations used to confirm delivery against the signed scope.
Transfers
H05
Runbooks
The instructions for monitoring, recovery, releases and routine operation.
Transfers
H06
Rights schedule
The ownership and license terms agreed for the client product and its dependencies.
Transfers

Turwin's private production methods remain with Turwin. Your agreement defines the product, materials and rights included in the handover.

Turwin responsibility

Named delivery principal

Delivery record

Signed by Turwin

Client acceptance

Named client approver

Controlling document

Signed agreement

Accountability

A named Turwin principal is accountable for your build.

Your Turwin delivery principal approves the scope, maintains the client record and signs the delivery record. Specialists may contribute to the work; delivery accountability stays with Turwin.

Named accountability does not replace the signed agreement. The agreement controls scope, price, timing, acceptance and rights.

Stage

Input

Your options

Output

A deliberate route

Condition

Responsibilities made explicit

Your options

Choose a build route that fits the company you want to run.

A permanent team, an MVP studio, a technical cofounder and a commissioned production build involve different responsibilities and commitments. Use these questions to make the choice explicit before you commit.

RoutePublic cost or commitmentBest fitQuestion to settle

Hire an internal team

Ongoing salaries, hiring and managementProduct and operating costs continue alongside the team.

Best fitYou want a permanent product function and have continuing work for the team after launch.

Question to settleWho will recruit, direct and retain the team?

Commission an MVP studio

A defined early-version projectScope and handover are set by the provider's agreement.

Best fitYou need a narrow first release to learn from before committing to a broader build.

Question to settleWhich tests, production controls, operating documents and ownership rights are included?

Find a technical cofounder

Shared ownership and company riskThis route includes an ongoing leadership role.

Best fitYou want a long-term partner to help lead the company and its technology.

Question to settleWhat responsibilities, control and ownership should that person share?

Commission Turwin

From $135,000Medium-profile builds start at $260,000; the written scope controls the final fee.

Best fitYou have a named buyer and want an agreed production scope, delivery accountability and owner handover.

Question to settleDoes the business case justify funding this product, and who will operate it after handover?

Stage

Input

An assessed idea or funded brief

Output

A production proposal

Condition

About 35% to begin after signature

How commissioning begins

The commitment is defined before production starts.

You can begin with the $99 idea diagnostic. If its recommendation supports a build, Turwin can prepare a production proposal. You can also bring an existing funded brief if you have authority to commission the work. After signature, the first invoice is the “to begin” amount shown on the opportunity: about 35% of the production price, rounded up to the next $5,000. This payment is part of the production price and covers the signed Build Definition and mobilization. Production begins only after the Build Definition is approved.

01Written product and commercial scope
02Acceptance conditions and delivery boundaries
03Production price, timing and rights

Assess my idea · $99