Own Typst Batch Rendering.

What you'd own.

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

• ●Landing page, domain, and brand identity for the service
• ●Customer list from beta launch and initial outreach
• ●Typst community playbook covering Discord, Reddit, GitHub Discussions
• ●Year 1 financial model and three-tier pricing strategy
• ●Production API codebase and cloud infrastructure setup
• ●Free-to-paid onboarding funnel with email sequences
• ●SEO playbook targeting 'typst pdf api' and adjacent queries

What Roll Digital builds for you.

Custom scope to take Typst Batch Rendering from MVP shell to operating business.

• ▸Production FastAPI backend with async job queue and PostgreSQL database
• ▸Stripe billing system across three pricing tiers with usage tracking
• ▸Email and Google OAuth authentication with per-customer isolation
• ▸Free tier rate limiter and paid tier usage monitoring dashboard
• ▸API documentation site with code examples in JavaScript and Python
• ▸Discord bot for community viral distribution in Typst ecosystem
• ▸30-day hands-on customer success program and technical support runbook
• ▸Production monitoring with error tracking and uptime alerting infrastructure

Why this could work.

Typst has 35k stars and growing production adoption. The 2,000-team TAM at $1,200 per year average spend is achievable through inbound channels: Discord and Reddit organically discuss PDF generation friction, and SEO for 'typst pdf api' captures high-intent developer search volume. Free-to-paid conversion in developer tools runs 5-10% when pricing is clear. Mid-range Year 1 ($42k ARR) proves PMF before hitting self-hosting friction or competitive threats.

What you'd risk.

Typst GmbH is VC-backed and shipping their own hosted API is the obvious next move. Self-hosting friction is nearly zero: Typst CLI is a single Rust binary, so price-sensitive teams just run it on a $6 per month VPS. TAM ceiling is real. Even 50 percent market share yields only $1.2M ARR, barely sustainable long-term. You're racing against a well-funded competitor with native distribution, and the technical barrier to churn is trivial.

Who this fits.

Solo founder or small agency owner with existing distribution in developer communities or SEO expertise. You've shipped SaaS before and understand free-to-paid conversion mechanics. You're comfortable with the 10 percent success odds and have runway to operate at a loss for six months. Non-technical skill is optional if you hire first, but business instinct and community credibility in Typst or adjacent tool ecosystems are critical.

Timeline.

From contract signing to operating business.

1. Day 1
   Receive domain, codebase, customer list, financial model, playbooks
2. Week 1
   Production API deployed, Stripe billing active, beta customers onboarded
3. Week 3
   SEO content published, Discord campaign launched, free tier live
4. Week 6
   First paid customer acquired, email nurture running, docs complete
5. Day 90
   Year 1 traction validated or pivots assessed, scale decision point

Pricing.

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