The Demand-Based Pricing Pivot: HomeForge Pro
Type: case-study
Stage: Stage 3: Pricing Proof
Difficulty: advanced
HomeForge Pro slashed annual churn from 22% to 5% by abandoning fixed monthly fees and aligning pricing with customer job volume — proving that Pricing Proof isn't just about the number, it's about the model.
Overview
HomeForge Pro is a proptech SaaS built for seasonal home service contractors. The original pricing model was a fixed annual fee — straightforward for the vendor, but structurally misaligned with the customer's revenue reality. Contractors earned most of their income in spring and summer, and resented paying full fees through the slow winter months. The result was 22% annual churn. The pivot to demand-based pricing cut churn to 5% and drove the company to $50M ARR.
The problem
Seasonal contractors — landscapers, pool service companies, exterior painters, gutter cleaners — have a specific financial reality: income is not evenly distributed across the year. A landscaping company might do 80% of its annual revenue between April and October. The remaining four months are slow, cash-light, and operationally minimal.
A fixed annual SaaS fee, paid monthly at the same rate regardless of season, creates a specific friction point: in January, a contractor is paying the same software bill they paid in July, on a fraction of the revenue. This triggers a rational decision process — 'do I need this tool right now?' — and a significant percentage of those decisions result in cancellation.
HomeForge Pro's 22% annual churn was not a product quality problem. The customers who churned often returned in spring. The churn was a pricing model problem: the model asked customers to pay uniformly for a tool they used non-uniformly.
The pivot
The demand-based pricing model restructured the annual fee around customer usage patterns:
• 70% of the annual fee paid upfront — this gives the vendor revenue certainty and gives the customer a reduced per-month obligation during peak season
• 30% of the annual fee scaled to actual job volume — during peak months, contractors pay slightly more; during slow months, they pay less or nothing above the base
The model is not complicated to describe, but it is psychologically different to experience. A contractor paying $70 in January (low volume) and $130 in July (high volume) has a billing experience that matches their own revenue curve. They're not paying a fixed cost during a cash-light period — they're paying a cost that flexes with their business.
The outcome
Churn dropped from 22% to 5%. Renewal rates reached 95%. The company reached $50M ARR.
The unit economics improvement is significant: a company with 5% churn has an average customer lifetime of 20 years. A company with 22% churn has an average customer lifetime of 4.5 years. The revenue difference between those two scenarios — same acquisition cost, same pricing — is the entire difference between a business that compounds and one that runs to stay in place.
The $50M ARR outcome is a downstream result of the retention improvement. When churn is low, expansion and referral revenue compound on a stable base. When churn is high, every new customer partially replaces a lost one, and the business runs harder to stay in the same place.
The lesson
Pricing Proof isn't just about the number — it's about the model. A price that customers initially accepted can still destroy a business if the payment cadence is misaligned with their financial reality.
Demand-based pricing is one model for alignment; usage-based, outcome-based, and seasonal pricing are others. The underlying principle is the same: the customer should pay the most when they're getting the most value, and the least when they're getting the least.
For student founders building SaaS products for businesses with variable revenue — freelancers, seasonal operators, project-based businesses — the fixed monthly fee is the default pricing model, but not always the right one. The question worth asking at Stage 3 is not only 'what price will they pay?' but 'when will they pay it, and does that timing align with when the tool delivers value to them?'