How We Grow

Product-Led Growth

We don’t grow by outspending competitors on ads. We grow because the product is good enough that people tell other people about it.

Our growth model is simple:

1. Build something useful - solve a real pain point for AI engineers
2. Make it easy to try - free tier, no sales call required, 5-minute setup
3. Let usage drive expansion - teams start small, add seats and features as they see value
4. Word of mouth does the rest - engineers talk to engineers

Developer-First

Our primary audience is the engineer deploying AI agents. Not the VP of Engineering, not the CTO - the person writing the code. Everything we build, write, and ship should make that person’s life easier.

This means:

• Docs are a product - not an afterthought. If the docs are bad, the product is bad.
• The API is the interface - dashboards are nice, but the CLI and API are how real work gets done.
• Show, don’t sell - blog posts with real code, not whitepapers gated behind email forms.
• Respect their time - no dark patterns, no unnecessary meetings, no “let me loop in my manager.”

Content Strategy

We write about what we know. Our content serves three purposes:

1. Education - help engineers understand AI evaluation, observability, and guardrails
2. Transparency - share how we build our own product, including the mistakes
3. SEO - rank for the terms our users are searching for

What We Publish

Type	Cadence	Purpose
Technical blog posts	2-3/week	Deep dives on AI evaluation, tutorials, benchmarks
Changelog	Every release	What shipped and why
Handbook updates	Ongoing	Transparency about how we operate
Case studies	Monthly	Real customer stories with real numbers
Open source contributions	Ongoing	Libraries, tools, and datasets we release

What We Don’t Do

• Gated content (no email-for-PDF)
• Clickbait titles that overpromise
• “Thought leadership” that says nothing
• Paid influencer campaigns disguised as organic
• Aggressive retargeting

Developer Relations

DevRel at Future AGI is engineering, not marketing. Our DevRel team:

• Builds - contributes to open-source projects, writes SDKs, creates example apps
• Teaches - gives talks, runs workshops, writes tutorials
• Listens - spends time in communities, surfaces feedback to the product team
• Supports - helps users in Discord, GitHub issues, and Stack Overflow

DevRel success is measured by community health (active contributors, questions answered, integrations built) - not leads generated.

Metrics We Care About

• Weekly active evaluations - are people actually using the product?
• Time to first evaluation - how fast can someone go from signup to value?
• Net Promoter Score - would you recommend us?
• Organic traffic - are we earning attention?
• Community engagement - GitHub stars, Discord activity, contributions

We don’t optimize for vanity metrics (page views, social followers, email list size).