Short fit call
Check there is a real project, a real confusion point, and a bounded reason to investigate before anything heavier starts.
Process
How Statepath keeps the route finite, legible, and low theatre.
The process is designed to make the current state readable, keep access proportionate, and return one decision-ready route without blurring into a much larger engagement.
Access
Read-only preferred where possible.
Scope
Agreed surfaces only.
Closeout
Temporary access removed at closeout.
Working sequence
The route should feel deliberate, not chaotic.
Each step exists to keep scope tight and the result decision-grade.
Proposal and scope lock
Agree exactly what will be reviewed and what stays outside the audit so the work does not quietly sprawl.
Access and onboarding
Use the minimum practical access route, with read-only access preferred where possible.
Audit and review
Inspect the agreed surfaces, separate what is direct, derived, or unresolved, and assemble the decision pack without blurring those truth states together.
Return one next route
Deliver one sensible next move. If a bounded corrective lane is found, it can be quoted separately. If the truth points to something broader, the broader route is named explicitly instead of blurred.
What gets checked
The audit checks the agreed surfaces, their contradictions, and the decision risk around them.
Process is not just sequence. It also defines what Statepath is actually looking for inside the named repo, docs, dashboards, automations, and handover material.
Repo, code, and implementation surfaces
Review the parts of the live build, scripts, configuration, or automation logic that are actually in scope for the decision.
Docs, handover notes, and operating story
Check whether the current explanation still matches the current implementation or whether the narrative has drifted from the truth on disk.
Dashboards, flows, and live-route behaviour
Inspect the named dashboards, integrations, exports, or flow surfaces that matter to the actual decision instead of assuming the route lives only in code.
Contradictions, blockers, and decision risk
Look for the specific gaps, conflicts, or fragile assumptions that would make the next wrong move expensive if they remain unresolved.
What this prevents
The method is designed to stop three predictable failures before they compound.
Premium process should feel safer because the route blocks avoidable sprawl, over-access, and confidence-heavy guesswork before they become expensive.
Scope drift before truth exists.
Without a fixed sequence, the work quietly expands from one bounded audit into broad rescue labour before the baseline has even been made legible.
Too much access before real need is proven.
The process keeps access proportionate so the review can stay serious and bounded instead of defaulting to “give us everything” by habit.
A recommendation that outruns what the surfaces actually prove.
The sequence forces confirmed truth, caveats, and one next route into the same pack so the answer stays decision-grade rather than confidence-heavy.
Truth labels
The pack keeps direct, derived, and unresolved material separate on purpose.
This is the discipline that stops a tidy summary from over-claiming what the agreed surfaces can really prove.
Direct
Use direct when the agreed surfaces themselves clearly support the claim without extra interpretation doing the real work.
Derived
Use derived when the route needs reasoned interpretation across multiple signals, even if that interpretation is sensible and well-supported.
Unresolved
Use unresolved when the current surfaces cannot prove the point cleanly enough yet and caution still belongs in the recommendation.
Trust and privacy
Operate with the minimum access needed, and keep the route inspectable.
Minimum access, agreed surfaces, and a clean closeout matter more than looking busy.
- read-only access is preferred where possible
- only the agreed in-scope materials should be used
- temporary access is preferred to shared personal credentials
- access should be removed at closeout
Client secrets, credentials, private code, sensitive personal data, or confidential commercial material should not be placed into third-party AI tools unless explicitly agreed in writing for that engagement.
Best first note
The strongest first contact is short and concrete.
The goal is enough context to judge fit, not a novel.
- the project
- the confusion point
- why the wrong next move matters
If one clearly bounded corrective route exists, it can move forward cleanly.
That follow-through lane is quoted separately at £1,500 fixed. If the truth points to something broader, the broader route is re-scoped explicitly rather than being smuggled into the original engagement.
Output delivery boundary
The first delivery ends with a pack and one bounded route, not a hidden implementation commitment.
This is where the process turns into a usable handover: clear enough to act, but still honest about what belongs inside the first step and what remains separate.
One decision-ready audit pack
- first-read summary
- current-state truth map
- risk and caveat notes
- one bounded next-route recommendation
Anything broader than the first step
- open-ended implementation labour
- permanent support expectations
- broad rescue work hidden inside the audit
- follow-through unless one bounded corrective lane is clearly justified
If one clearly bounded corrective lane exists, optional follow-through can be quoted separately. If not, the broader route must be re-scoped explicitly rather than implied by the audit pack.
Linked pages
Use the page that answers the next question instead of forcing everything into one slab.
That is the whole point of the new structure.
See the fixed-fee structure and scope boundary.
Lead fee, follow-through lane, included outputs, and what is intentionally out of scope.
Open Offer
Check whether the route fits the project.
Inherited builds, AI-heavy drift, automation tangles, and decision-pressure signals.
Open Situations
See the decision-pack shape before any scope handover starts.
Review the truth-map, risk-note, and next-route structure that the process is designed to produce.
Open Sample Output
Read the access boundary and review posture.
See how Statepath handles agreed surfaces, read-only preference, and closeout before anything starts.
Open Trust & Access
Use the fit-check route that now lives on-site.
Send the project, confusion point, and why the wrong next move matters from a dedicated page.
Open Start Here