What an AI agency delivers in 30 days
In thirty days a serious build should be running on your real data. We built Content OS from the first line of code to live and posting daily within one month, and what ships in that time is one system doing one job end to end rather than a roadmap for several.
On this page
What happens in week one?
Questions, then a written proposal with one fixed price and one delivery date. Nothing is signed before you have read the solution and the number.
| Week | What exists at the end of it |
|---|---|
| Week one | A written proposal with a fixed price and a date |
| Week two | The first working path running on test records |
| Week three | The system running on your real data, with you watching |
| Week four | Handover, and the system running on your accounts |
Week one is mostly reading and asking. The single biggest cause of a failed build is an agreement to build the wrong thing quickly, and the only defence is spending the first days making the problem specific enough to price.
What runs by day 30?
One system doing one job end to end, on your accounts, with your data going through it. Not three half systems and not a plan for the next quarter.
Content OS is the proof we can point at, because it is ours and we can say everything about it. It went from the first line of code to live and posting daily on a real page within one month, and it has been posting since September 2026 [1]. It picks the time, the topic and the template for each slot, writes the post and waits for a human yes before anything publishes.
A client build in the same window is usually smaller than that, because a client system does one job rather than being a product. The lead outreach system that a real estate agency ran was a first month build, and the result was readable without anyone explaining it.
What does not ship in the first month is everything that was not the job. No second channel, no reporting layer nobody asked for, no admin screens built in case. Every one of those is a separate proposal with its own number, and keeping them out is what makes the first month deliver something instead of half of four things.
The habit that protects the date is testing on your real records rather than on a clean demo set. Real data is messy in ways no demo anticipates: duplicate leads, half filled fields, a customer who replied to a message from last year. Finding that in week three is a normal week; finding it after handover is a failed project.
What is left for the retainer?
Monitoring, fixes and small changes, all of it optional [2]. The things that were deliberately out of scope stay out of scope until you ask for a new proposal.
The retainer exists because the systems on the other end change without warning. A vendor renames a field and a connection that ran for six months stops. Somebody has to notice, and if you would rather that were us, it is.
What the retainer does not do is quietly widen the build. A change that is genuinely new work gets its own proposal and its own number, so nobody discovers a bigger invoice at the end of a month.
What should you expect to see?
A result you can read without a meeting. That is the only honest measure of a first month.
The three systems we publish numbers for are on our work, including the Content OS case study and the real estate lead outreach case study.
Tell us the problem on the contact page, and you get a proposal and a price before any deal is signed.