01
First plan
Write done
Who buys, what they do, what operations must run, and what is out. Priced and dated. You edit it before you sign.
Greenfield
A product your customers can buy. Under your name.
We have built dozens of our own products this way. One principal, a swarm of agents, and a written definition of done before anyone designs a screen. Now we build yours.
Why new products arrive late and half-run.
Because a project team was hired to build features, and nobody was hired to finish a product.
Done
What done means stays unclear until the week of launch. Then it is whatever is ready.
Ownership
A team reports status. No one owns whether a customer can pay and support can answer.
Operations
You inherit a codebase with no runbooks, no tests, and a vendor you now cannot leave.
While it runs
What you can see at any point.
Where it lives
Your cloud. Your repository.
- 01 Application Web, mobile, and reports run in your accounts.
- 02 Repository The first commit is already yours.
- 03 Hosting We never host it. There is nothing to unwind when we leave.
The work
How it runs, in order.
02
Contracts
Connections first
Identity, billing, data, and partners are built and tested before screens multiply.
03
Parallel build
The swarm builds it
Product, data, tests, and documentation move together. The principal reviews every piece against done.
04
Launch
Accept and hand over
Security, performance, support, and owners are in place. Your team runs it. We stay reachable for the agreed period.
01
Done
Launch is an acceptance, not a date on a slide.
Customers can buy. Your team can operate it. Security and performance have passed. That is the definition of done, written before the first screen.
Acceptance
What is in your repository before you sign
- 01 Tests Written with the code. Running in your pipeline.
- 02 Runbooks How to operate it. Who to call. How to roll back.
- 03 Risks Every open item has an owner. Nothing is discovered later.
02
Yours
UNIT01 is not on the product.
Your name, your customers, your market, your repository. We build it the way we build our own, and we hand it over completely.
Yours
Nothing we built stays ours
- 01 Code In your accounts from the first commit.
- 02 Brand Your name. Your customers. Your market.
- 03 Access Our keys are removed when you accept. No leftover claim.
03
The week
Every week ends in evidence or a stop.
What shipped, what failed, and what is blocked. You leave Friday with a decision and the proof behind it. Not a demo.
One week
What a week produces
- 01 Monday Scope for the week is fixed. Everything else is out.
- 02 Midweek Failed checks are visible the hour they fail.
- 03 Friday Release, pause, or stop. Written, with the evidence.
In the first plan
What is written before work starts.
The first plan names each of these. It is a document you can accept, edit, or decline.
Done
Written definition of done
In the first plan. The swarm does not scale build until it is agreed.
Principal
One named person
The engineer in charge is named in the contract. You meet them before you sign.
Launch
Launch checks
Security, performance, support, and owners. Written before launch. Passed before acceptance.
Brand
Product stays with you
Brand, customers, and code are yours. Assigned in the contract.
Files
In your repository
Code, tests, runbooks, and open risks. There before acceptance.
After
Warranty on agreed work
A warranty period after acceptance. The principal stays reachable. Written in the contract.
Questions we get asked
Common questions.
01
How is this different from hiring a dev shop?
A dev shop sells you a team and bills hours. We sell a finished product at a fixed price, built by one principal and a swarm. You never manage the people.
02
Do you take equity?
No. This is not a venture studio. You stay the product company.
03
Will it look like UNIT01?
No. Your name, your customers, your market.
04
Can you start without a specification?
We start by writing what done means, in your words. You edit it. That is the first plan.
05
Do you stay after launch?
For the agreed warranty period, yes. Your operations team owns the live system. The principal answers.
06
What stack do you use?
Yours, if you have one. Otherwise we choose, and it is still yours.
Other work
The same way of working, on a different system.
Next step
Tell us what must go live, and when.
We come back with a first plan: what done means in your words, what it costs, and when. Then it is your call.