The current average GTM stack of a European seed-stage startup runs between 8 and 12 tools. Half of them don't talk to each other.
Each tool showed up to fix something specific. A CRM to store contacts. An email tool because the CRM wasn't enough. An enrichment tool because the contacts were incomplete. The stack piled up week after week, without anyone ever deciding what it should look like.
According to a benchmark published by Najar based on the real usage of over 180 European companies, the smallest structures struggle the most with this sprawl, running twice as many tools per employee as large organizations.
The result is always the same. A pipeline no one can explain. Customers come in, but no one really knows from where.
The problem is never the number of tools
Take a five-person fintech team in Antwerp doing outbound. It has a CRM, a tool to send sequences, a tool to find emails. Three tools, and the leads still slip through the cracks between them. The email goes out, the reply lands in an inbox the CRM never sees, the rep follows up with someone who already signed elsewhere. That's not a tool shortage. It's that the three don't share the same information.
Teams that get acquisition right start from the opposite end. They don't pick tools, they design a flow. An analysis of outbound campaigns documented by GTM Engineering shows reply rates around 10%. Not thanks to a miracle tool, but because each step triggers the next automatically: a signal spotted, a profile enriched, a message personalized, a follow-up scheduled. The same tool, plugged into a deliberate system or stacked at random, doesn't produce the same result.
What GTM tools does a seed-stage startup actually need? The question most co-founders ask is the wrong one. The real question is in what order, and with what data flow.
What a pipeline you can't read actually costs
Ruben Dominguez, who writes the newsletter The VC Corner, describes the scenario well. The founder copies cold email templates seen on LinkedIn. Starts a blog because someone said content works. Tests five channels at once because another startup did. Three months pass, the budget has melted, and there's still no reliable way to find customers.
How do you structure acquisition without a sales team? By treating it as an architecture, not a shopping list. A fragmented stack doesn't just produce incomplete data. It produces decisions made on incomplete data. And that difference shows up directly in the numbers an investor checks first: where customers come from, how much each one costs, which ones stay.
Build in layers
The logic that holds always follows the same order. First the foundation: a CRM that works, email and calendar plugged into it, a simple analytics tool. Nothing else until data flows cleanly between those three points. That's where the pipeline becomes readable for the first time.
Then comes execution: outbound if the strategy is outbound, marketing automation if it's inbound. Not both at once when you're five people.
The mistake almost every co-founder without a technical background makes is jumping straight to the layer above. Lead scoring, enrichment, personalization at scale. These tools amplify what already exists. Laid over a shaky pipeline, what they mostly amplify is the mess.
Nightborn comes in before the first subscription. We start by looking at what's already there, we map what talks to what, and we hand over an architecture with a clear installation order.
By the end, the co-founder has a document they can put on the table in front of an investor: here's how we find customers, here's what feeds what, here's what we measure. That's what our Product Discovery approach lays out, before any technical decision.
A fragmented stack doesn't grow with the startup. It gets more complicated. And that fork happens before the first tool, never after.
.webp)