So I did what every 'techie' would do before automating an entire firm.
Pen and paper.
Yes, I bought a giant drawing pad, a bunch of post-it notes, and some coloured markers, and blocked out three days.
Then I tore my own firm apart on it. Every workflow, hand-drawn. Every process, broken into micro-steps. The systems used, the triggers, the inputs, the outputs, the handovers, the pain points. Where the time leaked. Where the quality dropped. Where I was doing the same thing twice because two tools didn't talk to each other.
Then I scored every step on a value matrix — what's high-value-only-Peter, what's high-value-but-anyone-could-do-it, what's pure admin drag, what could be automated tomorrow.
I'd essentially audited my own business.
What I drew on those sheets of paper is exactly what I now run for other recruitment founders. I call it the AI Performance Audit™.
The build that came out of that audit had four rules I refused to break:
Rule one — first principles, before tools.
Identify the biggest problem you're trying to solve. Describe what good looks like before you build a thing. No automating low-impact admin for the sake of it. No buying a tool because it's trending on LinkedIn. Only the highest-leverage problems earned a build.
Rule two — live searches only.
Every workflow had to survive a real candidate, a real client, a real deadline — with client data protected throughout. No sandbox. No demo data. If it didn't work on a paying search, it didn't ship.
Rule three — one module live before the next.
Start small. Iterate in production. Each module shipped, ran on a real search, produced an artefact, then informed the next. No parallel builds. No building ahead of validation.
Rule four — Customer One from day one.
Designing for one firm is a dead end. Designing for two is a Plugin. So from module one, I built with a Customer One in mind — a second search firm who'd use it. Even if for free. Even if only part of it. The moment another founder tries it, you begin to see what really works.
Four rules. One discipline. That's why Customer Zero isn't a marketing concept — it's the operating system of the firm.