The four moments that tell you it's time
Most founders don't decide to invest in design because the logic convinced them. They decide because something specific happened. These four patterns show up before almost every decision.
Posted on:
May 25, 2026
Team:
André Sequeira
Categories:
Systems
The four moments that tell you it’s time
Most founders don’t decide to invest in design infrastructure because they read an article about it and agreed with the logic.
They decide because something happened. A specific moment made the problem impossible to ignore. And most of the time, they don’t even recognise it as a design problem when it happens. They call it something else: a slow sprint, a difficult hire, a lost deal, a gut feeling about the product.
These moments are not random. They fall into four patterns.
The enterprise buyer said something you can’t unhear
It might have been direct. “The product doesn’t look ready for our procurement team.” Or indirect: a longer-than-expected silence after a demo, a question about your UI during a security review, feedback that mentioned “professional presentation” in a way that felt like a warning.
You filed it away the first time. The second time, you started paying attention.
What it’s actually telling you: the gap between your science and your product has become visible to the people whose trust you need most. Enterprise buyers don’t have time to separate “the product looks unfinished” from “the company isn’t ready.” For them, it’s the same signal. The interface is the first argument for whether your data can be trusted.
Post-raise, the product suddenly looks like it belongs to a different company
You’ve been looking at this product every day for two years. Then you close your Series A, and you look at it again. With fresh eyes. And something has shifted.
The product didn’t change. What changed is what you’re now being compared to. Enterprise expectations are different at this stage. The investors around the table have seen more. And the product that looked fine six months ago now looks like it was built by a team still figuring things out, because in some ways, it was.
What it’s actually telling you: the standard moved. Not the product. The design debt that accumulated quietly during the build phase now has an audience that can see it.
A new hire named the problem in their first week
A senior designer joins, or a Head of Product comes on board. In their first week, they ask a question that sounds simple: “Do you have a design system?” When the answer is “we have some shared components somewhere,” they explain what that means in practice.
Suddenly you have a word for the friction you’ve been feeling for months.
What it’s actually telling you: the problem was always there. You just didn’t have the vocabulary for it yet. The new hire didn’t create the issue. They made the invisible visible.
A specific sprint broke in a way that made the cost impossible to ignore
A developer tells you they’ve rebuilt the same chart component three times this quarter. A feature that should have taken two weeks takes five, because half the time was spent making design decisions that should already be resolved. A handoff turns into a negotiation. A simple update requires a designer in the room for something that should be documented.
These things accumulate. And eventually, one of them tips you over.
What it’s actually telling you: the informal system your team built while moving fast has reached its limit. It worked when you were small. It doesn’t work anymore. The cost of inconsistency is now measurable in sprint capacity.
If you recognised yourself in one of these
The problem isn’t new. You’ve been carrying it for a while. What changes in the moment of recognition is that you can no longer pretend the timing isn’t right.
The question isn’t whether this needs fixing. The question is whether you’re going to address it before the next enterprise conversation, or after it.
If you want to understand exactly what’s going on before committing to anything, that’s what the Discovery Sprint is for. One week. A clear picture of what’s there, what’s missing, and what to do about it.
