Better work.
Built together.
From a first conversation to a system your people run, in six stages.
Book a discovery callDiscovery call
No commitmentAudit
Paid, scoped separatelyProposal and plan
Agreed before we buildDevelopment
With your peopleIntegration and training
In your environmentMaintenance
Optional
Discovery call
One call to understand the problem, the people and the systems. It commits you to nothing.
Make the
handoff clearer.
Requests arrive in different places.
Everyone knows the next step.
Keep final approval
with our people.
Let’s build around that.
Audit
A paid, separately scoped review of your workflows, systems and data, with the people who do the work.
Where the week
goes missing.
- Re-keying orders from inbox to CRMManual
- Approvals waiting on one personWaiting
- Finding the current price listSearching
- Intake checks
- Approval routing
- Knowledge search
Start with the approvals.
You receive
- A current-state assessment
- Prioritised opportunities
- A recommended approach
- A roadmap, with agreed measures
Proposal and plan
The audit, or a defined brief, becomes a plan you can hold us to.
The investment, in four parts
- Audit
- Scoped and billed on its own.
- Implementation
- Priced against the agreed scope and milestones.
- Infrastructure and usage
- Cloud and model usage, pay as you go, in your accounts or ours.
- Ongoing support
- Optional, under a separate agreement.
Agreed before
we build.
- Scope, deliverables and acceptance criteria
- Who owns accounts, environments, data and code
- What runs automatically and what a person approves
- The baseline, the target and how we measure the change
Final approval stays with our people.
Development
Your team stays involved as the work takes shape.
Make the idea tangible.
A working version around agreed scenarios, so your team has something real to respond to.
A clearer request.
Access to project files
Operations
Team lead
Start with the way requests arrive.
Made for
your people.
Your team, equipped.Integration
and training.
The workflow runs where it belongs, with the people who run it.
- Connected to your environment.
- Integrations, access and ownership, worked through with you.
- Practised with your team.
- Training on the scenarios your people meet every day.
- Documented for everyday use.
- Guidance that makes responsibilities clear.
Maintenance
Support and improvements, scoped separately. Hosting is agreed separately.
Agreed in scope,
not assumed.
Settled in writing on every engagement.
Employee adoption
Your people in discovery, testing and training. Uptake measured, not assumed.
Data and access
What a workflow can reach, where it runs and who can use the result.
Human oversight
What runs automatically, what gets reviewed and who approves.
Integration feasibility
APIs, permissions, data quality and licences, checked before we commit.
Operational ownership
Who owns decisions, accounts and the technical work after handover.
Three patterns we see often.
Patterns, not case studies.
Incomplete briefs, approved releases
Check the brief, route feedback and approvals, and release only on explicit sign-off.
Document collection, reviewable records
Collect the documents, extract the details, flag gaps and prepare the record for a reviewer.
Scattered information, sourced answers
Connect approved sources and answer questions with the supporting document attached.
Questions we are usually asked first.
What does the audit involve, and is it paid?
Yes, it is scoped and billed separately. We interview the people doing the work, examine the workflows, systems and data, and hand you prioritised opportunities, a recommendation and a way to measure the change.
Do we have to replace the tools we already use?
No. Most of the value sits in the manual work between systems, so we connect what you have. We only propose new software when your existing tools cannot support the workflow.
Where does our data go?
Decided with you before anything is built: what a workflow can access, where it runs, who can use the result and which actions need approval. Deployment can run in your cloud account or ours, with ownership agreed in writing.
Who approves what the AI does?
Your people. Every workflow defines what runs automatically, which exceptions need review and which decisions stay with an accountable person.
What happens after launch?
Integration, training on your real scenarios and documentation are part of delivery. Maintenance, monitoring and hosting are scoped separately.
How long does a first project take, and what does it cost?
A first project stays narrow enough to build, evaluate and measure. Scope, timeline and investment are set out in the proposal. There is no standard package or public price list.
Start with a discovery call.
One conversation. It commits you to nothing.