Own Typst Document Generation API.

What you'd own.

Every artifact below transfers to your accounts on day one. The whole engine.

• ●Production Typst API backend with FastAPI and multi-tenant architecture
• ●Stripe billing engine with free tier and usage-based pricing
• ●Landing page, brand identity, and developer-focused messaging
• ●GTM playbook targeting Hacker News, Reddit, and Typst Discord communities
• ●API documentation, Python and JavaScript SDKs, developer portal
• ●Email and OAuth authentication system with team workspace management
• ●Financial model, unit economics, and operating playbook

What Roll Digital builds for you.

Custom scope to take Typst Document Generation API from MVP shell to operating business.

• ▸Production backend on FastAPI with Postgres and multi-tenant isolation
• ▸Stripe integration for free-to-paid conversion and usage-based billing
• ▸Email plus OAuth authentication with team and workspace management
• ▸API documentation, Python and JavaScript SDKs, developer portal
• ▸Custom domain provisioning and automatic SSL certificate management
• ▸Monitoring, observability, error tracking, and usage analytics dashboard
• ▸Customer onboarding guide and 30-day launch success support

Why this could work.

Free tier with generous limits attracts developers organically via Hacker News, Reddit, and Typst communities, creating network effects. Usage-based pricing aligns value with consumption. The 15k-team TAM is real and currently underserved. Typst adoption is accelerating in technical and academic sectors. Early-mover advantage in the hosted Typst API space before Typst GmbH or competitors consolidate.

What you'd risk.

Typst adoption remains early and niche; developers can self-host Typst in 20 minutes, creating structural resistance to willingness-to-pay. Typst GmbH, VC-backed and incentivized to build an official API, could capture this market instantly through brand search and network effects. HTML-to-PDF solutions are entrenched with high switching costs. Year 1 take-home is negative; breakeven requires 2-3 years minimum. Only 13% probability of meaningful success.

Who this fits.

Technical founder or SaaS operator with existing channels into engineering teams. Background in developer tooling, Rust, or CLI platforms preferred. Must commit 2-3 years to profitability and be comfortable building a community-driven business. Ideal candidate has shipped SaaS before, understands B2B GTM, and can bet on Typst adoption trajectory without external funding pressure.

Timeline.

From contract signing to operating business.

1. Day 1
   Receive backend code, landing page, GTM playbook, financial model
2. Week 1
   Deploy to production, validate infrastructure, provision custom domain system
3. Week 3
   Launch beta cohort, collect first usage data, validate unit economics
4. Week 6
   Public launch with free tier, community outreach campaign begins
5. Day 90
   Measure retention, CAC, LTV signals, plan paid tier rollout

Pricing.

Three ways in, depending on how much you want to build yourself.