How Much Does a Family Tree Software Owner Make? Year 5 Revenue $698M
A family tree genealogy software owner can plan around a $140,000 CEO salary in this model, but early distributions are not supported by the numbers EBITDA is negative in Year 1 at -$803,000 and Year 2 at -$187 million, with breakeven in Month 26 By Year 5, the model reaches $698 million in revenue and $441 million in EBITDA before taxes, debt service, reserves, and reinvestment These are researched planning assumptions, not guaranteed owner earnings
Owner income$140kNet margin-244% to 63%Revenue for target pay$221kBusiness difficultyHard
Want the six income drivers?
1
Paid Users
$329K-$6.98M
More paid users drive most of the profit lift, with revenue rising from $329K in Year 1 to $6.98M in Year 5.
2
ARPU Pricing
$23-$37
A weighted monthly ARPU shift from $23 to $37 lifts revenue per subscriber and speeds payback.
3
Retention Churn
High
If churn stays low, each paid user pays back longer, but no fixed churn rate means this lever stays a big swing factor.
4
Acquisition Cost
$45-$35
CAC improves from $45 to $35, so each new customer costs less and leaves more cash for profit.
5
Tech Costs
19.5%-17.0%
Combined variable costs ease from 19.5% to 17.0% of revenue, which expands contribution margin.
6
Staffing Load
6-19 FTE
Payroll scales from 6 to 19 FTE, so headcount discipline is a major guardrail on owner cash.
Want to test your owner pay?
Owner income calculator
Estimate owner take-home and the target-pay gap from revenue, margin, costs, reserves, and target pay. Churn stays editable because this model does not provide a fixed churn rate.
!
Planning note: Research-based planning estimate only. It is not guaranteed salary, tax advice, or owner distribution advice. Churn is an editable sensitivity because the model does not provide a fixed churn rate.
Want to see owner income in the full model?
The dashboard shows revenue, EBITDA, cash, breakeven, payback, and owner income, while the assumptions tab covers pricing, sales mix, conversions, CAC, marketing, COGS, variable costs, payroll, fixed costs, and capex. Open the Family Tree Genealogy Software Financial Model Template to test lean, base, and growth cases.
Owner-income model highlights
Owner income at a glance
Revenue and EBITDA charts
Scenario test by case
What costs reduce genealogy software owner income?
For Family Tree Genealogy Software, the biggest income killers are the costs tied to each subscriber and the $15,000/month fixed load. In Year 1, cloud hosting and data storage can eat 80% of revenue, archive data fees 50%, payment fees 35%, and affiliate commissions can rise from 30% to 50%, which is why a plan like How To Write A Business Plan For Family Tree Genealogy Software? has to model margin carefully. Product complexity, media uploads, record integrations, privacy work, and support tickets can turn decent subscription sales into thin owner pay.
Gross margin drag
80% hosting and storage in Year 1
60% hosting and storage by Year 5
50% archive data fees, then 30%
35% payment fees, then 30%
Operating expense pressure
$15,000/month fixed overhead
Payroll, marketing, support, cybersecurity
Development costs rise with complexity
Support tickets cut owner pay fast
How many paid users does a genealogy software business need?
Family Tree Genealogy Software does not have one universal paid-user target. At $23/month weighted ARPU, or $276/year, covering the $140,000 owner salary alone takes about 507 average paid users, and the Year 1 cost base of about $965,000 points to roughly 4,300 paid users to break even on revenue. By Year 5, weighted ARPU rises to $37/month, or $444/year, and the $698 million modeled revenue implies about 15,700 average paid-user equivalents; conversion rate, churn, CAC, and plan mix still decide the real count.
Year 1 math
$23 monthly ARPU
$276 yearly ARPU
507 users for salary alone
4,300 users for Year 1 costs
Year 5 scale
$37 monthly ARPU
$444 yearly ARPU
$698 million modeled revenue
15,700 paid-user equivalents
How much can a family tree software founder take home?
A Family Tree Genealogy Software founder can take $140,000 pre-tax salary from launch only if funding covers the planned cash losses; for setup logic, see How To Write A Business Plan For Family Tree Genealogy Software?. No practical owner distributions exist in Year 1 or Year 2 because EBITDA is -$803,000 and -$187 million.
Founder Pay
Plan salary: $140,000 pre-tax
Requires funding through early losses
No Year 1 distributions
No Year 2 distributions
Cash Reality
Year 1 EBITDA: -$803,000
Year 2 EBITDA: -$187 million
Breakeven lands in Month 26
Month 25 cash low: -$2016 million
Key Takeaways
Paid users drive revenue from 1,200 to 15,700.
Weighted ARPU rises from $23 to $37.
Retention matters because churn compounds as spend scales.
CAC must stay below lifetime value as costs rise.
Owner income scenario comparison for family tree software
Owner income scenarios
Owner income moves from salary-only in Year 1 to breakeven pay in Year 3 and distribution capacity in Year 5 as CAC falls and EBITDA rises.
Salary-only, breakeven, and scale-case owner income paths.
Scenario
Low Caseearly-loss
Base Casebreakeven
High Casemature-scale
Launch model
Owner income stays at salary-only levels while the business is still loss-making.
Owner income opens up once the model reaches breakeven and starts throwing off cash.
Owner income can expand into distributions when scale is strong and reserves are set aside.
Typical setup
Year 1 revenue is $329,000, CAC is $45, marketing is $120,000, contribution margin is about 80.5%, and EBITDA is -$803,000, so the owner draw is limited to the funded $140,000 CEO salary.
Year 3 revenue reaches $2,025,000, CAC is $40, marketing is $450,000, contribution margin is about 81.7%, and EBITDA is $1,024,000, so pay can move beyond salary.
Year 5 revenue reaches $6,976,000, CAC falls to $35, marketing is $1,200,000, contribution margin is about 83.0%, and EBITDA is $4,410,000, creating room for distributions after reserves.
Cost drivers
CAC $45
$120,000 marketing
5.0% trial conversion
12.0% paid conversion
-$803,000 EBITDA
CAC $40
$450,000 marketing
6.0% trial conversion
14.0% paid conversion
$1,024,000 EBITDA
CAC $35
$1,200,000 marketing
7.0% trial conversion
16.0% paid conversion
$4,410,000 EBITDA
Owner income rangeBefore owner reserves
$140,000Salary only
$1,024,000Post-breakeven
$4,410,000Reserve distributions
Best fit
Use this to test the early-loss case and the minimum owner pay needed before profits show up.
Use this for a realistic owner pay plan once the business is past break-even and can support profit draws.
Use this to test mature-scale upside, where owner income depends on disciplined reserve policy and steady growth.
!
Planning note: These scenario ranges are researched planning assumptions, not guaranteed earnings, salary promises, tax advice, or distributions.
Family Tree Genealogy Software Core Six Income Drivers
Paid user volume
Paid subscriber volume
More paid subscribers drive the main revenue lift. In this model, free users matter only when they move through the funnel, with visitor-to-trial conversion of 50% to 70% and trial-to-paid conversion of 120% to 160%. The implied average paid-user equivalents rise from about 1,200 in Year 1 to about 15,700 in Year 5, so owner income depends on how many users keep paying each month.
Here’s the catch: if support, storage, and acquisition costs rise faster than subscriber revenue, profit gets squeezed even when headcount grows. That means paid volume is not just a top-line metric; it also sets the pace for cash flow, gross margin, and how much the owner can safely draw.
Track paid conversion, not raw signups
Measure the funnel in three steps: visitor to trial, trial to paid, and paid-user equivalents. That shows whether growth is real revenue or just cheap traffic. The key test is whether each new paid customer covers support, storage, and acquisition cost after discounts and plan mix are included in weighted ARPU.
Watch paid conversions by channel.
Track storage and support per user.
Test offers against weighted ARPU.
Cut channels with weak payback.
Staffing and owner role
Founder role and staffing load
Owner income swings with who does the work. If the founder writes code or handles support, cash stays in the business longer, but the role is stretched. Year 1 payroll already totals $665,000: a $140,000 CEO, two $125,000 senior engineers, a $135,000 data scientist, an $85,000 marketing manager, and a $55,000 customer success rep.
By Year 5, the team reaches 19 FTE (full-time equivalents), including 5 engineers and 6 support reps. That means owner pay comes from profit after maintenance, security, AI infrastructure, and support, not from stripping out every dollar left at month-end.
Keep the owner role tight
Track three inputs: founder hours by task, payroll by function, and support volume per rep. If the founder is still the main coder or support lead, keep that time visible in the forecast so you do not overstate free cash.
Cap owner draw after reserves.
Forecast engineering and support headcount.
Keep a maintenance cash buffer.
Review payroll before hiring specialists.
The simple rule: only pay out profit that is left after ongoing product work and customer care are funded.
Customer acquisition efficiency
Customer Acquisition Efficiency
Owner income depends on buying paid users below lifetime value (LTV). In this model, CAC improves from $45 in Year 1 to $35 in Year 5, while annual marketing spend climbs from $120,000 to $12 million. That makes wasted traffic expensive fast. Genealogy search intent is narrow and competitive, so each click has to earn its keep.
The key inputs are visitors, trial sign-ups, trial-to-paid conversion, and CAC by channel. The model assumes trial-to-paid conversion rises from 120% to 160%, which helps offset paid spend. If acquisition cost rises faster than LTV, cash flow tightens and owner pay gets squeezed even if revenue keeps growing.
Track CAC by channel
Measure CAC for paid search, content, affiliates, and direct traffic separately. Compare each channel to LTV, not just first-month revenue. If a channel brings cheap clicks but weak trial-to-paid conversion, cut it quickly. For this kind of software, content and affiliates matter because intent is specific and competition is tight.
Watch three numbers weekly: cost per trial, trial-to-paid conversion, and payback period. As spend moves toward $12 million, small conversion losses hit cash flow hard. Tighter keyword targeting and better landing pages protect owner income more than adding spend.
Track CAC by source.
Kill weak keywords fast.
Raise trial-to-paid conversion.
Pricing and ARPU
Pricing and ARPU
Owner income improves when price matches the real load from storage, sync, privacy, collaboration, and research features. Here’s the quick math: Year 1 weighted ARPU is $23/month, then it rises to $37/month by Year 5 as the mix shifts to higher tiers. ARPU means average revenue per paid user, so list price alone does not tell you what the business actually earns.
If price sits below storage and support cost, the owner’s draw gets squeezed. The inputs that matter are paid users, plan mix, discounts, and the cost to serve each account. One simple rule: higher realized price usually means more cash left for payroll, tools, and owner pay, but only if support and data costs stay in line.
Measure ARPU by plan mix
Track realized revenue per paid account, not sticker price. Split it by tier so you can see whether the mix is moving toward higher-value users or being dragged down by discounts and lower plans.
Paid users
Plan mix
Discounts
Storage and support load
If ARPU rises but support tickets or storage costs rise faster, owner pay still compresses. Keep the price floor above service cost, and test upgrades around family sharing, extra storage, and collaboration so the higher tiers earn their keep.
Gross margin and technical costs
Technical cost load
This driver is the direct cost of serving each subscriber: cloud hosting, storage, data licensing, archive access, payment processing, and affiliate commissions. In the model, cloud hosting and storage fall from 80% to 60% of revenue, data licensing and archive access from 50% to 30%, payment processing from 35% to 30%, and affiliate commissions rise from 30% to 50%.
Here’s the quick math: combined variable load still moves from 195% to 170%, so technical costs can wipe out contribution before payroll. Large trees, media uploads, record integrations, and security work need to be priced into paid plans, or owner pay gets squeezed even when subscriber revenue grows.
Price heavy usage
Track this by plan tier and by usage. The key inputs are paid users, ARPU (average revenue per user), storage per account, record pulls, upload volume, payment mix, and affiliate share. If higher-value users create more files and searches but don’t pay more, gross margin falls.
Cap free storage growth.
Charge for heavy trees.
Test price on archive access.
Forecast fees every month.
A simple check: if a cohort’s technical load stays above 170% of its revenue, it is not funding payroll or owner draw. Raise prices for large trees and media, or trim costs on hosting, archive access, and payment fees before scaling acquisition.
Retention and churn
Retention and churn
Retention protects recurring revenue because family trees, media, and notes get more valuable over time. In this model, churn is a sensitivity, not a sourced benchmark, and users may cancel after they finish one research milestone. Renewal income has to come from ongoing records, collaboration, storage, and family sharing, or monthly revenue gets thin fast.
Here’s the quick math: a small retention slip matters more as marketing spend scales from $120,000 to $12 million. Weak retention makes acquisition payback harder even when trials convert, because each canceled account cuts the lifetime value that was supposed to fund growth and owner pay.
Improve renewal value
Track retention by cohort, plus family-tree growth, media uploads, notes added, storage use, and family-sharing invites. Those signals show whether the product has become part of the user’s ongoing record or just a one-time project.
Reduce milestone churn by tying paid value to ongoing work: saved records, collaboration, storage, and shared access. If users only pay to finish one search, payback gets weak; if they keep adding content and inviting relatives, owner income has a much better base.
