Show us one problem. We'll tell you what we'd fix first.
A free 30-minute call. You show us one recent case on screen, the way your team really does it. Within two business days you get a one-page note, "What we'd fix first", and you keep it whether or not you go ahead. Building is paid.
Mostly over screen share and a shared channel, in working sessions with your team.
Thirty minutes, on one real case.
The last time it happened
You pick one recent case and show it on screen with the real file open: who touches it, where the data comes from and goes, and what breaks.
The problem behind the problem
We ask what you would do differently if it were fixed tomorrow, what you have tried, and why now. Then we read back the problems we heard and agree on one.
What "working" means
We agree how we would both know it worked, who decides, whether we can get to the data, and what is off-limits.
The next step
Before we hang up, we book 20 minutes to go through the note together.
“What we'd fix first” is yours to keep.
If you choose to send a sample beforehand, the note may come with a small working piece built on it.
- 01What you told us, in your words.
- 02The real problem, and why we think so.
- 03The first job, and what you would have at the end.
- 04A draft bar for "working": a few statements you can check.
- 05What we would need from you.
- 06One or two things you can do yourselves this week.
- 07What we would not do, and who could.
When you book, we ask five questions.
- 01What's the problem, in your words?
- 02Which software is involved?
- 03Who does it today, and how often?
- 04What made you look at it now?
- 05How did you hear about us?
You can send a sample before the call if you like: an export, a screenshot or a short screen recording, with names removed. Never send passwords.
We ask before recording a call.
It's a good fit when
- A recurring job, or something broken, costs you time or money now.
- The person who decides is on the call, or on the next one.
- We can get to the data.
- It's our kind of work. If it isn't, we'll say who it's for.
It can be any of the five parts: reports & answers, fixes & connections, cleanups & bulk changes, ai workers or custom software.
Then a two-page brief, signed before anything is built.
The brief sets out the outcome in your words, the bar for "working" as a few checkable statements, what is in and out of scope, what we need from you, weekly checkpoints with a demo, who owns what, and what happens if we miss the bar. Beyond a sample you choose to send, nothing is built and we get no access to your systems until you have signed it.
Four steps, the same every time.
Mostly over screen share and a shared channel, in working sessions with your team.
Learn the work
We sit with the people who do the job, over screen share, and watch how it really runs, workarounds included.
Build on your data
We report on, fix, clean up, automate or build what the job needs, on your real data, with the least access it takes: read-only first, a test copy where possible, everything in your accounts.
Prove it against a bar you agree
Before we build, we write down with you what "working" means. The first working result is checked against that bar on your data, with stop points along the way.
Hand it over or run it for you
You run it: code, data, admin access, documentation and training, then our access is removed. Or we stay on and run it, including any AI worker.
Walk us through one problem. We'll tell you what we'd fix first.
Free · 30 minutes · a one-page note within two business days