How I work
Here’s exactly what happens, week by week.
This is the whole process, including the parts where you have to do something.
The Systems Map · one week
It starts with a week of looking
You can’t quote a fix for something you haven’t seen. Anyone who gives you a price for this work over the phone, before looking, is guessing, and you’ll pay for the guess later.
Day 1
I come to you
I sit where the work lands. I watch what your people actually do, where they retype things, and where they paste something into a chatbot because no proper tool exists. I follow one piece of work end to end, from first contact to money in. I ask a lot of questions. You don't have to prepare anything.
Days 2 and 3
I map it and time it
Every system that work touches, drawn out, plus every spreadsheet holding a gap together. Then I time the manual steps: how long the retyping actually takes, how often it gets missed, and which of those steps a machine could do now.
Day 4
I cost it
Every break gets a number. Hours a month, at what those hours cost you, plus the work that falls through and what a piece of it is worth. If I can't put a number on something, I say so.
Day 5
You get the document
I write it up and walk you through it on a call. You get the map, the costs, a fixed-price quote to fix what's worth fixing, and a list of what isn't worth fixing. It's your document. If you want to hand it to someone else to build, you can.
What you have to do: give me a few hours on day one, and access to the software you already pay for. That’s it. I don’t need you to prepare anything or tidy anything up. The mess is the point. I need to see it as it really is.
The connections · two to five weeks
Connecting them
Fixed price, quoted from your Map. Every system I’m connecting is named in the quote before I start. Most businesses need two or three.
Week 1
I build it away from your live system
Nothing touches your live data yet. I build what's named in your quote and test it against made-up work until the edges stop breaking: the malformed input, the duplicate, the one that arrives half-finished. Edges are most of the job.
Week 2
It runs alongside you
It goes live in parallel with how you work now. Real work going through it, and your team still doing it the old way as a backstop. We compare. I fix what's wrong. Nothing is at risk because the old way is still running.
Week 3
You switch over
Your team stops double-handling. I'm watching closely for the first week and I'll be quick to answer. Most of what needs fixing shows up here, and it's included.
Handover
The documentation
Written, in plain English: what's connected to what, what to do if something looks wrong, and who to call. It's on your accounts, in your name. If you and I part ways, none of it switches off.
I take one build at a time. If I’m busy when you want to start, I’ll tell you the real date.
The monthly · month to month
Keeping it working
A connection between two systems isn’t a thing you finish. It’s a thing that breaks: when a supplier changes a form, when your software updates, when someone renames a field, when a staff member leaves.
When it breaks, it usually breaks quietly. Jobs stop flowing and nobody notices for four days. That’s what the monthly fee is for.
- I watch everything I’ve built you, automatically, and I get alerted when something stops.
- I fix what breaks. It’s covered. No extra invoice, no hourly clock, no ticket queue.
- A short note every Friday. What got answered, what got booked, what went through and what didn’t. Ten seconds to read. You get it on the quiet weeks too. A quiet week is the point.
- A page at the end of every month with the numbers, and what it saved you, in dollars.
- Half an hour with me, once a month. Not a support call. A call about what’s next: what other businesses are doing, and what’s worth building now that wasn’t possible six months ago. When something better ships, I tell you. When it’s noise, I tell you that too, and most of it is noise. Ask me anything you like about how any of it works.
- Two hours a month of changes and additions, rolling over up to six.
30 days’ notice to stop, any time. It runs month to month.
Access and your data
What I can see, and what I can’t
You’re about to give a stranger access to the software your business runs on. I never ask for your master password, I use scoped access you can switch off yourself, and I show you exactly what I’ll be able to see before you hand over anything.
Next step
Tell me what your systems are.
30 minutes on a call. Bring your two worst systems.
