Adaptive Traffic Signal Control Break-Even: $167K Monthly Revenue

Fixed costs $133K/mo Launch overhead base

Contribution margin 80% After variable costs

Break-even revenue $165K/mo Monthly revenue target

Break-even timing Month 1 First breakeven month

Break-even calculator

Test how monthly revenue, variable expenses, and fixed costs shape break-even for AI-controlled traffic signals.

Lean Base Full

Monthly revenue Enter the monthly sales you expect before fixed costs. $ Low sales High sales Variable expenses Enter direct costs that rise as projects and installs grow. $ Low direct High direct

Money available to cover fixed costs $5,090,250 $6,327,500 revenue - $1,237,250 variable expenses

Margin ratio

80%

Covers fixed costs

Yes

Fixed monthly costs Enter monthly overhead the business must cover either way. $ Low overhead High overhead

Break-even chart Revenue Total costs

Which expenses are fixed, and which move with sales for an adaptive signal control business?

Cost classification

Break-even works only if fixed overhead stays separate from volume-driven expense. Here, $45,000/month of recurring facilities overhead and first-year payroll sit apart, while commissions, shipping, cloud usage, support, and warranty move with revenue.

Expense	Cost	Break-Even Treatment	Common Mistake
R and D Center Rent	Fixed	Include $15,000/month in fixed overhead from Month 1 through Month 60.	Spreading rent across each installed unit and hiding launch overhead.
Insurance and Liability	Fixed	Carry $5,000/month as fixed overhead in the break-even model.	Dropping liability cover until revenue starts, which understates Month 1 cash need.
Core technical and sales payroll	Fixed	Model the Chief Technology Officer, two AI ML Engineers, and Government Sales Director as $700,000/year before unit volume.	Treating required launch staff as optional selling expense.
Sales Commissions	Variable	Deduct 4.0% of first-year revenue from contribution margin, then use the lower forecast rates by year.	Modeling commissions as flat payroll instead of revenue-linked selling expense.
Logistics and Shipping	Variable	Deduct 2.0% of first-year revenue, declining by forecast as volume improves.	Ignoring shipment cost on hardware-heavy deployments.
Technical Support Allocation	Semi-variable	Use the 1.5% revenue allocation for support load, and add staff separately when service volume requires it.	Treating support as fully fixed while tickets rise with installed systems.
Quality Control Lab	Semi-variable	Apply the 0.5% revenue allocation because testing workload rises with shipped devices.	Booking lab work as fixed overhead only, then overstating unit margin.
Project Manager capacity	Semi-fixed	Add $105,000/year per full-time Project Manager in steps as deployment volume grows.	Treating field support and deployment labor as fully fixed when rollout volume drives workload.

How does break-even change from a lean pilot to a full rollout?

Scenario table

Lean is already above break-even, base adds more cushion, and full rollout widens it again. The real watch item is revenue timing, because launch-month delays can move cash faster than annual totals.

These are model-based planning assumptions, not guarantees; actual deployment timing can shift break-even even when annual revenue looks strong.

Scenario	Monthly Revenue	Variable Costs	Fixed Costs	CM Ratio	Operating Profit	Break-Even Signal
Lean pilot rollout	$1.23M	$240K	$133K	80.5%	$857K	Clear of break-even, but pilot timing still drives cash risk.
Base repeat deployment	$2.80M	$535K	$203K	80.9%	$2.06M	Repeat wins build a wider cushion and lower break-even risk.
Full regional rollout	$6.33M	$1.18M	$292K	81.3%	$4.85M	Scale gives the widest cushion and the least break-even pressure.

What pressures the break-even plan first: slow awards, higher support, or fixed-cost creep?

Stress test

The base Year 1 run rate clears break-even by a wide margin: monthly revenue is about $1.23M against a $167K threshold, so there’s about $1.06M of cushion. The real break risk is slower awards, heavier field support, or hiring before proof.

Stress Case	Changed Assumption	Break-Even Revenue	Revenue Gap	Risk Signal
Current plan	No change.	$167,000	$1,063,000 cushion	Year 1 revenue covers fixed overhead with room.
Revenue shortfall	Monthly revenue slips to $150,000 as awards delay.	$167,000	$17,000 gap	Deployments below break-even leave fixed overhead uncovered.
Fixed-cost pressure	Monthly overhead rises by $10,000 before volume lands.	$293,000	$937,000 cushion	Every added overhead dollar pushes the threshold up fast.
Margin pressure	Support and warranty load cut margin by 5 points.	$177,000	$1,053,000 cushion	More tickets and rework shrink the cushion but still clear break-even.
Combined pressure	Monthly revenue falls to $125,000, overhead rises by $10,000, and margin drops 5 points.	$303,000	$178,000 gap	Unpaid pilots, slow site access, and longer sales cycles can push the plan under break-even.

What should the founder verify before buying vehicles and scaling signal deployments?

Founder checklist

Don’t scale payroll, fleet, or rollout crews until you have signed municipal or agency purchase orders and enough cash for Month 1 burn. The opening month needs at least $1.194M, so the test is whether demand and support clear that floor.

1Signed POsAgency orders

Verify signed municipal or agency purchase orders before you add payroll, because demand proof has to come before rollout spend.

2Fixed burn$132.9K/mo

Add the $45K of monthly operating overhead to Year 1 payroll, and don’t add headcount until that burn is covered by signed work.

3Contribution margin89.0% CM

Verify the blended variable load stays near the modeled 11.0% of revenue, so the rollout still funds itself after support, shipping, and QC.

4Install coverage$220K fleet

Secure installer or field-service partners before buying the $220K vehicle fleet, or you’ll own equipment without enough crews to use it.

5Cash cushion$1.194M

Hold at least the opening-month minimum cash and demo or replacement stock, because Month 1 is the lowest-cash point in the model.

6Collections paceBefore payroll

Track when municipal cash lands, because booked revenue does not pay payroll and expansion only works once receipts are arriving on time.