Three businesses, three completely different jobs, three CRMs built from scratch to match. Each one is in daily use running a real company — and none of them would be much use to the other two. Here is what was changed for each, and how the work actually flows through it.

Built forA working photographer booking shoots across two brands, where the job is won or lost before the shutter ever opens.
A photography business does not run on a sales pipeline. It runs on a look — the reference images, the palette, the framing everyone agreed on before the shoot day. So this CRM was built around the creative brief, not the deal stage, and everything else hangs off it.
From the booking form on the public site to finished photographs in the client's hands — one path, no spreadsheet, nothing re-typed.





This is the one that keeps this website running.
Built forA studio that builds and then keeps running client websites — where the work does not end at launch, it starts there.
Selling a website is the easy half. The hard half is the years afterwards: is the server healthy, did the backup run, has this site had its maintenance this month, and did the client ever get a report about it. This CRM was built so the answer to all four is on the same screen as the client's invoice.
The whole life of a client website — sold, built, launched, watched and reported on — tracked in one place.



Built forA DMCA takedown service acting for creators, where the product is not a project — it is thousands of individual URLs, each at its own stage.
There is no version of an off-the-shelf CRM that models this. A client is not worth a deal value, they are worth a removal rate. So the sales furniture came out entirely and the whole application was rebuilt around a single unit of work: one stolen link, moving from found to gone.
Thousands of links, every one at its own stage, worked column by column until the board is empty.

Every one of these started the same way: someone doing the job by hand across four tools that didn’t talk to each other. Tell us how your work actually flows and we’ll build the software around it — not the other way round.