The deal terms.
Every term is here, on one page. You sign these terms before any build starts. The build fee is $0. The subscription starts only after the acceptance test passes.
The short version
You pay nothing to build. You pay monthly only after a written test passes. You can leave any month and take your data. I own the software and may resell it, even to competitors.
Terms
Eighteen terms, in four groups. Nothing hidden in a contract you see after the work.
Ownership
The question I am asked first.
- Ownership
- I own the software and may sell it to third parties, including the client's competitors.
Money
- Build fee
- $0
- Subscription price
- Set per industry. Fixed for a stated number of months. Put in writing before the build starts.
- Launch client price
- The first client in an industry always pays less than the standard price for that industry. The gap never expires. When their fixed term ends, they renew below the standard price.
- Model costs
- Model and tool costs sit inside the monthly price. The price does not move when a vendor raises its prices.
- Spend limits
- There is a monthly cap on model and tool costs, set per client in the contract, against an agreed volume of work. I carry anything over the cap. If your volume grows past what we agreed, we set a new price rather than a new cap.
- Start date
- The day the acceptance test passes. Until then the client pays nothing.
Your data and exit
- Cancellation
- Notice before month end takes effect at month end, with no fee.
- Data export
- Within 7 days of a request, all data as CSV or JSON.
- Data retention
- 90 days after cancellation, then deleted.
- Continuity
- If the service stops, 90 days written notice and a full data export.
Quality and safety
- Acceptance test
- A written list of pass or fail tasks, agreed and signed before the build starts.
- AI behaviour
- The agent is tested against real cases before launch. The list of cases is agreed in writing, and the agent must pass it before the subscription starts.
- Human handoff
- When the agent is not sure, it hands the work to a person. Which cases trigger a handoff are listed in the contract.
- Documentation
- Every feature explained in writing, so a person with no software training can complete each acceptance-test task using only the docs.
- Security review
- A named security review before launch. The scope is set per client in the contract.
- Breach notification
- I notify the client within a stated number of hours of a confirmed breach. The hours are set per client in the contract.
- Uptime
- An uptime commitment, set per client in the contract.
What it costs a month
A five-person engineering team costs about 120 times more. The exact price is set for your industry, and it is put in writing before I build anything.
Two terms are promises. Nobody can check deletion and continuity until they are tested.
What I turn away
The full list. If one of these is you, this is not a fit, and I will say so quickly.
- A chatbot that only answers questions. I build agents that do the work.
- Venture builds where the code is your edge.
- Regulated and procurement-bound firms that need to own the code.
- One-time payers who want to buy the code outright.
- Industries without a few hundred similar companies.
- One-off features the rest of your industry would not fund.
Ready to see if it fits?
Tell me what the agent should do. I will tell you if I will build it.