Why We Built Our CRM and Performance Trackers In-House
We built our CRM and performance trackers in-house because off-the-shelf tools forced us to adapt our process to their structure, when a small agency's edge is usually the opposite — a workflow shaped exactly around how the team actually operates.
Where off-the-shelf tools broke down
Most CRM platforms are built around a generic sales pipeline — lead, qualified, proposal, close. Our actual lead flow (PPVL lead generation, franchise consultancy enquiries, and project-based creative work) doesn't map cleanly onto that shape, and every workaround added friction the team had to remember manually.
Performance tracking had the same problem: SEO, paid ads, and creative delivery each have different useful metrics, and most generic dashboards either force everything into one template or require three separate paid subscriptions to cover all three.
What building in-house actually cost
The honest tradeoff: building in-house costs real development time upfront and ongoing maintenance that a subscription doesn't. It only pays off if the tool gets used daily and if the customisation genuinely removes friction rather than just being customisation for its own sake.
We treated the first build as a working prototype, not a finished product — shipping the smallest version that handled our actual lead flow, then extending it as real gaps showed up in daily use rather than designing every feature upfront.
When off-the-shelf is still the right call
For most small teams, a standard CRM (with custom fields and automations configured, not custom-coded) is the right starting point — building in-house only made sense for us once we'd hit specific, recurring friction that configuration alone couldn't fix.
The tell I'd watch for: if you're building workaround spreadsheets next to your CRM every week to track something it can't handle, that's the signal a custom tool might pay for itself. If the workaround happens once a quarter, it's cheaper to keep tolerating it.
- Start with configuration of an existing tool before building custom
- Build the smallest working version first, extend based on real daily friction
- Weigh ongoing maintenance cost, not just the initial build cost
- Custom tooling pays off when it removes recurring, high-frequency friction — not occasional annoyance
Frequently Asked Questions
Isn't building a CRM in-house a distraction from client work?
It can be, if scoped poorly. We kept the initial build small and treated it as internal infrastructure with a hard time budget, not an open-ended side project competing with client delivery.
How do you know when to stop customising and just buy a tool?
When the friction you're solving for is rare rather than daily — occasional edge cases are usually cheaper to handle manually than to build permanent tooling around.
Does an in-house CRM scale as the team grows?
It can, but it requires deliberate investment as headcount grows — this is one of the real ongoing costs of the custom route that's easy to underestimate at the start.
Key Takeaways
- Off-the-shelf tools cost less upfront but force your workflow into their structure.
- Custom tooling pays off when it removes recurring, high-frequency friction — not occasional annoyance.
- Start with the smallest working version and extend based on real daily use.
- Configure an existing tool before defaulting to a custom build.
Have a project that touches web development?
Get in touch