Modeled Scenarios
What a rebuild
actually looks like
Straight talk: the industry line is new and we have no named customers yet, so there are no real case studies to show you. Instead of inventing logos, we modeled six typical situations from published legacy-vendor pricing. Every card below is labeled for what it is.
// shipped
1
product live & open source (Drift)
// in build
4
products in private development
// after handoff
$0
required recurring fees — you own the build
// named customers
0
so far — and we won't invent any. Be the first.
scenario-water-district.sh
Utility Management
A Small Water District Stuck on a $24k/yr Billing Contract
The typical setup: ~800 accounts, software built in 2001, a renewal invoice north of $24,000/year, and monthly billing that takes days because one admin babysits the whole run. The rebuild we'd scope: automated billing runs, online payments, and a customer portal — delivered as a one-time build the district owns outright.
// modeled scenario — not a customer · costs from published legacy pricing
scenario-small-warehouse.sh
Warehouse OS
A 12-Person Warehouse Running on Spreadsheets
Inventory lives in one spreadsheet, shipping in another, and the truth in nobody's. Enterprise WMS quotes start around five figures a year — overkill for a small floor. The rebuild we'd scope: barcode scanning, guided picking, and shipping integration built for how the floor actually works, with no per-seat subscription attached.
// modeled scenario — not a customer · sized from typical small-3PL operations
scenario-regional-isp.sh
Telecom Portal
A Regional ISP Whose Billing Platform Outcosts Its IT Budget
A couple thousand fiber subscribers, and an enterprise billing contract that runs $100k+/year — often more than everything else in the rack combined. The rebuild we'd scope: subscriber billing, provisioning hooks for installs, and a self-service portal, owned by the ISP with no meter running.
// modeled scenario — not a customer · costs from published enterprise-billing pricing
scenario-hvac-dispatch.sh
Field Services
An HVAC Shop Dispatching 14 Techs Off a Whiteboard
Dispatch by phone call, schedules on a whiteboard, and no idea where the trucks are between jobs. The rebuild we'd scope: GPS-aware dispatch, work orders on the techs' phones, and automated appointment reminders — the boring plumbing that turns drive time back into billable jobs.
// modeled scenario — not a customer · sized from typical mid-size service fleets
scenario-regional-insurer.sh
Insurance Ops
A Regional Insurer Processing Claims on a 12-Year-Old System
A few thousand P&C policies on software old enough that a simple auto claim takes over a week of manual touches. The rebuild we'd scope: straight-through processing for routine claims, modern policy admin, and an agent portal that answers the questions people currently call about.
// modeled scenario — not a customer · sized from typical regional P&C books
scenario-electric-coop.sh
Utility Management
An Electric Co-op Printing 3,000 Paper Bills a Month
Every month: thousands of bills printed, stuffed, and mailed at nearly a dollar each, because the billing system predates e-billing. The rebuild we'd scope: paperless billing, autopay, and outage notifications — print-and-postage math alone often covers a chunk of the build.
// modeled scenario — not a customer · print costs from USPS + industry rates
your story first
Want to be the first
named case study?
Book a 30-minute scoping call. We'll model your actual numbers — like the scenarios above, but with your data — before you commit to anything.