Technical discovery
One workflow, connected to the systems that hold the answer, running on your data.
- A written plan
- A working version on your data
- A go or no-go recommendation
IWise / Method
Six stages. Something you keep at each one.
Every engagement runs in the same order, and a stage does not start until you have signed off the one before it. Two things change from business to business: what we build at stage 4, and who runs it at stage 6.
01
Start: tell us how your business runs.
Take the free Ops Audit, four questions and about two minutes, or book a free fifteen-minute call. An architect reads it and takes you through a 45-minute technical session. None of this costs anything.
02
Map: work through the business, function by function.
Strategy workshops, including full-day immersion sessions, with the people who run the business. Together we find where the hours go, which work repeats, who owns it, where a person needs to approve, and what a correct answer looks like.
03
Prove: one real job, on your own data.
A fixed-price technical discovery, and the first thing you pay for. We take one job your team does today, connect it to the systems that hold the answers, and run it on your own records. Not a demo. If it will not work, we would rather find out here, and so would you.
04
Build: the AI Brain first, then what the map calls for.
The AI Brain is your company's knowledge in one place, connected to the software you already run, with skills written from your own procedures and agents set up for each function. On top of it we build whatever the map calls for: AI automation, agentic AI workflows, voice AI, MCP integrations, AI engines or a new AI product.
05
Ship: go live one step at a time.
It goes live behind your own security. Research, analysis and drafts come first. Anything that sends, pays or publishes is switched on only once the quality is proven. We run the first 60 days beside your team.
06
Compound: keep it running, then add the next function.
You choose who runs it. We keep operating it, a PairedOps operator runs it for you, or your team takes it in house, trained to write its own skills. Models change without asking, so whichever you choose, it is tested again every quarter against real cases. The next function goes onto the same Brain, and each one is faster than the last.
Working together
Three shapes. None of them per seat.
We price the engagement, not the person. There is no seat count and no token allowance. The Ops Audit, the fifteen-minute call and the technical session are free.
Implementation
The AI Brain, the agents, the connections into your software and the limits they cannot cross, taken live.
- The system, in your repository
- The tests that catch its mistakes
- A written procedure and a named person to call
Build and operate
We keep running it: tested every quarter, model changes absorbed, new functions added.
- A quarterly test run against real cases
- A named person on call
- A clean exit with the documentation
Questions
The ones worth asking.
Is the free Ops Audit the same as the paid discovery?
No. The Ops Audit is free: four questions, about two minutes, and you get the architect's read on where our AI OS fits, a 45-minute technical session and a written recommendation. The fifteen-minute introductory call is free as well. The technical discovery is stage 3 above, it is fixed price, and it is the first thing you pay for. Nobody gets sold a discovery before the free part has happened.
What happens when the model changes underneath us?
Every system we run carries a graded eval set, and that set reruns whenever a provider ships a change. The deltas get written down whether they are flattering or not.
What if it breaks at 2am?
A written procedure for exactly this ships at stage 5, before anything goes live, along with a named person to call.
What do you need from our team?
Two people. A product owner who can say what a correct answer looks like, and a systems owner who can grant access and sign off on what the agent is allowed to write. If neither exists yet, that is worth solving before you spend money with us.
How is this different from hiring someone in-house?
A hire is one person, six months out, with no eval harness and no second opinion at 2am. You get a pod that has shipped this before, and a written methodology with gates you can hold us to. When it is running steadily, you can take it in-house with the runbook.
Do you also do placement or offshoring?
Yes, through PairedOps. Offshore operators paired with AI agents on Claude take a whole function off your desk, and we can recruit, train and place the operator who runs it for you. Ask us which fits.