The phone rings at 6 AM.Your shop already answered it.
Dino AI Hub is the entire operating system for a plumbing shop — phones, dispatch, quotes, payments, and books — running on one hub you own, sitting in your office. Not eight subscriptions. Not your data on someone else's server. One hub. The whole shop.
one-time purchase · no subscription · your data stays at the shop
Eight subscriptions to run a shop.Or one Ai Hub you own.
Hit collapse. Watch the stack become your AI Hub.
voice
ops
customers
sales
money
growth
accounting
scheduling
$1,064/mo
$12,768 per year, every year, forever
You own it.
No subscription. No per-seat. No data leaving the shop.
—— Hover any tile for what that subscription costs you
Manual, assisted, or fully automated. You decide. Per module.
Manual
You drive. AI stays out of the way. For the parts of your shop you want total control of.
AI-assisted
AI suggests, you confirm. Move faster without giving up the call. The default for most shops.
Fully automated
AI runs it. You oversee. Trust the system to handle the work and bring you in when it matters.
Set it per module. Dispatch on full auto, sales calls manual, marketing assisted — whatever fits how you actually run.
A day on the hub
One day at your shop. Three ways to run it.
Manual, AI-assisted, or fully automated — you choose per module. Here's the same kind of day, run each way.
The shop runs the shop. The AI is on call for the paperwork.
Doreen's board
A four-truck plumbing shop in upstate New York. Doreen has been the dispatcher for twenty-one years. She runs the board by hand. Manual dispatch, manual quoting, AI on call for everything else.
- 6:30 AM.
Doreen walks in, makes coffee, sits at the board. Today's jobs are listed in the order she scheduled them — by hand, in BOS, the way she always has. She assigns each one to a tech based on what she knows: who lives where, who's good with which kinds of customers, whose truck has the camera, whose wife is having a baby this week and shouldn't catch the late call.
- 8:45 AM.
A tech calls in. He's at a job and the customer asked him to look at a second issue while he's there — a hose bibb that's leaking. He's not sure what model the bibb is. Doreen pulls up the customer record on BOS, looks at the property history (the previous tech who serviced this house, two years ago, noted the bibb model in his job notes), and reads the model number to him over the radio. Took her eighteen seconds.
- 11:30 AM.
A customer calls and asks if a job she had done last spring is still under warranty. Doreen asks BOS — typed into the chat box, *"is the Williamson Park Drive job from April still under warranty?"* — and the system returns the answer in two seconds: *"Yes. Standard one-year labor warranty expires May 14. The job covered a kitchen P-trap replacement and a vanity install."* Doreen tells the customer yes, schedules the warranty visit on the board by hand.
- 3:00 PM.
A tech needs a follow-up email written to a customer he gave a quote to yesterday — the customer hasn't approved yet. He calls Doreen. She types into BOS: *"Draft a polite follow-up to the Greene Street quote from yesterday, asking if she has any questions, mentioning we can adjust the timing if needed."* The system drafts the email; Doreen reads it, changes "any questions" to "any questions or concerns," sends it. The whole thing took ninety seconds.
- 5:00 PM.
Board cleared. Doreen has assigned every job in the building today. The system has helped her with lookups and drafts but hasn't made a single decision on her behalf.
The shop ran the way Doreen has always run it. The system made her faster at the parts that used to take longer.
The system proposes; a human approves before anything goes out.
Lisa's morning
A five-truck plumbing shop in northern Virginia. Lisa is the dispatcher; she's been with the company eleven years. Dispatch runs on AI suggestions. Quoting runs fully automated under $1,500.
- 6:30 AM.
Lisa opens BOS with her coffee. The board for today is already populated — eight scheduled jobs, four techs, a proposed assignment for every job. Each card shows the system's reasoning: *Mike — closest to Reston, journeyman level, last serviced this customer two years ago.* She reads through the eight proposals.
- 6:34 AM.
Six are obvious — she taps accept on each. Two she wants to swap. One customer specifically asked for Carlos last time; the system flagged it in the card but proposed Diego because Carlos is starting twenty minutes farther east. Lisa overrides — she knows the customer's neighbor is married to Carlos's cousin, and she's not going to be the one to break that streak. The system updates the routes for the day in three seconds.
- 8:15 AM.
A call comes in. Burst pipe in a kitchen ceiling. The receptionist books it and the system flashes a proposed assignment on Lisa's screen: *Mike — already in Reston, finishing in fifteen minutes, water-damage qualified.* She accepts.
- 11:50 AM.
Mike flags a missing part on the job he's currently at. The system proposes the same kind of intercept it would run on full auto: route to Tom's truck, pick up the part, continue, save twenty-four minutes. Lisa sees the proposal with the math attached. She thinks about Tom's afternoon, decides he can spare it, taps accept.
- 3:20 PM.
Another call — a hot water heater leak, the customer requesting end of week. The system proposes Friday at 10 AM with Diego. Lisa knows Diego is on vacation Friday but hasn't told the system yet. She overrides to Thursday afternoon with Mike. The system absorbs the constraint, asks her if she wants to mark Diego unavailable Friday in his schedule. She taps yes.
- 5:00 PM.
End of day. Lisa has touched fourteen decisions. Twelve she accepted as proposed; two she overrode. She's tired the way she always is. The work is the same. The mental load is not.
The system proposed; Lisa stayed in charge. Nothing happened she didn't see and approve.
The system decides and acts. The owner reviews what happened.
A Tuesday at a plumbing shop on Dino
A four-truck plumbing shop on Long Island. The owner runs trucks half the week. Dispatch and quoting are fully automated; the owner reviews exceptions at the end of the day, not jobs in progress.
- 6:47 AM.
A customer calls — no hot water in the house. The receptionist answers in your shop's voice, asks the right diagnostic questions, gets the address, and offers a 9:00–11:00 window. The customer accepts. Seconds after he hangs up, his phone buzzes — an SMS with a link to a clean, branded portal where he can track the job, upload anything the tech might need, see his quote when it lands, and pay when it's done.
- 6:51 AM.
The customer opens the portal link. He takes two photos of his water heater — an older brand, a specific model — and writes a note that the cold-water valve has been weeping for weeks. Photos and note attach to the job record automatically.
- 7:02 AM.
The system evaluates today's available techs against the new job: who's on shift, who has the skill level for water heaters, who's geographically closest to the address, what each one's current load looks like. It picks Mike — a journeyman fifteen minutes from the house — and assigns the job. Mike's phone, already in his truck, lights up.
- 7:04 AM.
Mike opens Field. He sees the job, the receptionist's notes, the customer's photos and message from the portal. He recognizes the water heater immediately: an older unit that takes a specific flue-pipe adapter. He doesn't carry it. He taps a button in Field to flag the missing part.
- 7:05 AM.
The system already knows who has what. It checks van inventory across the fleet and finds the adapter — but it's with Tom, not in the shop. Tom is twelve minutes east of Mike, finishing a sink installation. The system runs the numbers two ways. Route Mike east to intercept Tom, grab the adapter, and continue to the customer: adds 24 minutes, still inside the customer's window. Reassign the job to Tom once he wraps his current one: arrives 32 minutes later, customer pushed to the late edge of the window. Mike-intercepts-Tom wins. The system updates Mike's route, drops Tom a short note that a coworker is stopping by, and pushes a new ETA to the customer's portal.
- 9:15 AM.
Mike pulls up to the house with the adapter in hand. The customer has been getting automatic ETA updates the whole way. He opens the door already knowing he's about to meet someone named Mike.
- 9:45 AM.
Diagnosis done. Mike generates a quote on his phone — water heater repair plus the leaking valve as a second line item. The quote pushes to the customer's portal. The customer reviews it on his phone in the kitchen, taps to approve, and the job is locked in.
- 11:15 AM.
Job complete. Mike marks done. The invoice generates from the on-site quote with no rekeying. The customer's portal shows the invoice with a Pay button. He taps it. The payment processes over Mike's phone's cellular connection while Mike is still on the porch, and reconciles to the books before Mike's truck is back in gear.
- 2:00 PM.
A second call. The customer mentions the receptionist sounds familiar — she called last year. The system pulls her history and starts the conversation halfway through, already knowing what's been done at her property and what's still under warranty.
- 4:30 PM.
The owner pulls up the dashboard between his own jobs. Today: nine jobs done, $5,800 in revenue, three on-site upsells the techs made because the system surfaced relevant equipment history at the right moment. The dashboard flags one AI decision for his review — the tool-routing call from this morning. He taps it, sees the math, confirms it was right, moves on. Marketing analytics flag that one of his lead sources — a Yelp ad — hasn't returned a single call this week. He turns it off.
- 7:00 PM.
Office closes. The receptionist keeps answering. Whatever it can handle, it handles. Anything urgent gets escalated to whoever's on-call.
The shop ran itself. Mike and Tom did real work. The owner reviewed two decisions and ran a quarter of a marketing audit during a coffee break. Nobody fought with software.
The shop runs the shop. The AI is on call for the paperwork.
Doreen's board
A four-truck plumbing shop in upstate New York. Doreen has been the dispatcher for twenty-one years. She runs the board by hand. Manual dispatch, manual quoting, AI on call for everything else.
- 6:30 AM.
Doreen walks in, makes coffee, sits at the board. Today's jobs are listed in the order she scheduled them — by hand, in BOS, the way she always has. She assigns each one to a tech based on what she knows: who lives where, who's good with which kinds of customers, whose truck has the camera, whose wife is having a baby this week and shouldn't catch the late call.
- 8:45 AM.
A tech calls in. He's at a job and the customer asked him to look at a second issue while he's there — a hose bibb that's leaking. He's not sure what model the bibb is. Doreen pulls up the customer record on BOS, looks at the property history (the previous tech who serviced this house, two years ago, noted the bibb model in his job notes), and reads the model number to him over the radio. Took her eighteen seconds.
- 11:30 AM.
A customer calls and asks if a job she had done last spring is still under warranty. Doreen asks BOS — typed into the chat box, *"is the Williamson Park Drive job from April still under warranty?"* — and the system returns the answer in two seconds: *"Yes. Standard one-year labor warranty expires May 14. The job covered a kitchen P-trap replacement and a vanity install."* Doreen tells the customer yes, schedules the warranty visit on the board by hand.
- 3:00 PM.
A tech needs a follow-up email written to a customer he gave a quote to yesterday — the customer hasn't approved yet. He calls Doreen. She types into BOS: *"Draft a polite follow-up to the Greene Street quote from yesterday, asking if she has any questions, mentioning we can adjust the timing if needed."* The system drafts the email; Doreen reads it, changes "any questions" to "any questions or concerns," sends it. The whole thing took ninety seconds.
- 5:00 PM.
Board cleared. Doreen has assigned every job in the building today. The system has helped her with lookups and drafts but hasn't made a single decision on her behalf.
The shop ran the way Doreen has always run it. The system made her faster at the parts that used to take longer.
It replaces the stack. A to Z.
Dino AI Hub isn't a tool you bolt onto your stack. It replaces it — built for how a plumbing shop actually runs.
Answers the phone.
A voice receptionist in your shop's voice, handling the 6 AM no-hot-water call and the midnight burst pipe, catching emergency keywords, booking the job, walking a panicked homeowner through the shutoff valve.
One inbox for everything.
Phone, Instagram, WhatsApp, Facebook, web chat — every customer message in one place.
Dispatches the trucks.
Skill- and location-aware assignment, van-inventory awareness across the fleet, on-call rotation overnight, the part-intercept math that keeps you inside the window.
Knows the equipment.
Every water heater, every property, every install date. When a 14-year-old unit calls in again, the history is right there — and so is the replacement conversation.
Quotes from the truck.
Good-better-best from your pricebook, written on the tech's phone, approved on the customer's.
Takes the payment.
Card on the porch, reconciled to the books before the truck moves.
Keeps the books.
QuickBooks today, a native accounting module coming — every invoice, payment, and job already connected.
Generates the leads.
Scrape, enrich, and draft outreach — you approve every message before it sends.
Three connected views — an owner dashboard, a technician field app, and a customer portal. Updates ship automatically, for the life of the hub.
You're not buying a hub. You're hiring the team behind it.
Most software companies sell you a login and disappear — whatever they built for everyone, frozen on the day you signed up. Dino AI Hub is the opposite: a physical system and the engineering team that builds it, trains it, and keeps making it better for your shop.
Configured to your shop, not a template.
During onboarding, the team trains the AI on your scripts, your customers, your pricebook, your workflows. It learns how your shop talks and runs — not a generic, out-of-the-box default.
It keeps getting better, for free, for life.
New features, new integrations, improvements — they ship to your hub automatically, to every client at once, at no extra cost. When the native accounting module lands, you get it. You never re-buy. You never get bumped to a higher tier.
The trades change. The system changes with them.
There's a team whose entire job is keeping the system ahead of how your business actually runs. The version you buy today is the worst one you'll ever use.
What you're actually buying.
You don't take our word for the AI. You watch it run.
Book a demo and we'll walk a real plumbing day through the system — the emergency dispatch, the live inbox, the quote-to-payment, the customer history surfacing on the second call.
And here's the part that doesn't depend on a single AI feature: the math. Eight subscriptions at roughly $12,768 a year1, or a hub you buy once and own. It's true on day one, before the first call is even answered.
Voice AI agencies charges the bundle. Dino AI Hub charges the line.
Same 1,000 voice minutes a month. SaaS bundles every layer and bills per minute. Dino AI Hub runs the layers on the Ai Hub — you pay for what's actually metered.
All AI runs on the Ai Hub. The only per-minute fee is the Twilio phone line.
Bundled per-minute
capacity
10 concurrent calls
industry average
1,000 min × $0.2000 / min
$200.00 / mo
$2,400.00 / yr
Everything on the Ai Hub. Pay the line.
capacity
4 concurrent calls
per 1 AI Hub unit
1,000 min × $0.0125 / min
$12.50 / mo
$150.00 / yr
Twilio is the online phone line — the only per-minute fee for voice. IG DM, Facebook Messenger, email, and website chat run through Dino AI Hub with no connection fee. Same agent, every channel. All Twilio expenses are paid directly to Twilio.
Fire, flood, or a dead drive. Your shop keeps running.
Backed up to a drive you own.
Everything on your hub is continuously backed up to a dedicated external drive in your shop — yours, like everything else.
Recovers on any computer.
If your hardware goes down — failure, fire, flood, break-in — plug that drive into any capable computer and the whole working shop comes back up. Records, scheduling, dispatch, quotes, invoices, payments, the books.
The AI, your call.
Only the on-board AI doesn't travel — it runs on the hub's own hardware. For the few days in between, run those parts by hand, or connect a metered cloud-AI key you control and switch off the moment your hub is back.
And here's the part no SaaS can touch: your data never goes anywhere. Not to us, not to a cloud, not ever. It lives on a drive you hold in your hand. When a SaaS vendor has an outage, you're simply down. With Dino AI Hub, the worst day means plugging a drive into a laptop and getting back to work.
You can't be locked out of something you own.
The questions every plumber asks.
Is there a contract?
Where does my data live?
Do I need an IT person?
What if I want to leave?
Coming off another platform?
Most plumbing shops we talk to are on ServiceTitan, Housecall Pro, or Jobber — paying every month, with their customer list living on a server they don't control.
Feeling the ServiceTitan bill?
See exactly what switching looks like for a larger shop.
Dino vs. ServiceTitan →On Housecall Pro or Jobber?
The move is simpler than you'd think — and we do most of it.
How migration works →One hub. The entire shop.Book the 20-minute demo.
We'll run a real plumbing day through the system and show you the math for a shop your size.
Sources
- 1.Subscription pricing is representative — the same eight-tool stack and monthly figures shown on the homepage. Confirm each tool's price with a dated citation before publish. ↩