Opportunities › Software solutions for emergency services departments › Proposed app
Stationhouse Ledger
Fixed-price records, rosters and run reports for small fire departments
- Score
- 41
- confidence 66
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 35 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 1970
- Mature market · AI estimate
ScreensConcept
Desktop and mobile: Fire crews write run reports from the road on mobile, but station staff review rosters, training logs, and equipment records on computers during shifts. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
New run report
Saved offlineAbout this appAI proposal
Stationhouse Ledger is a web app for small and rural fire departments to keep incident reports, member rosters, training hours and equipment checks in one place. It installs on any phone or station computer and works when the connection is poor.
It is built for departments with budgets down to around $130k a year, where a vendor price rise can take a real share of the budget. Pricing is flat per department, published, and not tied to call volume or member count. Data exports in open formats at any time, so you are never locked in.
It does not try to replace dispatch or other life-safety systems. It covers the paperwork around the calls, and does that part simply.
- Tagline
- Station paperwork at a price that stays put.
- Voice
- PlainSteadyHonest
- Why this name
- A ledger is a plain record kept honestly, and a stationhouse is where the crew works. The name says records for the fire station, with no jargon.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Run reports in under five minutes
A short form built for the truck ride back: times, units, crew, narrative. Saves offline and syncs when signal returns.
No member yet
Roster and certifications
Track members, roles and expiry dates for certifications. Reminders go out before anything lapses.
No member yet
Training hour log
Log drills with a sign-in on a phone. Hours roll up per member for the year.
No member yet
Apparatus and gear checks
Checklists per vehicle with photo notes. Failed items flag the chief and stay open until fixed.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#C2410CEmber · primary#FAF6F0Bone · surface#1F2421Soot · text#2F5D50Pine · accent#D9D2C7Ash · borders and dividers
Typography
Aa
Stationhouse Ledger
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Station paperwork at a price that stays put.
PricingAI proposal
The material gives no competitor price list. It reports one department's cost rising from $4k to $12k a year. These tiers are a starting point to test; Department is about $588 a year.
Volunteer
Free
- Up to 15 members
- Run reports and roster
- Open data export
Department
$49 a month
- Unlimited members
- Certifications and training log
- Apparatus checks
- Email support
County
$199 a month
- Up to 10 stations
- Shared reporting view
- Priority support
Would you pay Department · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$190,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. It reaches departments through direct outreach, fire service forums and word of mouth between chiefs. Using the app does not expose it to new buyers in any strong way.
- Do they become customers?
- Chiefs talk to neighbouring chiefs, so referrals may work. Test whether a county or mutual-aid group adopts it together and whether referral credits help.
- First customers
- Volunteer and combination fire departments in one US state with 15 to 40 members and annual budgets under about $300k, starting with the chief or administrator.
- Where to reach them
- State fire chiefs associations: Offer a short demo at regional meetings and a post in member newsletters.
- Fire service forums and groups: Join discussions on software costs, share a free tier and ask for feedback on reports.
- Direct outreach to chiefs: Email departments whose vendors raised prices and offer a free data import and setup.
- First milestone
- Ten departments in one state run real reports for 60 days, and at least five agree to pay the Department price.
Why people already pay for this
- VerifiedHacker News post received 19 points and 2 comments
- Public claimEmergency services software costs are escalating dramatically due to private equity consolidation.
- Public claimFire departments currently pay for commercial software from vendors now owned by private equity.
- Public claimEmergency services departments have inelastic demand and limited alternatives, creating pricing leverage for vendors.
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Offline storageIndexedDB with a background sync queueCrews write reports with no signal and need them to sync later without loss.
- This app · PDF exportServer-side PDF generation libraryDepartments often need printable reports for boards and records requests.
RisksAI inference
- RegulatoryFire departments may have to submit incident data in state or national formats. The material does not say which. Without that support, some departments cannot switch.
- CommercialThe evidence is public claims and one post with 19 points. It does not show that departments would move from their current vendors, or what they would pay.
- TechnicalOffline sync conflicts, where two members edit one report, could lose or duplicate records unless handled carefully.
- CommercialSmall departments buy slowly, often through boards or budget cycles, so sales could take months.
- DataIncident records can hold personal and medical details. Departments will expect strong access controls and clear retention rules.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.