Bespoke software, planned before it's built.

If you're running your business across four tools that don't talk to each other, or paying per seat for something that does 30% of what you need, custom is often cheaper than it sounds.

Start a conversation Discovery first, then a phased build

Three projects a month · 2 slots left in September

[ Discovery ]

Two weeks before anyone writes code.

I sit with you and your team and work out what actually happens day to day, as opposed to what the process diagram says. Those are rarely the same thing, and the gap is where most software projects fail.

You get a full technical specification: data model, feature scope, integration points, phasing and realistic cost. That document is yours whether or not I build it — take it to another developer if you'd rather.

The stack is the same one I use for Mirola, my own CRM platform, which runs in production for paying clients. I'm not experimenting on your budget.

[ Scope ]

What that involves

  • Discovery and specification, contracted separately
  • Data model and architecture
  • Phased build so you get something usable early
  • Integrations with what you already run
  • Migration from your current tools
  • Team training and documentation
[ Afterwards ]

The build is how we meet.

Software needs someone watching it. Partner covers ongoing development, integrations and the work that comes after launch.

See how Partner works