ProjekinAja. Founder's Playbook Stage 3 · Revenue Architecture Lesson 3.1
● Stage 3 · Lesson 3.1

Business Model Archetypes

Most founders choose a business model by accident or imitation — here is the framework for choosing deliberately.

⏱ ~22 min read 💰 Revenue design 🧮 Stage milestone

🎯 By the end you'll understand

The seven B2B business model archetypes — SaaS, usage-based, marketplace, transactional, services-wrapped-in-software, hardware plus recurring software, and data/licensing — and the structural mechanics that distinguish them: gross margin range, cash flow profile, sales motion implications, and scaling characteristics. You'll also understand the two failure modes most specific to the wrong model choice, and use the Business Model Selector to map Forge's customer behavior to archetype fit scores and a 24-month cash flow simulation.

KEY INSIGHTA business model is structural — not cosmetic

Revenue is a design decision, not an afterthought. The model you choose in the first 90 days of Stage 3 will constrain every downstream decision — hiring, fundraising, pricing, sales motion, unit economics — for the life of the company.

Most technical founders pick a business model by one of three methods: (1) copying the model of a company they admire, (2) defaulting to "SaaS" because everyone else does, or (3) letting the first customer's contract structure become the template. All three are accidents dressed up as decisions. The business model is not how you charge — it is the structural logic that determines your gross margin ceiling, your cash conversion cycle, your sales cycle length, your scaling leverage, and your capital requirements. Getting the model wrong is as lethal as getting the product wrong, and it is significantly harder to fix after the fact.

🔑 The core move of Stage 3

Before you set a price, before you write a contract, before you hire a sales rep — answer this: which archetype most closely matches the structural reality of how your customers derive value from what you build, and what that implies for your gross margin and growth curve? Revenue architecture is the technical discipline of matching your charging mechanism to your value delivery mechanism. When they are misaligned, you either leave money on the table or you destroy your own unit economics.

CORE CONCEPTSeven archetypes, seven structural realities

The seven archetypes below cover the vast majority of B2B software-adjacent business models. They are not exclusive — hybrid models are common — but every successful B2B business is anchored in one primary archetype. The anchor determines the structural mechanics. Hybrid elements are overlays on top of the anchor, not replacements for it.

1 · SaaS (Subscription Software)
Gross margin 70–85% Predictable ARR High churn risk

Customer pays a flat recurring fee (monthly or annual) for access to software. Value is continuous — the software runs whether or not the customer actively engages. Revenue is highly predictable; COGS is mostly hosting, support, and infrastructure. The critical structural requirement: customer value must be continuous, not episodic. If the customer only needs the product four times a year, SaaS pricing creates a value gap — they are paying for 12 months of access to use 4. That gap produces churn, discount pressure, and justification-of-renewal fights. SaaS works when daily or near-daily usage is the norm, or when the product is deeply embedded in workflow.

2 · Usage-Based (Consumption Pricing)
Gross margin 55–75% Low barrier to start Unpredictable revenue

Customer pays for what they consume — API calls, messages sent, compute hours, units processed. Revenue scales automatically with customer usage, which aligns the charging mechanism tightly with delivered value. The structural tradeoff: revenue becomes variable, making forecasting harder and investor narratives more complex. Usage-based works best when (a) usage is highly variable across customers, (b) customers are sensitive to paying for idle capacity, and (c) your COGS actually scales with usage. The failure mode: if your costs do not scale proportionally with usage, heavy users can destroy your gross margin.

3 · Marketplace
Gross margin 60–80% Network effects Cold start problem

You facilitate transactions between two sides — buyers and sellers — and take a percentage or flat fee per transaction. Revenue scales with GMV (gross merchandise value), not with your own sales effort. The structural challenge is the cold start problem: neither side joins an empty marketplace. Once solved, marketplace dynamics are self-reinforcing. In B2B, true marketplaces are relatively rare; the model is more often confused with a platform or a distributor. A marketplace requires genuine two-sided participation — you are not the seller, you are the facilitator.

