The AI-Native CTO OS: your first 90 days

The AI-Native CTO OS is what a Forward Deployed CTO installs inside your team. A Forward Deployed CTO is a senior technical leader who works inside your company, not outside it. The OS has four parts: the plan, the product and platform decisions, the AI-native software lifecycle, and guardrails for anything that runs by itself. It is not a document. It is habits, tools and rules your people run.
Key points in 30 seconds
- Three phases in 12 weeks: Embed (weeks 1–2), Equip (weeks 3–6), Hand over (weeks 7–12).
- One real AI workflow goes live with real users. Your team learns by working on it with us.
- Guardrails come with it: an AI policy, an agent register, spend caps and decision rights.
- You own everything at the end. Nothing depends on us.
- The timing is typical, not a promise. If you start with a weak team or messy data, it takes longer. We say so on the first call.
What happens in each phase?
Tap a phase to see what we install and what you have at the end.
Weeks 1–2
Join the team and write things down.
The plan
Where AI helps in the next two quarters, where it does not, and what it takes. Ten minutes to read. If AI is not your problem now, we say so.
The first workflow
One workflow that matters, is used every day and can be checked. We define "done" before anyone builds: what it does, who uses it, what good looks like, what must never happen.
The AI policy
One page: what AI may touch, what it may not, and who is accountable.
The agent register
A list of everything that already runs by itself, with an owner for each. We add caps and a kill switch to risky items straight away.
At the end: A plan you can see, one workflow with a definition of done, and no automation without an owner.
Weeks 3–6
Build the first workflow and the system around it.
The delivery loop
Intent written before an agent starts. Specs agreed before code. Checks that block bad changes. A narrow AI reviewer, then a human reviewer. A named person who can explain every change. We install only what your stage needs.
Knowledge and model choices
We make your own information searchable. We pick a model by data sensitivity, cost at your volume and capability. A gateway in front lets you change it later without rewriting code.
The guardrails
Spend caps per run and per hour. Step limits on loops. Scoped credentials for agents. Alerts go to a named person, not a busy channel.
The first workflow, live
Small visible pieces, then real users by the end of the phase. Real use shows what is wrong. Better to learn it in week five than in month five.
At the end: A working AI workflow in use, the delivery loop running on real changes, and guardrails on everything that runs unattended.
Weeks 7–12
Move the work from us to your people.
Your team leads, we review
Your people choose and specify the second workflow. We check the plan. Gaps in skills, review capacity or ownership show up while there is time to fix them.
Playbooks from real work
How your team writes intent, reviews an agent change, handles an incident and updates the register. Written from what they just did, not from a template.
Decision rights
For each workflow: what AI does alone, what it drafts for a person to approve, and what stays human.
Hiring, if needed
If you need a permanent technical hire, we say who, at what level, and help you assess candidates. If not, we say that too.
At the end: A team that has run the whole loop on real work, playbooks in their own words, and no dependency on us.
Your team builds with us the whole time. Training is not a course at the end. It is pairing on real work, every week.
What do you own after 90 days?
Everything is in your accounts from day one. Tick each item to see the full list.
What you own at day 90
0 of 6 checked
Some companies keep the partnership after 90 days, because the next quarter brings new decisions. Some do not need to. Both are fine. The system works either way.
What can 90 days not do?
We want to be plain about the limits.
- Puts a working system in place.
- Proves it on one real workflow.
- Leaves your people able to repeat it.
- Transform a whole company in twelve weeks.
- Make AI write your product for you.
- Make a team ten times faster. Anyone who promises that is selling you something.
How do you start?
This is the post-MVP starting point on our plans page. It is for companies with a product in use that want to scale what they build and how. The AI-Native CTO OS page describes the full system. If you are earlier than that, the plans page has a shorter way to start.
Frequently asked questions
What is the AI-Native CTO OS?
The AI-Native CTO OS is the operating system a Forward Deployed CTO installs inside your company: the plan, the product and platform decisions, the AI-native software lifecycle, and the guardrails around anything that runs by itself — agent register, spend caps, review rules and decision rights. It is installed with your team, in your accounts, and handed over so your people can run it without us.
What happens in the first 90 days of the CTO OS?
We typically run it in three phases. Weeks 1–2 are Embed: joining standups, reading the code and the numbers, and writing down the plan and the AI policy. Weeks 3–6 are Equip: installing the delivery loop and guardrails and shipping a first AI workflow to real users. Weeks 7–12 are Hand over: your team runs the loop with us beside them, and the playbooks, register and tools are theirs. The timings are how we usually run it, not a guarantee; every company starts from a different place.
Do we need an engineering team to use the CTO OS?
No, but it changes the shape of the work. With an existing team, most of the effort goes into their process and review capacity. Without one, more of the building is done by us and by agents, and the hand-over covers who you should hire and when. In both cases everything lives in your accounts from day one.
What do we own at the end of 90 days?
The code and data, in your accounts. A written plan. An AI policy and an agent register with a named owner for every automation. A delivery loop your team has run on real work, with the checks and spend caps wired in. And at least one AI workflow in use. Nothing is held back as a dependency on us.