How Building In-House Products Helped Us Build More Empathy with Our Clients

1. From service provider to founder/client mindset

When it’s your own product, you live every decision: the trade-offs, the uncertainty, the late-night “should we pivot?” moments. You feel the risk in your gut. That experience builds empathy; because when clients worry about budget, scope, or timelines — we’ve been there too. We know all our clients have an investor, audience, boss, Board to answer to - and sometimes that can be scary.

And, to be honest, when it’s your own product, you also get to ignore your own advice. You cut corners, skip documentation, and prioritise momentum over process… just to ship something! And that’s exactly the point. It’s a humbling reminder of how hard it is to keep rigour and intent alive across every stage of a build. Personally, I’ve behaved terribly when we’re working on our own thing, as I’m sure the team would attest to! Changed scope without testing things properly, made assumptions, ignored resource bookings…!!

It forces a sharper awareness of time and output. When you’re both the client and the maker, you see every hour as a spend, not just of money, but of opportunity. Every feature, refinement, or rework is a decision about where value lives. You start to weigh the cost of doing against the cost of delay, and you begin to see how precious focused effort really is.

Conversely - you realise that sometimes, you just need time to consider. So when we, as a supplier, are chasing feedback/reviews, sometimes the cogs need more time to turn when collating comments from everyone. 

This experience also cemented something else for us: that product and marketing are inseparable. You can build something exceptional, but it means nothing if it doesn’t reach the right people in the right way. The story, timing, and pathways to adoption are as much part of the product as the code itself. That realisation shaped one of our core offerings at Grade: strategic product marketing. Because building something great is only half the job, the rest is making sure people understand it, trust it, and choose it.

2. We stopped designing for approval and started designing for outcomes

When you build for clients, it’s easy to fall into the rhythm of presentation cycles: showing progress, seeking alignment, iterating through feedback. When you build for yourself, that layer disappears. You’re not trying to impress anyone; you’re trying to make something work.

That changes everything. You start designing for outcomes, not applause. You make decisions faster, validate ideas with smaller bets, and let real-world behaviour (not opinions!) guide the next iteration.

It’s a mindset we’ve carried into our client work. With corporate clients especially, this helps us push toward evidence over assumption. We use the same lean testing, validation and iteration patterns we use on our own products to help large organisations move faster. It’s helped us teach teams to act more nimbly within enterprise structures: to test, learn, and evolve rather than plan endlessly and ship too late.

By building in-house, we’ve lived the friction of getting things live, the anxiety of feedback, and the thrill of quick wins. So when we help our corporate partners shift gears, we’re not speaking theory, we’re sharing mexperience.

3. Feeling the friction first-hand

Nothing teaches empathy faster than living your own UX debt.

When you use your own product every day, you can’t escape your own design flaws. You notice the clicks that shouldn’t be there, the confusing moments, the missing states. It’s confronting, and it builds empathy for clients navigating their own imperfect systems.

From a technical perspective, this has been huge for us. Building in-house has helped us get narrower on when to ship fast and when to ship slow and how to balance technical debt. We’ve learned that sometimes velocity is the right move: get the thing live, learn, and fix later. Other times, you need to slow down and harden foundations before the cracks spread.

That awareness has reshaped our engineering culture. We’re more deliberate about documenting why we made a shortcut, not just where. We plan for iteration instead of pretending we’ll get it perfect. And that makes us better technical partners for our clients; more pragmatic, more transparent, and more strategic about long-term architecture.

4. Building empathy through shared experience

There’s something powerful about being able to tell a client, “we’ve been there.” We’ve shipped products that stumbled, refactored code that aged badly, struggled with onboarding and adoption. We’ve debated features that excited us but confused users. We’ve delayed launches to fix bugs that no one else could see but we knew mattered.

We’ve created a business that tried to flip the real estate market on its head (a lesson in starting small), a ‘Canva Lite’ (a lesson in keeping scope tight), a simple content translation tool (if only we’d seen the Ai wave coming) - all of them have made us better product partners than we were before.

That lived experience changes the relationship. It moves conversations from vendor/client to co-founder/partner. It helps us connect with product owners and internal stakeholders who are balancing competing priorities, political realities, and the weight of decision-making.

It’s empathy grounded in reality and it helps us show up with more patience, more precision, and better questions.

5. Closing the loop: walking the same path

Empathy isn’t a buzzword, it’s earned experience. By building our own products, we’ve lived the thrill of a launch and the fatigue of iteration.

We get that the dynamic of client (holding the 💰) and supplier is a powerful thing, and look, we’re a commercial entity so we have to make money (in a sensible and honest way) but this has made us far more aware of what it can be like on the other side of the table.

It’s made us better designers, better technologists, and better advisors. It’s helped us guide clients through uncertainty with more confidence and more respect for their constraints. And it’s reinforced a truth that sits at the core of how we work at Grade: that great digital products don’t just come from great ideas, they come from great empathy.