4 · Transactional (Per-Event Fee)
Gross margin 30–60% Scales with customer activity Revenue tied to volume

Revenue is generated per discrete transaction — per contract processed, per document analyzed, per shipment managed. Unlike usage-based, which bills for resource consumption, transactional billing charges for business outcomes. The gross margin is typically lower than pure SaaS because transactional businesses often have meaningful per-transaction costs (compliance, processing, review). The structural advantage: revenue scales directly with customer business activity, making the product feel more like a variable cost than a fixed overhead — which can actually make it easier to sell.

5 · Services-Wrapped-in-Software (Managed/Professional)
Gross margin 20–50% High ACV Does not scale as software

The software is the delivery mechanism, but humans do the work. Implementation, configuration, ongoing management, and analysis are delivered as a service enabled by proprietary software. Gross margin is structurally capped by headcount costs. Revenue can be very high per customer, but scaling requires hiring rather than deploying code. The critical diagnostic: if removing the software would not meaningfully increase your costs, you are in this archetype regardless of what you call yourself. Many early-stage startups are here and do not know it — they think they are SaaS, but every new customer requires significant professional services hours.

6 · Hardware Plus Recurring Software
Blended gross margin 40–65% High switching cost Hardware margin often negative at small scale

Physical hardware generates a one-time (or amortized) revenue event; the recurring software layer generates ongoing ARR. The value proposition of the hardware is often durable only if the software is embedded — this creates the switching cost moat. The structural failure mode: hardware margin is often negative at small scale (or marginally positive only after years of volume). If the hardware gross margin is negative, you are paying customers to adopt your product — which feels like growth but is actually a unit economics crisis. The model only works if the LTV of the software subscription materially exceeds the hardware margin deficit, and you have the capital to fund the gap.

7 · Data / Licensing
Gross margin 75–90% High margin ceiling Requires proprietary data moat

Revenue comes from licensing proprietary data or intellectual property to customers who embed it in their own products or processes. Gross margins are extremely high because once the data asset exists, distribution is nearly zero-marginal-cost. The structural requirement: you must own data that customers cannot easily replicate or acquire elsewhere. Without a genuine data moat, this archetype devolves into custom data services — which has the economics of services-wrapped-in-software. The failure mode is building a data business before you have data that is both proprietary and continuously valuable.

HOW IT WORKSStructural mechanics — the four dials that matter

For each archetype, four structural mechanics drive all the downstream consequences: gross margin range, cash flow profile, sales motion requirements, and scaling characteristics. You do not get to choose these — they are structural outputs of the archetype you pick.

