A defined workflow
One process, handoff or recurring decision is costing time, context or money.
- What comes into view
- The people, systems and evidence needed to understand and improve that piece of work.
Working with us
Clear before we begin.Useful before we’re done.
Every engagement follows SPHERE. We agree what success looks like, carry the work through to a practical change and leave your business able to run it.
Talk through one processSame process. Different reach.
SPHERE stays intact. The amount of business in view changes.
We scope around the problem—not a predetermined package. Once the work, outcome and acceptance criteria are clear, the engagement is priced as a fixed fee.
Connected operations
The problem runs across a team, function or several systems.
- What comes into view
- The connected workflows, dependencies and decisions creating the operating constraint.
Across the business
Work needs to join up across functions, locations or entities.
- What comes into view
- The broader operating picture, prioritised so the strongest opportunities move first.
Price and timing are confirmed before work begins. No open-ended billing.
What you leave with
Not a recommendation waiting for someone else to deliver it.
The evidence gathered through SPHERE becomes part of the working result.
- 01A baseline
The current workflow, constraint and measures made visible.
- 02A working change
Configured, connected or built inside the operation.
- 03Business memory
The context and decisions needed to keep improving.
- 04A clear boundary
What AI may do, what requires review and who decides.
- 05A handover
Documentation, ownership and measures your team can use.
Commercial principles
Certainty without the consultancy theatre.
Clear before we begin
We agree the intended outcome, scope, cost, timing and acceptance criteria before delivery starts.
Platform agnostic
We keep, connect, replace or build around technology according to the work—not a vendor relationship.
Founder-led delivery
The people who understand the problem remain involved through design, deployment and handover.
No hidden operating model
Where practical, infrastructure runs through your accounts. Ongoing costs and dependencies are visible.
Ownership without ambiguity
Your operating advantage stays with your business.
The commercial terms draw a clear line between what is specific to your business and the reusable methods we bring to the work.
Your business controls
- Your data
- Your business memory
- Your outputs and configurations
- Your client-specific workflows
- Your deployed capability
Think Spherical keeps improving
- The SPHERE method
- Pre-existing connectors
- Reusable skill patterns
- Non-client-specific components
- General industry knowledge
Value before claims
Measure the work before promising the return.
We establish a baseline using the measures that actually fit the workflow. That may be recovered time, but it may also be fewer errors, faster decisions, protected margin or lower operational risk.
VolumeHow often the work happens
TimeLabour consumed each time
DelayWaiting between steps
ReworkErrors and repeated handling
ValueRevenue or margin affected
RiskConsequence and confidence
If the likely value cannot justify the change, we recommend a smaller move—or no build at all.
After launch
Prove it. Stabilise it. Put your team in control.
We compare the result with the agreed baseline, correct what is not working and document the operating model. Your team can take it from there, or we can continue improving and extending the capability with you.
See the SPHERE processStraight answers
Before we work together.
Do we need an AI strategy before speaking to you?
No. Bring us a process, handoff or operating problem that feels slower, less reliable or harder to see than it should. We determine whether AI belongs in the answer.
Does every engagement begin with an audit?
No separate audit is required. Evidence gathering, diagnosis and prioritisation are part of SPHERE. The work continues into a practical change when the evidence supports one.
Will we need to replace our current systems?
Not by default. We first decide whether the best move is to keep, connect, replace or build around what you already use. The choice is based on cost, flexibility and fit with the business.
Who owns the data and what gets built?
Your business controls its data, business memory, outputs, configurations and client-specific deployment. Think Spherical retains its pre-existing SPHERE method, reusable skill patterns and non-client-specific components. The exact position is agreed before work begins.
What if the evidence does not justify a build?
We say so. The right outcome may be a process change, better use of an existing system or no investment at all. A custom build has to earn its place.
What happens after launch?
We stabilise the change, compare it with the agreed baseline, document how it works and hand over operational control. Ongoing improvement and support can continue where it is useful.
Start with the work
Bring us one process worth improving.
We’ll help you frame the problem, establish whether the value is real and explain what a sensible engagement would involve.
Start with one process