SaaS launch plan

The Tekiz path to $10k MRR.

Tekiz is launching as a hosted routing control plane: generated API keys, quotas, fallback reliability, account analytics, and support for agent teams that want one OpenAI-compatible endpoint without handing over provider credentials.

Start API key setup Compare plans Estimate route value Reliability proof Community launch kit Founder sales kit Request managed-access beta View reliability

The public offer sells routing infrastructure, account management, API-key management, quotas, analytics, and reliability. Managed provider access is a separate guarded beta path, not a public pooled-provider entitlement.

MRR target

$10k

The first public SaaS milestone for hosted routing, billing, activation, and support.

Recommended mix

100/200/50

100 Lite, 200 Pro, and 50 Max customers produces $10,200 MRR.

Activation path

5 steps

Signup, paid routing, generated key, public-edge verification, and first routed request.

Plan ladder

Simple pricing, measurable conversion.

The plan mix is intentionally modest enough to sell founder-led while still proving self-service demand. Pro is the center of gravity; Max is the sales-led path for teams and high-volume automation.

Plan	Price	Included usage	Launch role
Lite	$6/month	10,000 requests/month, 60 rpm	Low-friction entry for individual agent experiments.
Pro	$30/month	50,000 requests/month, 180 rpm	Main conversion path for daily agent development.
Max	$72/month	200,000 requests/month, 600 rpm	Founder-led sales path for teams, automations, and private deployment support.

Conversion funnel

Every launch page should move users to a routed request.

Homepage, pricing, calculator, launch plan, and Gateway migration pages capture privacy-safe page-view and CTA intent.
Account onboarding tracks signup, plan selection, generated key creation, public-edge key verification, and the first browser-side sage-router/frontier request.
The private launch funnel ranks source/channel acquisition actions, activation bottlenecks, managed-access demand, and per-plan revenue actions without returning emails, prompts, keys, OAuth tokens, or raw responses.
Before traffic exists, the same funnel seeds launch actions for Gateway migration proof, GitHub builder traffic, pricing checkout proof, calculator qualification, and founder-led launch-plan outreach.
Support, troubleshooting, billing, and status pages are part of conversion because 401, 402, 429, and 503 errors must lead to a safe next step.

Managed access boundary

Capture demand before reselling model access.

The product can compete with provider-wrapper marketplaces without making an unsafe resale claim. Public plans remain BYOK/customer-authorized by default. Managed provider access requires provider resale terms, terms acknowledgment, provider-family allowlist, positive unit economics, a margin policy, durable quotas, durable operator audit events, and acceptable-use controls.

Join managed-access beta list Review resale boundary Review margin policy

Acquisition motions

Compete where router buyers already compare.

Gateway migration content for hosted-router shoppers.
GitHub and docs traffic converted into quickstart, pricing, and generated-key setup.
Discord/community activation help for first-request debugging.
Calculator-driven Pro/Max qualification for workflows with cost leaks, fallback needs, and human-review points.

Operator evidence

Track the real business, not vanity traffic.

/analytics/funnel reports estimated current MRR, target attainment, plan gaps, acquisition actions, zero-traffic launch seeds, and target-aware bottlenecks.
/edge/health reports public reliability evidence, auth mode, rate-limit posture, quota posture, generated-key revocation posture, and retry failover.
/admin/customers gives bounded operator review with secret-free audit events and without raw generated keys, key hashes, provider credentials, prompts, or raw provider responses.