The 5 to 500 software team segment

There is a strange thing about the AI tool landscape in 2026. The conversation is dominated by two extremes.

On one end, you have consumer AI: ChatGPT, Claude, Perplexity. These tools sell to individuals or get pulled into companies through bottom up adoption. They are priced for individual users and optimized for individual productivity.

On the other end, you have enterprise AI: Glean, Microsoft Copilot, Atlassian Rovo. These tools sell to large enterprises with dedicated procurement functions, established budgets, and IT led buying processes.

What is missing is the middle. The 5 to 500 software team, which describes roughly 200,000 companies globally, has no good options. Consumer AI tools do not capture team level intelligence. Enterprise AI tools are priced and sold for organizations 10x their size.

This article is about why that gap exists, why it is structural rather than accidental, and what it means for the next wave of AI tools.

The size band reality

Let me walk through what each company size actually needs and what is available to it.

Under 5 people.This is the founder cohort. At this size, the team coordinates by talking to each other. Everyone is in every conversation. Institutional memory lives in the founders’ heads. They do not need AI knowledge tools because they do not have an institutional memory problem yet. They need productivity tools (ChatGPT for writing, Cursor for coding) but not coordination tools. This is the consumer AI market.

5 to 50 people.This is where institutional memory starts breaking. The team has grown past the point where everyone is in every conversation. Decisions get made in subteams. Knowledge starts living in specific people’s heads. Senior employees become “the only person who knows X.” But the company is still too small to afford enterprise tools. Glean is structurally out of reach. Notion AI helps inside Notion but does not span the stack. There are no good options.

50 to 200 people. This is where the problem becomes acute. Multiple subteams, multiple workstreams, real institutional knowledge that needs to be preserved. Some senior employees are starting to leave. New employees take 60 to 90 days to become productive. The team is large enough to value AI knowledge tools but still too small for enterprise pricing. Notion AI is too narrow (only works inside Notion). Glean is too expensive. This is where the gap is most painful.

200 to 500 people.This is the transition zone. Some companies in this band have grown into Glean’s economics. Others still find it too expensive or too sales led for their culture. Many in this band are trying to evaluate Glean alternatives because the floor pricing has become a real friction point.

500 to 2000 people.This is mid market enterprise. Glean’s economics start to make sense. There is a dedicated IT or operations function that can drive procurement. Microsoft Copilot becomes viable if the company is on the Microsoft stack.

2000+ people. This is enterprise proper. The companies Glean was built for. They have CIOs, procurement teams, established AI vendor relationships. The buying process accommodates large starting contracts.

The 5 to 500 band sits in the middle, with 200,000+ companies globally, and almost no tools built specifically for it.

Why incumbents cannot serve this segment

This is not an accident. The structural reasons are specific and worth understanding.

Glean’s minimum floor is not pricing greed; it is GTM economics. Glean has built a sales led, AE driven, enterprise focused company. They have account executives, customer success managers, implementation engineers, and a paid POC process. The unit economics of that GTM motion require a large annual contract value to support the headcount required to close and onboard each customer. Lowering the floor would require rebuilding the entire company. Not the product: the company.

Microsoft Copilot’s bundling lock in. Copilot requires Microsoft 365 commitment. Most companies in the 5 to 500 software band have made deliberate choices to leave Microsoft for Google Workspace, Slack, and the modern stack. Copilot is not an option for them without re platforming, which is not going to happen.

Atlassian Rovo’s Atlassian Cloud requirement. Rovo only works if your team is on the Atlassian stack (Jira, Confluence, Bitbucket). Most modern software teams have moved off Atlassian to Linear, Notion, and GitHub. Rovo has no data foundation for these teams.

Notion AI’s single tool limitation. Notion AI is excellent at making your Notion workspace smarter. It does nothing for cross tool intelligence. A team whose decisions happen across Slack, GitHub, Linear, and Notion gets value from Notion AI for one quarter of their work. The rest stays uncaptured.

The result: the 5 to 500 software team segment has tools for individual productivity (ChatGPT, Cursor, Notion AI), tools for individual tool intelligence (Notion AI inside Notion), but nothing built for team level intelligence across the modern stack.

The structural opportunity

The math of this segment is real.

There are roughly 200,000 software companies globally in the 5 to 500 person band (depending on definition; this is a rough estimate based on funding databases, employer reporting, and SaaS market analysis).

Notion has demonstrated that the modern software team is a real buyer. Glean has demonstrated that enterprises will pay for AI knowledge tools. What is missing is the product purpose built for the band where these two trends intersect: software teams running on the modern stack who cannot afford enterprise tools and cannot get the coordination layer from consumer products.

What this segment actually needs

Talking to teams in this band over the past year, the same five requirements come up.

1. Self serve onboarding. No paid POC. No procurement cycle. No sales call required. They want to try the product, see it works, and start paying. Standard SaaS motion, not enterprise sales motion.
2. Works across the modern stack. Linear, Notion, GitHub, Slack, Google Workspace. The tools they have already chosen. Not the tools they might migrate to.
3. Team level intelligence, not per user. They have already given every employee ChatGPT or Cursor. What they need is shared institutional memory. A company brain, not another individual AI.
4. Trust positioning that survives a security review. They do not have a dedicated CISO, but the head of engineering will eventually evaluate whether the tool can pass a basic security review. No training on customer data, permission inheritance, audit logging.
5. Fast time to value. No two month implementation project. Setup in 30 minutes. Useful within a week.

These five requirements describe what Pulse is built to deliver. Not by accident, but by deliberate segment selection.

Closing: the segment bet

Pulse made a specific bet about which segment to serve. We could have gone enterprise. Glean and others have demonstrated that buyers exist there. We could have gone consumer or per user. Notion AI has demonstrated that path.

We chose the 5 to 500 software team segment because it is underserved, the math is real, and the product requirements (self serve, cross stack, team level, trust positioned) align with our architectural choices.

If you are at a software company in this band, you have probably felt the gap we are describing. You cannot afford Glean. You do not want to migrate to Microsoft or Atlassian for Copilot or Rovo. Notion AI helps inside Notion but does not help across your stack.

Pulse is built for you. The demo is live at pulsehq.tech, walkable end to end without signup. If the segment positioning rings true, we are probably the right fit.