August 11, 2026
8 min read
A framework for understanding where your company is, where it's going, and what it takes to get there.
Every company grows. Not every company builds the infrastructure to support that growth.
After years of working inside and alongside growth-stage companies, we have seen the same progression play out in different orders, at different speeds, and with different tools but with the same underlying pattern. The revenue side of the business gets people. The operational side gets tools. That imbalance is manageable at first and compounding by the time most companies notice it.
We call this the GTM Maturity Gap. Kayt defined what it looks and feels like from the inside in her blog. In a follow-up blog, we explored what triggers it and why it compounds. This blog gives you the map: four stages of GTM infrastructure maturity, where the dysfunction concentrates, and what it takes to move through it.
At this stage, the founder is the go-to-market motion. They sell. They are customer support. They handle escalations. They set up the tools, maintain the spreadsheets, and keep the institutional knowledge in their head.
Everyone on the team wears multiple hats because the company is small enough that it works. A team of under ten people can coordinate through shared context, Slack channels, and weekly standups. There is no formal process because the founder is the process.
This is not dysfunction. This is appropriate for the stage. The scrappiness that defines Stage 1 is the same thing that produced the product-market fit that allowed the company to grow.
The risk in Stage 1 is not that things are informal. It is that the habits and systems built at this stage get carried forward into stages where they no longer fit.
Something starts working. Revenue is climbing. The team is growing. And the instinct, the right instinct by the way, is to add resources to the functions most directly connected to growth.
The marketing person who was also qualifying leads and running events gets an SDR. Then the company adds an event coordinator. Then a second AE. Then a customer success hire. These decisions make sense. Revenue-generating roles have a clear return and that return shows up in the quarter it is made.
You know who does not get headcount at this stage.
The operations person who set up HubSpot is now managing HubSpot plus a customer portal plus a Salesforce instance plus the integration between them plus the spreadsheet reporting that leadership needs every Monday. The person who was doing invoicing, customer onboarding, collections, and expense approvals at Stage 1 is still doing all of those things. They have just added tool administration, data stewardship, and systems ownership to the list.
Revenue-generating roles get people. Operational roles get tools.
The tools are necessary. They fuel the growth that is happening. But each tool added without a coherent architecture underneath it is a small bet that someone will eventually figure out how it all fits together. That someone is an operations person. They are running out of capacity before the company runs out of growth.
The rise of AI coding agents is going to make this pattern worse before it makes it better. The instinct will be to give the operations person AI tools and expect them to do more with even less headcount justification. More automation, more integrations, more surface area, same one person. The operational debt does not go away because the tools got smarter. It compounds faster.
This is the stage where the bill comes due.
The tools work. The people work. But they do not work together. Marketing’s attribution platform does not agree with Sales’ pipeline view. Customer Success finds out about a renewal risk the same week the customer decides to leave. Leadership asks a simple question in a Monday meeting and gets four different answers depending on who is in the room.
None of this was planned. Nobody built it on purpose. It accumulated, quietly, while everyone was busy chasing growth.
The operational workarounds that were survivable at Stage 2 are now load-bearing. The spreadsheet that was a temporary fix is now the system of record. The integration that was hacked together by a contractor 5 years ago is now business-critical and nobody remembers how it works. The operations person who absorbed everything is either burning out or has already left, taking the institutional knowledge with them.
This is where operational debt becomes more dangerous than technical debt. Technical debt is visible. Someone can open the codebase and see it. Operational debt lives in undocumented processes, informal workarounds, and the heads of people who might not be there next quarter. You cannot audit what was never written down.
We will explore operational debt specifically in a future blog. But the most important thing to understand about Stage 3 is this: the earlier you address it, the cheaper it is to fix. Every month that passes adds another layer of complexity that has to be unwound before you can build something stable on top of it. This is not a problem that gets easier with time. It gets harder.
The companies that move through Stage 3 successfully are the ones that stop trying to outrun the dysfunction and start building the foundation underneath it. The ones that do not stay in Stage 3 longer than they should, or never fully get out.
Stage 4 is not a revenue milestone. It is an operational one.
A company enters Stage 4 when growth is supported by an operating environment rather than dependent on the heroics of individual people. The CRM is trusted. The forecast is reliable. A new executive can come in and get up to speed from documentation, not from tribal knowledge. When leadership asks a question, the data has an answer everyone in the room can agree on.
This is not perfection. Stage 4 companies still have problems. They still make bad tool decisions and accumulate debt in certain areas. The difference is that they have a foundation that can absorb those mistakes without crumbling. The system is resilient because someone built it to be.
The revenue operations motion at this stage is not reactive. It is designed. Demand flows from generation to close to payment with minimal manual intervention. The strategy is clear and execution is aligned to it across every function. When something breaks, there is a process for fixing it that does not depend on one person knowing where all the bodies are buried.
Note that the revenue ranges for Stage 3 and Stage 4 overlap intentionally. A company at $60M ARR could be in Stage 3 or Stage 4 depending entirely on whether they have built the foundation. We have worked with companies at $80M that are still running on instinct and tribal knowledge. We have worked with companies at $40M that are already operating with the discipline of a business twice their size. The stage is a condition, not a number.
We see companies at every stage of this maturity curve. The work we do most often lives in two transitions: late Stage 2 into Stage 3, and Stage 3 into Stage 4.
Late Stage 2 is where the operational debt starts accumulating faster than anyone realizes. The tools are multiplying. The operations team is outnumbered. The architecture underneath the stack was never designed, it just happened. The companies that engage with us at this stage tend to have the best outcomes because there is still time to build before the dysfunction becomes load-bearing.
Stage 3 is the most common place we find companies for the first time. Something broke, or a board member asked a question nobody could answer, or a new executive came in and said the systems are not good enough. By this point, the work is harder. There is more to unwind before there is anything to build. But it is still the right time, because the alternative is carrying Stage 3 dysfunction into a Stage 4 operating environment, which is where companies get stuck for years.
The move from Stage 3 to Stage 4 does not happen automatically. It requires someone looking across the whole operation, not just one function or one platform, and building the foundation that lets everything else work.That’s GTM Architecture. It’s the work we do at 28 North.
Platform-agnostic. Outcome-focused. Built for the stage you are in, not the stage a playbook assumes you should be in.
If you are reading this and recognizing your company in Stage 2 or Stage 3, the most useful thing we can tell you is this: the gap between where you are and where you want to be is not as wide as it feels. But it does not close on its own.
Not sure which stage you’re actually in? That’s usually the first sign you need someone looking across the whole operation, not just one function.