Founder sales kit

Turn high-intent routing conversations into Lite, Pro, and Max activation.

Use these no-secret snippets for direct founder-sales follow-up. Every link uses measured founder-sales attribution, keeps provider-custody boundaries explicit, and routes prospects toward Lite pilots, generated-key activation, OpenRouter migration, Max implementation review, or calculator qualification.

Create API key Start Lite pilot Request Max review One-subscription review Estimate workflow fit

Copy the next action first

Use this when the launch funnel shows zero outreach or setup copies. Start with the short recommended reply for a warm thread, then use the full revenue packet or one focused reply when the prospect asks for implementation detail.

Tekiz may fit your agent/model routing work if you want one OpenAI-compatible endpoint with health-aware fallback, generated Sage keys, and route profiles for frontier/local/coding traffic.

Fastest path:
1. Create a Pro generated key, then verify /v1/models:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=next-revenue-packet

2. Copy the 60-second setup:
https://tekiz.ai/quickstart?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=next-revenue-packet

If this is a production/team workflow, request Max implementation review:
https://tekiz.ai/managed-access?intent=max-implementation&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=next-revenue-packet#managed-access-quick-form

If you want one-subscription simplicity, use managed-access review instead of assuming public bundled resale is enabled:
https://tekiz.ai/managed-access?intent=one-subscription&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=next-revenue-packet©_open=1#managed-access-direct-contact-primary

Boundary: Tekiz is routing, generated-key, quota, analytics, and reliability infrastructure for provider/local access you are authorized to use. Public managed-provider access remains gated behind provider authorization, terms, cost model, unit economics, quotas, and acceptable-use controls.
Tekiz may fit your agent routing work if you want one OpenAI-compatible endpoint with health-aware fallback, model routing, and hosted generated keys.

Start by creating the sk_sage key, then verify /v1/models before wiring it into an agent:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=hero-pro-reply

60-second setup:
https://tekiz.ai/quickstart?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=hero-pro-reply
Preview the setup bundle 
# Tekiz hosted setup
# 1. Create your generated key:
# https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=hero-setup-bundle
# 2. Replace the placeholder below with the one-time sk_sage key.

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_sage_your_key_here
export SAGE_ROUTER_MODEL=sage-router/frontier

curl "$OPENAI_BASE_URL/models" \
  -H "Authorization: Bearer $OPENAI_API_KEY"

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"sage-router/frontier","messages":[{"role":"user","content":"Route this well"}]}'

Use for direct replies

Send these only in direct founder-sales contexts: replies, DMs, warm intros, support follow-up, or managed-access qualification.

No-secret boundary

Do not paste prompts, provider credentials, OAuth tokens, generated API keys, cookies, raw provider responses, customer data, or private operator dashboard data into outreach.

Measured links

Every CTA uses utm_source=founder-sales, utm_medium=direct, and utm_campaign=sage-router-launch so conversion can be measured without identity leakage.

Copyable Lite pilot reply

If you want to try Tekiz without committing a production workflow, start with the Lite pilot.

Lite is the low-friction hosted path: create the sk_sage key first, verify /v1/models, then checkout unlocks routing for a small agent or evaluation workflow.

Start Lite key setup:
https://app.tekiz.ai/account.html?plan=lite&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=lite-pilot-reply

Quickstart:
https://tekiz.ai/quickstart?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=lite-pilot-reply

Boundary: this is hosted routing, account, quota, analytics, and reliability infrastructure for provider/local access you are authorized to use. It is not bundled model resale.

Copyable Pro activation email

Subject: one Tekiz key for your agent model routing

Saw your routing/failover work and thought Tekiz might be useful.

It gives agent tools one OpenAI-compatible endpoint, then routes by task, model capability, provider health, latency, and policy. The hosted Pro path creates a generated sk_sage key first, so you can verify /v1/models and copy setup before wiring it into an agent.

Pro activation:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=pro-activation-email

60-second quickstart:
https://tekiz.ai/quickstart?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=pro-activation-email

Boundary: Tekiz is routing infrastructure for provider access you already control. It does not ask you to paste provider keys into public channels and does not advertise bundled model resale.

Copyable Max implementation DM

If you are routing agent traffic across multiple providers or local/Tailnet models, Tekiz's Max path may be a better fit than self-serve Pro.

The Max review is for implementation help around route policy, provider health, credential boundaries, quotas, and failover. It also keeps managed-provider access explicitly gated behind provider authorization, terms, unit economics, and acceptable-use controls.

Request Max implementation review:
https://tekiz.ai/managed-access?intent=max-implementation&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=max-implementation-dm#managed-access-quick-form

Pricing context:
https://tekiz.ai/pricing?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=max-implementation-dm

Copyable gateway migration reply

If the pain is "we have too many model gateways / provider configs", the migration path is straightforward:

1. Point OpenAI-compatible clients at Tekiz.
2. Keep BYOK/provider credentials on the router side.
3. Use route profiles for frontier, local-first, or coding-agent traffic.
4. Let the router handle health-aware failover, 429 retries, and modality capability checks.

Gateway migration guide:
https://tekiz.ai/docs/gateway-migration?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=gateway-migration-reply

OpenRouter comparison:
https://tekiz.ai/compare/openrouter?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=gateway-migration-reply

Copyable OpenRouter migration reply

If OpenRouter is working for broad remote catalog access, keep it available. The Tekiz migration is about adding a policy layer around your own authorized routes, local/Tailnet models, generated Sage keys, quotas, and health-aware failover.

Start with the OpenRouter comparison and copy the 60-second migration setup:
https://tekiz.ai/compare/openrouter?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=openrouter-migration-reply

Create the generated Tekiz key:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=openrouter-migration-reply

Boundary: OpenRouter can remain a BYOK/OpenAI-compatible provider route behind Tekiz. Tekiz is not selling bundled OpenRouter resale or claiming marketplace replacement breadth.

Copyable calculator follow-up

If you want to sanity-check whether Tekiz is worth adding, use the calculator before you create an account.

It estimates workflow fit from request volume, fallback gaps, human review points, and routing complexity, then recommends Lite, Pro, or Max without asking for prompts or provider credentials.

Model routing calculator:
https://tekiz.ai/model-routing-calculator?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=calculator-followup

If the score points to Pro, create the generated key here:
https://app.tekiz.ai/account.html?plan=pro&start=create_key&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=calculator-followup

Copyable one-subscription review reply

If you want one subscription instead of bringing every provider account yourself, use the managed-access review path rather than public checkout.

Tekiz can qualify the workflow, target provider family, request volume, and commercial preference now. Public managed provider access stays disabled until provider authorization, terms acknowledgment, an authorized provider-family allowlist, a private cost model, unit economics, quotas, audit events, and acceptable-use controls all pass.

Request one-subscription review:
https://tekiz.ai/compare/openrouter?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=one-subscription-review©_open=1#openrouter-managed-access-copy-open

Managed-access review fallback:
https://tekiz.ai/managed-access?intent=one-subscription&utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=one-subscription-review©_open=1#managed-access-direct-contact-primary

Provider and margin boundary:
https://tekiz.ai/provider-resale-terms?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=one-subscription-review
https://tekiz.ai/margin-policy?utm_source=founder-sales&utm_medium=direct&utm_campaign=sage-router-launch&utm_content=one-subscription-review

Founder-sales operating rule

Use one snippet per conversation, then wait for the prospect's reply. Do not batch-send identical outreach, and do not include private funnel metrics, customer identities, prompts, provider credentials, generated API keys, OAuth tokens, cookies, or raw provider responses.