# Temporal Financial Model Workflow orchestration platform that makes distributed applications fault-tolerant and reliable by abstracting away state management, timers, retries, and queuing. - Canonical: https://finamodel.com/startups/temporal - Excel download: https://finamodel.com/startup-models/temporal.xlsx - Category: Dev Tools - Model type: SaaS ARR / Valuation - Funding round: Series A - Funding: $18.75M - Founded: 2021 - Geography: US-based (San Francisco references in demo UIs); global OSS community. - Customer: B2B ## About the company Temporal is a workflow orchestration engine that makes distributed applications reliable by managing state, storage, timers, retries, queues, and failure recovery. Developers write workflow functions while Temporal guarantees completion through crashes, replacing a complex stack of routing, consensus, load balancing, storage, and streaming components. The product evolved from Uber’s Cadence project and was open-source only at the deck stage. Its planned commercial path was a hosted managed service priced by workflow usage, with self-hosted enterprise licensing still an open question. Community adoption and developer evangelism are the funnel rather than a mature sales model. Uber had more than 100 apps running on Temporal or Cadence, with Slack, Box, Coinbase, HashiCorp, DoorDash, Checkr, and Fortune 100 companies named. No revenue or paying-customer metrics are disclosed. The model should forecast developers, workflows, cloud conversion, enterprise contracts, infrastructure cost, expansion, and churn. ## What's included - 5-year monthly revenue build with stage-appropriate growth assumptions - Full P&L, headcount plan, and operating-expense schedule - Cash-flow statement, runway, and burn-rate tracking - Valuation via exit multiple with a DCF cross-check - Returns analysis with MOIC and IRR - Unit economics including CAC, LTV, payback, and cohort retention ## Product & value proposition Temporal is a workflow orchestration engine that hides the complexity of building reliable distributed applications. Without Temporal, engineers must manually implement state machines with persistent storage, timers, retries, and failure recovery - a large and error-prone surface. Temporal abstracts all of that: the developer writes a workflow function; Temporal guarantees it runs to completion, survives crashes, and handles timeouts. Core infrastructure components replaced / unified: routing, sharding, consensus, load balancing, queueing, timers, storage, streaming, rate limiting. Positioned as replacing a stack of tools (Redis, RabbitMQ, MySQL, Amazon S3) with a single platform. Temporal is a fork/evolution of Uber's open-source "Cadence" project; the founding team built Cadence at Uber. ## Revenue model - Primary future model: **hosted managed service** (cloud SaaS) - Temporal runs the cluster; customers pay for usage. - At deck time: open-source only; hosted service was the planned 2020 launch milestone. - Secondary (implied): on-prem / self-hosted enterprise licensing was flagged as an open question. - Distribution channel: developer-led / community-led (open-source adoption → convert to hosted cloud); evangelism and market education explicitly called out as investment areas. ## Traction & metrics - Uber: 100+ apps running on Temporal/Cadence - Slack: 900 (unit unclear - likely workflows or internal apps) - Named customers: Uber, Slack, Box, Coinbase, HashiCorp, DoorDash, Checkr, plus 3 unnamed Fortune 100 companies - Customer testimonials: Checkr (Ben Jacobson) and Snap (Steven Sun) - No revenue figures, ARR, MRR, growth rates, or paying-customer counts disclosed. ## Competition / moat - Competitive context shown via a timeline of prior workflow/orchestration tools since 2004: AWS SWF, AWS Step Functions, Azure Durable Functions, Apache Airflow, Conductor (Netflix), Cadence (Uber) - Temporal positioned as the latest and most capable. - "Today" stack (Redis + RabbitMQ + MySQL + S3) shown as the status quo Temporal displaces. - Moat sources (implied, not stated): OSS community lock-in from Cadence lineage; Uber internal validation at massive scale (100+ apps); developer experience as a differentiator (DX investment area); network effects from open-source ecosystem. - No explicit competitive moat slide. ## Team & funding ask / use of funds - Team: Not explicitly shown. Cadence/Uber provenance implied by slide 13 (Uber Cadence presentation by Temporal team). - Runway target: 3 years. - Use of funds / investment areas: - Hosted service build-out - Community: developer experience, evangelism, open-source improvements - People growth: 3x headcount by EOY 2020, 10x by 2021 - Product and Engineering - On-prem offering (under consideration) ## Recommended financial model - **Archetype + why:** OSS-to-Cloud SaaS (usage-based ARR model). Temporal follows the HashiCorp/Confluent/CockroachDB playbook: free OSS drives adoption → hosted cloud converts high-value users → enterprise on-prem as optional upsell. Revenue will be driven by workflow execution volume on the hosted service once it launches. A 3-statement model is premature given pre-revenue stage; a bottoms-up SaaS ARR + runway model is the right fit. - **Forecast horizon & granularity:** Monthly for years 1–2 (2020–2021, the active hiring/product build phase); quarterly for year 3. 3-year total horizon aligned with stated runway target. - **Key drivers & assumptions:** - OSS community size (GitHub stars/forks as leading indicator) - OSS → hosted cloud conversion rate - Average hosted workflows per customer per month - Price per workflow execution or per compute-hour - Headcount ramp: 3x EOY 2020, 10x 2021 - Avg fully-loaded cost per engineer - Hosting / infrastructure COGS as % of cloud revenue - Enterprise / Fortune 100 deal size - Community-to-trial conversion driven by evangelism spend - **Scenarios (Base / Bull / Bear - which variables flex):** - Bear: hosted service delayed past 2020, slow OSS community growth, headcount ramp slips to 2x. - Base: hosted service launches mid-2020 per roadmap, conversion rates at low end, 3x headcount EOY 2020. - Bull: hosted service attracts Fortune 100 pipeline from named logos; on-prem enterprise upsell layer adds ARR; 10x headcount by 2021 justified by revenue. - Flex variables: OSS→cloud conversion rate, enterprise ACV, time-to-first-revenue, headcount ramp pace. - **Required sheets / outputs:** 1. Assumptions - all drivers in one place with Base/Bull/Bear toggles 2. Headcount & Opex - hiring plan (eng, product, GTM, community) × loaded cost 3. ARR Bridge - OSS users → trials → paid cloud seats/usage; monthly cohort view 4. Revenue & COGS - cloud hosting revenue, gross margin build-out 5. P&L (simplified) - burn rate, EBITDA 6. Cash & Runway - starting cash (implied by raise) vs. monthly burn; 3-year runway check 7. Dashboard - KPIs: ARR, customer count, gross margin %, monthly burn, runway months ## Frequently asked questions ### Is the Temporal financial model free? Yes. The Temporal model is a free Excel download with live formulas. ### Can I change the assumptions? Yes. The workbook is editable and its live formulas recalculate when assumptions change.