Most of our work is building software for other people. A few years ago we decided to build something for ourselves: Digi CRM, a tool to manage the messy reality of leads, conversations, and follow-ups that every agency knows too well. Being both the maker and the daily user changed how we think about software.
You feel every shortcut you take
When you build for a client and move on, the small compromises — the clunky flow, the report that takes one click too many — become someone else's daily friction. When you use your own product every morning, those compromises come back to find you. It is a humbling and clarifying feedback loop. We started fixing "minor" annoyances we would once have shipped, because we were the ones wincing at them.
The feature you were sure about is rarely the one that matters
We planned Digi CRM around an elaborate reporting engine. What people actually reached for was something far more mundane: a fast way to see who had gone quiet and needed a nudge. The lesson repeats across almost every product we have touched — the roadmap you write confidently at the start survives first contact with real use for about a week.
Ship the smallest thing that solves a real problem, then let the people using it tell you what to build next. They always know better than the plan.
Simplicity is a feature you have to defend
Every product accumulates requests. Each one is reasonable on its own; together they turn a sharp tool into a bloated one. The hardest and most valuable product work is saying no — protecting the core flow so the thing that made the product useful does not drown under the things that made it complicated.
What we changed in our client work
Living with our own product quietly rewrote how we build for others:
- We prototype the daily flow first, not the impressive edge cases. The thing people do a hundred times a day deserves a hundred times the attention.
- We ship earlier and narrower, then iterate with real usage instead of guessing in a spec document.
- We treat performance as a feature. A tool you use all day has to feel instant, or people quietly stop using it.
- We design for the boring moments — the empty state, the error, the fifth time you do something — because that is where products are actually lived.
The real dividend
Building our own product made us better partners on everyone else's. We now speak about roadmaps, trade-offs, and maintenance from the inside, not the outside. When we tell a client that a feature is not worth the complexity it adds, it is because we have paid that bill ourselves. If you are weighing whether to build a product of your own, we would gladly share what the experience taught us — the parts that do not make it into the pitch decks.