Archetype Gross Margin Cash Flow Profile Sales Motion Scaling Logic
SaaS 70–85% Predictable; upfront annual = positive; monthly = delayed Land-and-expand; CSM-driven retention Software leverage; headcount decoupled from revenue at scale
Usage-based 55–75% Variable; follows customer activity cycles Product-led or low-friction sales; PLG expansion Scales with customer growth, not new customer acquisition
Marketplace 60–80% Transaction-driven; delayed until GMV matures Two-sided; supply and demand acquisition simultaneously Network effects; platform leverage above critical mass
Transactional 30–60% Lumpy; tied to volume events Integration-heavy sales; often API-first Scales with customer transaction volume
Services + Software 20–50% Milestone-based; often large upfront Consultative; relationship-driven; long cycle Headcount-constrained; professional services model
Hardware + Recurring 40–65% blended Negative at deployment; positive over LTV horizon Proof-of-value pilots; hardware team required Requires inventory financing; supply chain complexity
Data / Licensing 75–90% Highly predictable; often prepaid Enterprise deals; legal-heavy; long negotiation Zero marginal cost per additional licensee
90% 70% 50% 30% 10% SaaS 70–85% Usage 55–75% Mkt 60–80% Transact 30–60% Svc+SW 20–50% HW+SW 40–65% Data 75–90% Gross margin ← Forge
Gross margin ranges by archetype. Hardware + Recurring Software (Forge's anchor) has a blended ceiling of 65% — achievable at scale but starting well below that during early deployment when hardware margin may be thin or negative.

The gross margin ceiling is not aspirational — it is structural. A services-wrapped-in-software business cannot reach 80% gross margins without fundamentally changing its delivery model. A data licensing business should not tolerate 40% margins without examining whether its cost structure is broken. When you see a company with gross margins significantly outside the archetype range, either they have a structural problem or they have built a genuine moat that changes the cost curve. Both are worth investigating.

💡 The margin diagnostic test

Add up every cost that would go to zero if you served zero customers next quarter: hosting, support, processing, hardware COGS, customer success headcount. Divide by revenue. That ratio, subtracted from 1, is your gross margin. If it is lower than the floor for your archetype, you have a cost problem. If it is higher than the ceiling, check that you are attributing all variable costs correctly — misclassifying COGS as operating expenses is common in early-stage companies and produces an inflated margin picture that collapses during due diligence.

SEE ITBusiness Model Selector — map Forge to the right archetype

⚙ Interactive · Business Model Selector & 24-Month Revenue Simulation

Answer 10 questions about Forge's customer behavior and value delivery. The widget maps your answers to fit scores for each archetype and renders a 24-month cumulative revenue simulation showing how each model's cash flow profile differs at the same customer acquisition rate. Then toggle between models to see the downstream implications.

Archetype fit scores (based on your answers)
24-month cumulative revenue — toggle to compare archetypes
Model selected
SaaS
Month-24 cumulative revenue
—
Implied gross margin
—
Cash flow profile
—
📊 Model insight

Select a model above to see the structural insight.

A few things to notice in the simulation. At the same acquisition rate of 2 customers per quarter, the hardware-plus-recurring model starts with lower early revenue (because some value is deferred into the recurring stream) but produces higher total LTV by month 18–24 due to the compounding annual contract. Pure SaaS without hardware compresses the sales cycle but requires the customer to see software value on its own — difficult for a hardware-embedded product where the edge sensor is the data source. The services model produces high ACV on paper but its gross margin math makes it structurally unscalable past 8–10 customers without a major team expansion.

FORGEModel locked — and why

By the end of Stage 3, Forge has closed two pilots and converted them to annual contracts. The model is locked: annual SaaS platform fee of $30K plus a one-time hardware fee of $12K per site. Here is the reasoning behind each structural choice, and what it implies going forward.

1

Annual SaaS platform fee — $30K ACV

The primary archetype is Hardware + Recurring Software. The $30K annual platform fee is the SaaS layer — it covers the software dashboard, AI inference pipeline, anomaly detection updates, and customer success. Charging annually (not monthly) was a deliberate choice: it improves cash flow, reduces churn risk, and signals enterprise commitment from the buyer. Monthly billing for an enterprise hardware deployment creates an implicit "cancel anytime" message that undermines long-term integration. At $30K ACV, two contracts produce $60K ARR — real revenue, not a pilot.

2

Hardware fee — $12K one-time per site

The edge vision sensor hardware is priced at $12K per site deployment. This is a one-time fee, not a recurring lease. The reasoning: hardware leases require sophisticated billing infrastructure and create financing liability for an early-stage company. The one-time fee keeps the COGS model simple and transfers ownership to the customer, which increases switching costs (they own the hardware; replacing it means both a hardware write-off and a software migration). At current stage, Forge's hardware margin is thin — component cost plus integration labor is approximately $9K, producing a $3K gross margin per site, or 25%. This is below the healthy range for the archetype. The path to healthy hardware margin is volume-driven component cost reductions — achievable at 20+ sites, but a cost management priority until then.

3

The unit economics model

With two customers, the gross margin model shows 61% blended. Here is the math: Customer 1 — Year 1 revenue: $42K ($30K SaaS + $12K HW). COGS: $9K hardware + $2K hosting/support + $5.5K implementation = $16.5K. Gross margin: $25.5K / $42K = 60.7%. The path to 75%+ gross margin at 20 customers runs through three levers: hardware component volume discounts (target: $6.5K at 20 sites), reduced implementation cost (first two customers required extensive custom integration — template-based deployments should cut this to $2K), and higher ACV per customer via multi-site expansion (each additional site adds $30K SaaS + lower hardware margin, improving the blended rate).

4

CAC, LTV, and payback

CAC of $18K represents the fully-loaded cost of acquiring one customer at this stage: 0.5 AE-months + 1 implementation engineer-week + travel + demo hardware. LTV is computed using a 5-year capped retention model at early churn assumptions: approximately $165K from the software layer (consistent with Stage 3's unit economics baseline). Payback period uses the correct formula: CAC ÷ (monthly gross profit) = $18K ÷ ($25.5K gross profit / 12 months) ≈ 8.5 months on the blended first-year economics, or roughly 10 months on software gross profit alone. A common error is dividing CAC by monthly revenue instead of monthly gross profit — that would give a misleadingly short payback of ~5 months, understating true capital recovery time. These are strong early indicators — but they rest on the churn assumption. If churn reaches 25%, LTV drops materially and the model still works but compresses. Stage 3's job is locking the model; Stage 5's job is proving the retention number.

🔑 Why not pure SaaS for Forge?

The temptation to call Forge a "SaaS company" and ignore the hardware is real — it would command higher valuation multiples and simpler investor narratives. But it would be structurally dishonest: the software has no data without the edge sensor. A Forge customer who cancels the software but keeps the hardware sensor gets no value. A Forge customer who cancels the hardware loses the data source. The two are inseparable, which means the model must be designed around their integration. Pretending to be pure SaaS would mean subsidizing hardware as a sales cost, destroying the gross margin you need for the business to work. Better to own the archetype correctly and build the margin model that makes it work at scale.

WEAKNESSWhere this bites

✗ SaaS fails when customer value is episodic

The most common misapplication of SaaS pricing is applying it to a product where customer value events are infrequent. If a customer uses your product intensively for two months to solve a specific problem, then barely touches it for the remaining ten months of the annual contract, you will face a renewal conversation where they correctly argue they have not gotten $42K of value. Episodic value is real value — but the model that captures it is either usage-based, transactional, or project-based. Forcing episodic value into a flat annual subscription creates a structural misalignment that manifests as churn, discount pressure, and stalled expansion. The diagnostic question: if you logged each customer's activity over 12 months, would you see 200+ distinct value events, or 3–5 significant ones? SaaS requires the former.

✗ Hardware plus recurring fails when the hardware margin is negative

Negative hardware margin is not a rounding error — it is a structural tax on every unit of growth. If Forge's edge sensor costs $14K to produce and deploy and is sold for $12K, every new customer makes Forge $2K poorer before the software subscription generates a dollar. With 20 customers acquired in 24 months, that is $40K of capital consumed by hardware margin deficit, on top of CAC and operating expenses. The cash burn profile becomes deeply nonlinear, and the sales motion creates a perverse incentive: closing more customers accelerates the cash crisis. Hardware margin must be tracked as a separate line item — not buried in COGS and rationalized as "acceptable for now." The acceptable answer is a specific timeline to positive hardware margin at a specific volume milestone, with the capital plan to fund the gap until that milestone.

✗ Choosing the model based on investor narrative, not structural fit

Some founders reverse-engineer the business model from the multiple they want to command in fundraising. "SaaS companies trade at 8–15x ARR, so we are SaaS." This produces a company that calls itself SaaS but has service-level gross margins (because the founders did not change the delivery model to match the label). During Series A due diligence, the gross margin gets scrutinized — and 42% gross margins on a company claiming SaaS multiples is a yellow flag that turns red as soon as the investor models the path to 80%. Build the model that actually fits your structural economics, then raise on the honest multiple for that model. A well-run hardware-plus-recurring company with 62% gross margins growing 150% year-over-year is a far more fundable story than a self-described SaaS company with 42% gross margins that the investor needs to mentally reconstruct during diligence.

KEY INSIGHTHow this connects

  • Problem/Solution Fit (2.9) — you proved in Stage 2 that Forge's product resolves the specific problem customers have with their current inspection workflow. The business model you choose here is the structural mechanism for capturing a fraction of that value as revenue. The solution fit determines what customers are willing to pay for; the model determines how you charge for it. Both must be correct for the economics to work.
  • Value-Based Pricing (3.2) — the next lesson takes the archetype chosen here and builds the pricing logic on top of it. You cannot set a value-based price without knowing the structural model, because the model determines whether you charge per seat, per site, per event, or per outcome. The $30K ACV Forge landed on is not a guess — it is the output of value-based analysis applied specifically to the Hardware + Recurring archetype.

Revenue architecture does not end with the archetype choice. Stage 3 continues through packaging, contract structure, and gross margin management — each of which layers constraints on top of the archetype decision you make in this lesson. Getting the archetype right is the prerequisite; every subsequent Stage 3 decision is building on top of it.

GLOSSARYKey terms introduced

Business model archetype
A structural template for how a business captures revenue relative to the value it delivers. The archetype determines gross margin ceiling, cash flow profile, sales motion, and scaling logic — it is not interchangeable with pricing strategy.
Gross margin
Revenue minus cost of goods sold (COGS), divided by revenue. COGS includes all costs that scale directly with serving customers: hosting, hardware, support, implementation. Gross margin measures the structural profitability of the product itself, before operating expenses.
ACV (Annual Contract Value)
The annualized recurring revenue from a single customer contract, excluding one-time fees. For Forge: true ACV = $30K (software platform fee only). Year-1 revenue per customer = $42K ($30K ACV + $12K one-time hardware deployment fee), but only the $30K is ACV — the hardware fee does not recur at renewal. Confusing ACV with blended Year-1 revenue overstates ARR and misleads investors. ACV is the primary unit metric for B2B enterprise sales.
LTV (Lifetime Value)
The total gross profit a customer generates over the duration of the relationship. The infinite-horizon formula is (Annual Gross Profit) / (Annual Churn Rate); a 5-year capped variant is used when early churn data is thin and infinite retention is implausible. At Forge's Stage 3 baseline: approximately $165K using 5-year implied retention at early churn assumptions. Note: using an inflated gross margin input (e.g., 91%) or ignoring the finite horizon inflates LTV — use the margin derived from your actual COGS stack.
CAC (Customer Acquisition Cost)
The fully-loaded cost to acquire one new customer: sales headcount time, marketing spend, implementation costs, and any trial/demo hardware costs. Forge's current CAC is $18K. The LTV/CAC ratio of approximately 15:1 indicates healthy unit economics at this stage.
Payback period
The number of months required for the gross profit from a customer to recoup the CAC. Formula: CAC ÷ (ACV × Gross Margin ÷ 12). Forge's payback is approximately 8.5 months on blended first-year economics ($18K ÷ ($25.5K/12)), or roughly 10 months on software gross profit alone. A common error is dividing CAC by monthly revenue rather than monthly gross profit — this understates payback by the inverse of gross margin (~1.65× for Forge). Payback under 12 months is generally considered strong for B2B enterprise.
Hardware margin
The gross margin on the physical hardware component of a hardware-plus-recurring model: (hardware revenue − hardware COGS) / hardware revenue. Forge's current hardware margin is approximately 25% ($3K gross on $12K revenue). Positive but below target; 40%+ at volume is the structural goal.
Blended gross margin
The weighted-average gross margin across multiple revenue streams in a hybrid model. Forge's blended margin of 61% in Year 1 reflects the blend of lower-margin hardware ($3K on $12K = 25%) and higher-margin software ($25.5K on $30K = 85%). As software revenue dominates over time, the blended margin rises.

ACTIVE RECALLCheck your understanding

Answer in your own words first, then reveal.

1Why would SaaS pricing fail for a product where customers use the software intensively for 2 months and lightly for 10? What model would better match that value pattern?›

SaaS pricing requires continuous customer value to justify a flat subscription — the customer is paying for ongoing access, and if they only derive value episodically, they will correctly feel overcharged for 10 months of the year. At renewal, they will either negotiate aggressively on price or churn. The structural mismatch produces discount pressure and retention problems regardless of product quality. Better models for episodic value: usage-based pricing (charge only when they consume the product), transactional pricing (charge per event or outcome), or project-based pricing (charge per project engagement). The key diagnostic is the frequency and distribution of value events: SaaS requires many value events per month; anything less needs a different mechanism.

2Forge's hardware margin is currently 25%. What is the specific danger if this remains negative at scale — and what is the mechanism by which it destroys the business?›

A 25% hardware margin is positive (not negative), but the concern in the lesson is the risk of it turning negative — or remaining too low to support the economics. If hardware margin is negative, every new customer deployment makes the company poorer before a dollar of software revenue is recognized. The mechanism: assume hardware cost is $14K and hardware price is $12K — a $2K loss per site. At 20 sites in year 2, that is $40K of capital destroyed by the sales motion itself. Combined with CAC, implementation costs, and operating expenses, the cash burn rate becomes nonlinear with growth: faster growth = faster cash consumption = earlier cash crisis. This is the "growth trap" — closing more customers accelerates the runway problem rather than solving it. The fix is either raising hardware price (if customer tolerance exists), reducing component COGS through volume purchasing, or restructuring the model to include a hardware lease that amortizes the cost over the contract term.

3What is the difference between ACV and LTV, and why do both matter for evaluating whether Forge's model is structurally sound?›

ACV (Annual Contract Value) is the annualized recurring revenue from one customer — Forge's true ACV is $30K (software platform fee only; the $12K hardware fee is one-time and does not recur at renewal). Year-1 revenue per customer is $42K, but ACV = $30K. LTV (Lifetime Value) is the total gross profit over the entire customer relationship — for Forge, approximately $165K using 5-year implied retention at early churn assumptions. It measures the long-term economic value of acquiring and retaining a customer. Both matter for structural soundness: Year-1 revenue of $42K vs. $18K CAC = 2.3× in year 1 alone. LTV/CAC ≈ $165K / $18K ≈ 9× — strong if churn holds. Payback period: $18K CAC ÷ ($25.5K first-year gross profit / 12 months) ≈ 8.5 months. The model is structurally sound if these ratios hold under realistic churn scenarios — the vulnerability is the churn assumption, which Stage 5 must validate with actual retention data.

4A founder describes their company as "SaaS" to investors but actually has 42% gross margins. Why is this a problem — and what is the correct response?›

SaaS businesses are expected to achieve 70–85% gross margins at scale. If a company labels itself SaaS but runs at 42% gross margins, there is a structural mismatch between the label and the economics. During due diligence, investors will model the path to scale and notice that 42% gross margins cannot support the operating cost structure of a software company (typically 50–70% of revenue going to sales, marketing, and R&D). The valuation multiple implied by a "SaaS" label — 8–15x ARR — assumes the gross margin profile improves to 70%+. If it cannot (because the delivery model requires significant human labor or hardware), the multiple is unjustified and the funding conversation collapses. Correct response: own the archetype honestly. If the business is "services-wrapped-in-software" or "hardware-plus-recurring," describe it that way and build the narrative around a realistic path to 60–65% blended margins, not an implausible SaaS multiple. Investors who understand the business correctly are better long-term partners than investors who discover the mismatch during their Series A diligence.

Next: pricing based on value, not cost — the only pricing that survives →