How we work
Engaging us looks and feels like engaging any serious technology partner. Fixed scope. Fixed timeline. Fixed price. Acceptance criteria agreed before any work starts. Weekly check-ins. Your team in the room. The system in production at the end of it. New build or legacy modernisation — the process is the same.
Most engagements start with a 45-minute call. No deck, no demo, no pre-call homework. Just a conversation about what you're trying to fix.
We ask the questions that matter. What does the work look like today. Who does it. How long does it take. What happens when it goes wrong. What would good look like. By the end of the call, we both know whether there's a real engagement here, and we both know roughly what shape it would take.
We end every discovery call with a one-page summary of what we'd do next, sent within 24 hours. You decide if there's a next.
If the discovery call leads somewhere, the next step is a proposal. We write proposals like the one you'd want from any serious technology partner. Scope is defined. Timeline is committed. Price is fixed. Acceptance criteria are written into the document, agreed before any work starts.
Our proposals don't drift. There are no estimates that creep, no time-and-materials surprises, no scope additions presented as urgent mid-build. If the work expands, we issue a change order with its own scope, timeline, and price. You decide whether to commission it.
Proposal · Draft for review
Sales pipeline automation
A four-week engagement for [Client Name]
Every engagement runs on a weekly cadence. We meet for 30 minutes. We show what we built. You tell us what you think. We adjust.
Your team is in the room from week one. The people who'll operate the system once we're gone are the same people we're showing it to as we build. They learn the system as it takes shape, not after we hand it over and wave goodbye.
You see the work as it's built. Staging environments are open to your team. Pull requests are visible. Documentation is written as we go, not stitched together at the end.
Every engagement includes a post-launch support window. The duration depends on the size of the engagement, but the principle is the same: we're available while your team learns the system, while you find the edge cases, while the first month of real usage exposes whatever we missed.
Beyond the support window, you have options. A retainer that keeps us close at a defined cadence. A managed service where we operate the system on your behalf. Or nothing at all, if the system is doing what it was built to do without intervention. The choice is always yours, never assumed.
What we work with
We don't insist on rip-and-replace. Most of the businesses we work with already have software — sometimes a lot of it. Salesforce. SAP. NetSuite. A bespoke CRM from 2008. Three different finance tools that don't talk to each other. We don't tell you to throw it all out and start again. We work with what you have.
Modernisation is real work, not a downgrade. Connecting legacy systems, automating the gaps, putting an intelligence layer on top of data that's been in the same database for fifteen years — that's where most of the value sits for an established business. We treat it as core engineering, not as cleanup work for greenfield projects.
If a system is past saving, we'll say so. Sometimes the right answer is a new build. We'll tell you that honestly, and we'll show our working. The decision is yours, and the price is the same either way.
Straight answers
We don't build inside your existing software product. If you're a software company looking for a feature build, we're not your team. We work alongside your operational systems, not inside your engineering organisation.
We don't take on engagements where success is impossible to define. If the project starts with "we want AI somewhere in the business", we'll tell you so on the discovery call and help you scope it down to something measurable. Vague briefs lead to vague results, and we'd rather decline the work than deliver disappointment.
We don't replace your team with our team. The work we automate is the work that shouldn't be done by humans in the first place — repetitive, rules-based, draining. The judgment, the relationships, the strategic thinking — that stays with your team. Always.