The scope step
Start with a scope.
Days — the scope: a written plan with deliverables, gates and a date. The Advisory Sprint is the step every engagement starts with — a film, a voice, a product or a workflow — and it can be bought on its own: decide what is worth building, and what is not, before anyone writes code.
There is no consulting division. Consulting is the scope step every engagement starts with — a written plan with deliverables, gates and a date.
The experience
One conversation. Then it ships.
The scope is the second step of every engagement, whichever door it comes through. This page is that step on its own.
- Day 1
The brief
One call, any door: a film, a product, a voice, a workflow — or all four.
- Days
The scope
A written plan with deliverables, gates and a date — you approve everything.
This page
- Weeks
The ship
Films in days, products and agents in weeks — you review working output, not status reports.
- Always
The run
Operated, monitored, tuned, reported — the engagement compounds instead of ending.
You stay the director of all of it. Every approval is yours; every burden is ours. That’s the deal, across all four divisions, in every engagement.
In the buyer's words
The reasons people ask for a scope before a build.
The board asked for an AI strategy and we have a slide, not a plan.
Statement 01Every vendor says yes. We need somebody to say no.
Statement 02We have a dozen ideas and no way to rank them.
Statement 03Nobody can tell us whether our data is good enough for any of this.
Statement 04The last pilot ran for months and shipped nothing.
Statement 05
What ships
A written plan with deliverables, gates and a date.
4 documents. One of them is a list of the things we recommend you do not build, with the reasoning attached to each rejection.
Ranked use-case shortlist
Every candidate scored, including the ones we recommend against, with the reasoning attached to each rejection.
Stack and data audit
What exists, what is reachable, what is clean enough to build on, and what would have to be fixed first.
Risk checklist
Access, privacy, failure modes and the governance steps each candidate would require before it could go anywhere near production.
A written recommendation
One document, in plain language, that says what to build first, what to defer and what to drop — with a scoped next step for the first item.
“Do not build it” is a finished deliverable
Then that is the deliverable, and it is by some distance the cheapest thing we sell. A two-week sprint that stops a six-month project has paid for itself several times over.
How it works
Every stage ends in a document you can open.
5 stages inside 2 weeks, ending in a recommendation written to be read by the people who will not be building it.
Stage 1: Intake and constraints
Budget, timeline, team capacity and the political constraints nobody writes down. These decide feasibility more often than the technology does.
Output A written constraint map, agreed before any assessment begins.
Stage 2: Data and stack audit
We go and look. Systems, access paths, data quality, integration surface.
Output An audit note per system, with a reachability verdict.
Stage 3: Use-case scoring
Each candidate scored on manual time consumed, rule clarity, data readiness and blast radius if it fails.
Output A scored, ranked shortlist.
Stage 4: Risk and governance pass
What could go wrong, who would notice, and what approval gate would have caught it.
Output A risk checklist per recommended candidate.
Stage 5: Recommendation
A decision document you can take to a board, written to be read by people who will not be building it.
Output The written recommendation, plus a scoped next step for item one.
The engagement
Advisory Sprint
Decide what is worth building, and what is not, before anyone writes code.
Duration
2 weeks
- Use-case shortlist
- Stack & data audit
- Risk checklist
No prices are published on this site. Every engagement is priced in a written proposal for a defined scope.
After the scope
Pick a door. Any door.
Every first engagement is deliberately small, fast and measurable. We’d rather earn the group relationship than pitch it — commercials follow a scoping conversation.
Proof
The method is the proof here. The films are next door.
We have not published an artifact for this service line. Everything in our gallery today is creative work, and dressing a film up as an engineering deliverable is exactly the move this site was rebuilt to stop. Advisory output is also, by its nature, a client’s private decision document. So this page shows you the method in full and asks you to judge that instead.
Questions
The questions a buyer asks before a scope.
Is consulting one of your divisions?
No. There is no consulting division. Consulting is the scope step every engagement starts with — one call, any door, then a written plan with deliverables, gates and a date, which you approve before anything is built. This page is that step, available on its own.
What is the difference between advisory and delivery?
Advisory is strategy, roadmap and feasibility — the plan. Delivery is code, integration and deployment — the build, which the four divisions do. You can buy the plan without buying the build, and a fair number of clients should.
What if the answer is "do not build it"?
Then that is the deliverable, and it is by some distance the cheapest thing we sell. A two-week sprint that stops a six-month project has paid for itself several times over.
How do you handle security and access?
Least-privilege access, clear data boundaries, audit-friendly logging, and architectures that keep your data inside your control wherever the workflow allows it. We hold no security certification and do not claim one.
How quickly can advisory start?
Advisory needs access and calendar time rather than a build environment, so it starts faster than delivery does. We will give you a specific date on the call instead of a range on a web page.
Why are there no consulting case studies on this site?
Because advisory output is a client’s internal decision document, and publishing one would require permission we do not have. The mechanism above is the honest substitute, and we would rather show you that than an anonymised story you cannot check.
Start here
Day 1. The brief.
One call, any door: a film, a product, a voice, a workflow — or all four.
We do not publish a response time, because we have not committed to one we would hold to every week. If it is urgent, WhatsApp is the faster channel.
Client brief
Three questions. The enquiry lands tagged as Start with a scope, and you get a reference number only once the server confirms it arrived.
Step 1 of 3: Who are we talking to?
The engine is running.
Bring one brief. See what four forces do to it.