How we work
Deliberately
unremarkable.
Consultancy goes wrong in predictable ways: vague scope, hourly billing, a six-month discovery phase, a final report nobody reads. We have designed the engagement to make each of those difficult.
The engagement
A calm path from first conversation to working system
No-commitment discovery call
30 minutes · Free
You describe where the time goes. We ask the questions that separate an automation problem from a process problem. It is a useful conversation, not a sales pitch.
You end up with
A straight answer on whether this is worth pursuing — including when it is not.
A thoughtful 24-hour follow-up
Within 24 elapsed hours · Free
We send a short written recap of what we heard, the first problem worth examining, and any immediate questions. You have room to consider it; we do not chase.
You end up with
A clear basis for deciding whether a second call would be useful.
Fit and scope call
30 minutes · Free
If you want to continue, we review the problem, likely scope, responsibilities, timing and fee. This is where we decide together whether to move forward.
You end up with
A defined next step — either an onboarding and audit, or an honest no.
Onboarding and system audit
Introductory audit £75 · Schedule agreed in scope
We meet the people doing the work, map the real process and review approved read-only evidence. You receive prioritised findings and recommendations. Live changes, record-writing tests and implementation require a separate agreement.
You end up with
A prioritised delivery plan with a defined scope, fee and success measure.
Build
Separately scoped · Fixed fee
Short cycles with progress reviews twice a week. We can improve the CRM, build a lead-handling system, create a new website, or connect the pieces already in place.
You end up with
A working system in production, with monitoring, alerting, error handling and a run history you can inspect.
Handover
Agreed in implementation scope
Documentation and training for the people who will maintain the system, with agreed recovery steps, support hours and an escalation route. Around-the-clock human support is not included unless expressly agreed.
You end up with
Full ownership: code in your repository, automations on your subscriptions, credentials in your hands.
Optional partnership
Optional · Separate agreement
You can request ongoing maintenance or improvement, or manage the system yourself after handover. Capacity, response hours, included work, fees and cancellation terms are agreed separately.
You end up with
Named maintenance responsibilities and agreed support arrangements, without an implied 24/7 service.
The deal
Both sides of it
What we need from you
- One decision-maker who can approve scope without a committee
- Access to the people who actually do the work, not just their managers
- Approved system access within the first half-week
- Half an hour per progress review, twice a week
What you get from us
- A fixed fee agreed in writing before anything starts
- Visible progress to review twice a week
- Direct access to the people building it, not an account manager
- A clear answer when we think an idea is not worth your money
Engagement shapes
What a project looks like in practice
Three representative engagements, described by shape rather than by client.
These are illustrative. They describe the type and scale of work we take on, not named past clients. Real, attributed case studies will replace them as there are completed projects and permission to share them.
Professional services firm · 40 staff
The problem
Every new enquiry was manually researched, logged in two systems and assigned in a weekly meeting. Response times ran to three days.
The approach
Intake automation: form to enrichment to scoring to CRM to owner assignment, with a drafted first reply queued for human approval.
Automation build · 2 weeks
B2B software company · 120 staff
The problem
Support specialists spent most of their day answering questions already documented somewhere in a decade of tickets and help articles.
The approach
Permission-aware retrieval layer over the help centre and ticket archive, then a support agent grounded in it that escalates with full context.
RAG + agent build · 4.5 weeks
Multi-site operator · 300 staff
The problem
A monthly reporting pack was assembled by hand from six systems, taking two people the better part of a week every month.
The approach
Automated collection, reconciliation and assembly with variance checks, delivered to the channel where the decisions are actually made.
Automation build · 2.5 weeks
Questions
Working with us
How quickly can you start?
Our target is to start within 1–1.5 weeks of the discovery call, subject to availability and agreed access. Audits may start sooner; where capacity is limited, allow two weeks. Your actual start date is confirmed in the written scope.
What if the build does not work?
Each build has agreed acceptance criteria and progress reviews twice a week. We raise failures and dependencies promptly, then agree corrective action or a scope decision rather than presenting an unverified system as complete.
Do you work with our existing team or agency?
Often, yes. We can run strategy and hand a specification to your developers, build alongside them, or take a defined piece end to end. We are not precious about who does what as long as ownership is clear.
Do you sign NDAs and DPAs?
Yes, as standard. We are happy to work under your paper. We can also work entirely within your infrastructure and accounts if your security posture requires it.
What sizes of business do you work with?
Typically 10 to 500 people. Below that the fixed costs of a proper engagement rarely pay back, and we will usually point you at tools you can run yourself. Above that you generally need a partner with more delivery capacity than we carry.
Next step
Discuss your next operational improvement.
Book a free, no-commitment discovery call to discuss your workflow, priorities and whether an audit is an appropriate next step.
30 minutes · No obligation