Growth idea action plan
MCP server before custom agent
Expose the product through an MCP server first so developers can use it in their own agent workflows before you invest in a full in-app agent.
Why this can grow a startup
A full agent can hide whether users truly want agentic help or just easier product access. An MCP server gives technical users an immediate way to pull the product into real workflows, while giving the product team a cleaner demand signal. It also avoids overbuilding UI and orchestration before the company knows which agent jobs people repeat often enough to deserve a native surface.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where mcp server before custom agent can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the AI Search and Developer Tools channel.
- Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
PostHog says its MCP server was used as much as PostHog AI for some creation flows, with 34% of AI-created dashboards coming through MCP and 18% of all dashboards created that way in one observed week.
Source: PostHog Newsletter (newsletter.posthog.com)
GrowthDex source hub: PostHog Newsletter
Last checked: 2026-05-26
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Layered context injection for AI answers same source · 2 shared channels · 1 shared stage
- AI install wizard for 90-second setup same source · 1 shared channel · 1 shared stage
- Task-based model routing for AI speed same source · 1 shared channel · 1 shared stage
- Async AI workflows with cached retries same source · 1 shared channel · 1 shared stage
Related GrowthDex essays
- AI products stop feeling smart when they hide their context AI products, product-led growth, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory