How we work: from proposal to handover
Five steps run every project: you tell us the problem, we send a proposal with the price, you take a pilot or the build, you watch it run on your real data, and we hand it over. The proposal comes before any deal is signed, in writing.
On this page
What are the five steps?
They run in this order on every project, with no step skipped and no step reordered. Nothing is signed before step two is in your hands.
- Tell us the problem. In your own words, on the form. No technical brief, no diagram and no meeting with your software provider.
- Proposal and price, in writing. You see the solution, the fixed number and the delivery date before anything is signed.
- Pilot or build. The first time you work with us you can start with a small paid pilot. Otherwise the build starts on the agreed date.
- Test on your real data. You watch it run on real leads, real orders or real bookings before handover.
- Handover. You own the system. A monthly maintenance retainer keeps it running if you want us on it.
Why does the proposal come before any deal?
Because the most common thing an owner tells us is that last time they paid and got a slide deck. Reading the solution and the number first is the only protection that costs you nothing.
What does the proposal actually contain?
The problem in your words, the system we would build, every tool it reads from and writes to, one fixed price and one delivery date. It is written to be read by the owner, not by a developer.
If you would rather read what a written proposal should contain before you send anything, that is set out in do you need automation consulting.
What does the test on real data prove?
That the system works on your business rather than on a demo. We built Content OS from the first line of code to live and posting daily within one month, and the same habit applies to a client build: it runs on the real thing before it is yours [2].
What happens at handover?
You get the system, the accounts and the data, and we keep nothing that lets us switch it off. The monthly maintenance retainer is optional and covers monitoring, fixes and small changes [1].
What moves the price inside $300 to $9,000 is on the pricing page. What we build is on custom AI agents, lead generation systems and AI software and app development, and the awkward questions are on the FAQ.
Tell us the problem on the contact page, and you get questions back, then a proposal and a price before any deal is signed.
How long does a build take?
Content OS went from the first line of code to live within one month, and most client systems are smaller than that. The proposal commits to a delivery date.
Can I see the proposal before I pay anything?
Yes. The proposal and the solution come before any deal is signed, in writing, with the price and the delivery date on the page.