Three months of BD compound into a software-margin AI services business. Drag the levers on the Data tab to model min/base/max scenarios. P&L tab folds in real headcount, software, and CAC.
As of Apr 29, 2026
Source: Notion · Revenue, Payroll, Software
Last refreshed: Apr 29, 2026
Step 2 — Revenue ignition$300k/mo
Q2 2026 peak monthly run-rate from those 3 months of BD.
→
Step 3 — Compound$XXk/mo
Q4 2027 exit run-rate at base growth + maintenance tail.
Software margins, brought to AI transformations.
Anchor Q2 2026 monthly run-rate
—
Set on the Data tab
FY 2026 revenue Base scenario
—
—
FY 2027 revenue Base scenario
—
—
FY 2027 net profit* After full opex + CAC
—
— net margin · see P&L tab
Quarterly revenue trajectory
New contractsMaintenance tail
Compounding kicks in from Q3 2026 as Q2 contracts begin paying maintenance; by Q4 2027 four prior quarters are paying simultaneously. Use the scenario toggle to switch between Min, Base, and Max.
Story-point unit economics — delivery margin
Gross profit*SP delivery cost*
Cost per story point*
—
25 SP pod = —/mo
Charge per story point
—
Standard team rate
Delivery margin per SP
—
Software-tier unit economics
* Delivery cost only. This shows the unit economics of delivering a story point of work. It does not include cost of customer acquisition, sales, marketing, leadership, finance, or other operating expenses. Full P&L view (including all opex + CAC) is on the P&L tab.
Quarterly projection
Quarter
Monthly run-rate
New contracts (Q)
Maintenance (Q)
Total revenue
SP delivered
Delivery cost*
Gross profit*
Margin*
Q1 2026 reflects actual recognized revenue. Q2 onwards is projected from the anchor. Margin* = SP delivery margin only — see P&L tab for net margin after full opex + CAC.
Annual summary
Year
New contracts
Maintenance
Total revenue
Delivery cost*
Gross profit*
Margin*
Min total
Max total
How the story compounds
Anchor
—
Q2 2026 monthly run-rate
QoQ growth (active)
—
Min 10% · Max 30% on toggle
Maintenance lever
—
% of contract × conversion, over 12 mo
Delivery margin*
—
From SP unit economics
The compounding mechanic: each quarter's contracts (TCV ≈ 3 × monthly run-rate) generate maintenance revenue equal to 17.5% of TCV, paid out across the next 4 quarters. By Q4 2027, four prior quarters are simultaneously paying maintenance — that tail, layered onto QoQ contract growth, is the difference between a services company and a software business.
Today's cost structure
Engineering payroll
—
— engineers / consultancy
Other payroll
—
— supporting roles
Software (active)
—
— active subscriptions
Total monthly opex
—
Capacity: — SP/mo
Engineers deliver story points; capacity = engineers × 25 SP/month. Other costs (leadership, sales, support, software) scale proportionally with engineering as the team grows.
FY 2026 net profit Base scenario
—
— net margin
FY 2027 net profit Base scenario
—
— net margin
FY 2027 headcount Engineers required
—
From 9 today · ramped quarterly
FY 2027 CAC 15% of new revenue
—
Tunable on Data tab
Revenue → cost → profit per quarter
Engineering costOther opexCACNet profit
Each bar's total height equals total revenue for that quarter. As demand grows, engineering scales (cost per SP demand), other opex scales proportionally with engineer count, and CAC takes 15% of new contracts.
Quarterly P&L
Quarter
Revenue
Engineers
Eng cost
Other opex
CAC
Total cost
Net profit
Net margin
Engineers needed = ceil(monthly SP demand ÷ 25), floored at current engineering count. Other opex = engineers × other-cost-per-engineer (set on Data tab).
Annual P&L summary
Year
Revenue
Eng cost
Other opex
CAC
Total cost
Net profit
Net margin
The realistic story: after full opex (engineering, leadership, sales, support, software) and 15% CAC on new contracts, FY 2027 net margin is —, on $— revenue producing — in net profit. Software-tier margins, in a services business model.