GrowthOS targets three distinct personas, each representing a different phase of the go-to-market strategy. The primary persona drives Phase 1 revenue. The secondary persona drives upsell to the Scale tier. The tertiary persona unlocks Phase 3 channel expansion.
This is the day-one customer — the person who feels the tool-sprawl pain most acutely and has the authority (and urgency) to act on it.
| Attribute | Detail |
|---|---|
| Company size | 5-50 employees |
| Role | Founder, Head of Growth, or Growth Lead — often wearing 3+ hats |
| Engineering resources | One part-time developer allocated to growth engineering (at best) |
| Current tool count | 6-10 disconnected growth tools |
| Current tool spend | $200 - $800/mo ($2,400 - $9,600/yr) |
| Integration debt | 10-20 engineer-weeks of brittle custom wiring |
| Decision speed | Can decide in one meeting — no procurement committee |
| Success metric | ROI visible in the first week |
This persona represents the upsell path — they discover GrowthOS through the Launch tier and grow into the Scale tier ($149/mo) as their needs mature.
| Attribute | Detail |
|---|---|
| Company size | 50-200 employees |
| Role | Head of Growth or Growth Manager with a dedicated team |
| Team size | 3-5 person growth team |
| Current tool spend | $800 - $2,000/mo ($9,600 - $24,000/yr) |
| Key need | Visual journey builder, advanced analytics, team collaboration |
| GrowthOS tier | Scale ($149/mo) |
| Decision process | 1-2 week evaluation, needs buy-in from VP Engineering |
| Capability | Launch Tier | Scale Tier |
|---|---|---|
| Contacts | Up to 5,000 | Up to 50,000 |
| Journey builder | Basic automation rules | Visual drag-and-drop builder |
| Analytics | Standard dashboards | Custom funnels + cohort analysis |
| Team seats | 2 | 10 |
| Support | Community + email | Priority email + onboarding call |
| API rate limits | Standard | 5x higher |
This persona is a Phase 3 expansion target — unlocked when GrowthOS adds WhatsApp Business API support and India-first payment integrations.
| Attribute | Detail |
|---|---|
| Company size | 20-500 employees |
| Region | India-first, expanding to Southeast Asia |
| Primary channel | WhatsApp (90%+ open rate vs 18% for email) |
| Key need | WhatsApp lifecycle messaging, UPI payment triggers, regional compliance |
| GrowthOS opportunity | WhatsApp module (Phase 3) + India payment integrations |
| Market context | India has 500M+ WhatsApp users; it is the default business communication channel |
| Metric | Typical Performance |
|---|---|
| Open rate | 15-25% |
| Click rate | 2-5% |
| Response time | Hours to days |
| Reach in India | ~30% of target audience |
| Metric | Typical Performance |
|---|---|
| Open rate | 90%+ |
| Click rate | 15-25% |
| Response time | Minutes |
| Reach in India | 95%+ of target audience |
For Indian fintech and e-commerce companies, email-only growth tools are fundamentally inadequate. WhatsApp is not a nice-to-have — it is the primary channel. GrowthOS Phase 3 addresses this by integrating WhatsApp Business API as a first-class channel alongside email, with the same unified contact graph and automation engine.
Knowing who you do not serve is as important as knowing who you do. GrowthOS deliberately excludes three segments.
Enterprise 500+ Employees
Companies with 500+ employees typically need enterprise-grade tools like Braze, Iterable, or HubSpot Enterprise. They have dedicated growth engineering teams, established vendor relationships, and procurement processes that favor established enterprise vendors. GrowthOS does not compete here — and does not need to.
Consumer Apps (B2C)
Consumer applications — social networks, gaming, media — have fundamentally different growth mechanics: viral coefficients, network effects, content loops. GrowthOS is built for B2B SaaS growth patterns: trials, onboarding, activation, expansion revenue, and referral programs. The mental models are different.
Analytics-Only Teams
Teams that need deep product analytics without growth execution should use PostHog, Amplitude, or Mixpanel directly. GrowthOS includes analytics as a supporting capability, not a primary one. If your only need is “understand what users do,” you do not need GrowthOS — you need an analytics tool.
How do we know GrowthOS is working for these personas? Four measurable outcomes:
| Criterion | Target | How We Measure |
|---|---|---|
| Integration time | < 30 minutes | Time from sign-up to first event received |
| ROI visibility | First week | Time to first measurable outcome (email sent, referral tracked, NPS collected) |
| Tool replacement | 3+ tools replaced | Self-reported in onboarding survey + tool-spend reduction |
| Engineering burden | 50%+ reduction | Hours/week spent on growth tool maintenance (pre vs post) |