Market Segmentation,Positioning & GTM

CASE STUDY · ENTERPRISE SAAS · APR 2016 – AUG 2020

Scaling Enterprise SaaS to ₹10Cr: Product, GTM, and the Segmentation Playbook

How a market transition from on-premise to cloud became the catalyst for a complete GTM overhaul — reducing CAC by 34%, improving NPS by 22%, and delivering ₹10Cr+ in annual revenue.

01 · THE SITUATION

A market in transition — and a team caught flat-footed

When I joined Frontier Business Systems, the enterprise technology landscape was undergoing one of its most significant structural shifts in a decade: organisations were moving away from on-premise infrastructure toward cloud-based solutions. This wasn't a gradual evolution — it was a rapid redefinition of how IT budgets were allocated, how decisions were made, and who the buyers were.

The outreach team, which I was part of initially, had a front-row seat to the friction this created. Enterprise accounts that had been loyal for years were pushing back. Conversations that once centred on hardware refresh cycles and upfront licensing were now being met with questions about OpEx models, scalability, and vendor lock-in. The noise in the enterprise data was unmistakable: the market had moved, but our approach hadn't.

Two structural opportunities became clear early on. First, cloud infrastructure dramatically lowered the upfront capital expenditure for companies — particularly low and mid-market enterprises that had previously been priced out of enterprise-grade solutions. Second, organisations were struggling internally with policy changes and IT sunk cost management as they tried to justify legacy investments while evaluating new platforms. Both of these were pain points we could solve — but only if we changed how we positioned, segmented, and sold.

02 · WHAT WAS BROKEN

One product, one message — sold to everyone the same way

The core problem was a lack of segmentation. Frontier was approaching the enterprise market as a monolith: the same product, the same pitch, the same commercial structure — regardless of company size, maturity, or infrastructure readiness. This created three compounding issues:

•       High CAC from misaligned outreach: Sales cycles were long because we were pitching enterprise-grade solutions to companies that weren't ready for them, and pitching cloud-first narratives to organisations still defending their on-premise investments.

•       Poor retention signals: Without understanding the actual use case and paying capability of each segment, post-sale satisfaction was inconsistent. Customers who bought solutions that didn't fit their stage churned or disengaged, dragging NPS down.

•       Internal knowledge lag: As the market moved to cloud, our team's knowledge base didn't keep pace. We lacked the ability to articulate the specific business case for cloud adoption to different types of organisations — particularly around policy change and sunk cost management.

The result was a business that was generating revenue but leaving significant value on the table — both in acquisition efficiency and in long-term customer value.

03 · THE APPROACH

Segmentation as the foundation for everything else

The first decision was to stop treating the market as uniform. I led a segmentation initiative that divided our target organisations by two primary variables: headcount and office location. This wasn't arbitrary — headcount was a reliable proxy for infrastructure complexity and budget authority, while location indicated regulatory environment and IT maturity.

Once segments were defined, different products and positioning strategies were mapped to each segment. A mid-size company in a Tier 2 city had fundamentally different concerns from a large enterprise in Mumbai or Bengaluru — the former was focused on cost control and simplicity, the latter on scalability, compliance, and integration. We built distinct value propositions and demo narratives for each.

The second major initiative was rebuilding our OEM relationships. Frontier operated as a reseller and integrator across 8 SBUs, and the quality of our OEM partnerships directly affected our product credibility, knowledge depth, and margin structure. I led the evaluation and formalisation of these liaisons — pushing for MOU agreements, joint roadmap transparency, and structured knowledge transfer sessions. This addressed the internal knowledge lag directly: our team needed to be able to speak credibly about technology roadmaps, not just current features.

The third lever was visibility. Enterprise buyers don't just evaluate products — they evaluate vendors. Winning awards at IT summits and maintaining presence on major IT platforms wasn't vanity; it was pipeline. We prioritised participation in events where our target segments were making decisions.

04 · OKRS

The framework we built and tracked against

05 · THE FAILURE — AND THE PIVOT

We moved the market before we moved our team

The most significant failure of this period was not conducting an internal knowledge audit before launching the new GTM motion. We assumed the team could adapt to the cloud-first narrative through osmosis — by being in customer conversations and picking up the language. That assumption was wrong.

As we began pushing cloud-first positioning to enterprise accounts, the team lagged in its ability to articulate the specific business case: how cloud reduced total cost of ownership over three years, how it addressed IT sunk cost justification, and how policy changes at the CIO level were creating new buying centres. We communicated the features of new technology but not the organisational implications — which is what enterprise buyers actually needed to hear.

The consequence was that we had to pull back our financial targets for the year. The pipeline had been built on assumptions of faster conversion that the team's knowledge depth couldn't support. This was a direct and expensive lesson in sequencing: you cannot change market positioning without first building internal capability.

06 · BUSINESS IMPACT

What the segmentation and OEM strategy ultimately delivered

07 · WHAT I'D DO DIFFERENTLY

Point A matters as much as Point B

The single most important lesson from Frontier was about sequencing and situational awareness. My instinct — and the business pressure — was to move quickly toward the target state: a segmented, cloud-first GTM with strong OEM partnerships. But I underestimated how important it was to first understand Point A with rigour.

If I were to lead this initiative again, I would begin with a structured internal audit: what does the team actually know, what are the gaps against the new positioning, and what training or enablement needs to happen before we change the customer conversation? Market strategy and internal capability have to move together. When they don't, the market strategy stalls — not because it's wrong, but because the organisation can't execute it.

The second thing I'd do differently is instrument the feedback loop earlier. We were collecting signals from the market — pushback, objections, lost deals — but we weren't systematically feeding those back into the product and positioning. A structured win/loss review process from month one would have surfaced the knowledge gap faster and reduced the financial impact of the pivot.