How Moovs got its whole team using AI
Moovs' quarterly forecast used to take about ten hours. Now it takes a couple. Customer replies that took days go out in hours, and onboarding follow-up and daily goal tracking run on their own. In ten weeks, 24 of its 25 teammates were using type.com to get there.
Moovs is an all-in-one software platform that helps black car, limo, chauffeured transportation, charter bus, and shuttle operators run and grow their businesses. Booking, dispatch, drivers, vehicles, customer communication, billing, and payments live in one system, so an operator can spend less time on manual work and more time growing.
Moovs' own revenue team is lean. The same handful of people sell, close, onboard, and forecast, so hours spent on spreadsheets and manual follow-up come straight out of selling time.
Moovs started using type.com on July 30, 2026. Ten weeks later, the quarterly forecast takes a fraction of the time, every new customer gets a consistent onboarding follow-up, the team's goals update themselves every morning, and almost the entire company is using type.com, with 11,981 automation runs doing work nobody had to start by hand.
Forecasting went from 10 hours in a spreadsheet to a couple of hours
Every quarter, Moovs has to answer the question leadership cares about most: where will MRR land? That means modeling new business, expansion, churn, and contraction. It lived in a Google Sheet and took roughly ten hours to put together.
Heading into a new quarter, the person who owns the forecast looked at that sheet and had a different idea.
“I could maybe build this with an app by looking at our HubSpot data.”
About a day later, it was one. Three cases, a month-by-month breakdown, and a tab spelling out the assumptions. Most of that day went into checking the numbers: the first pass pulled the wrong HubSpot property, and it got caught because the result didn't match the number already worked out by hand.
Then came review. The forecast was walked through with leadership on a call, and instead of taking notes, the call transcript went straight back into the conversation where the app was built. type.com suggested changes, and each one was approved or tweaked. One early idea stuck: make every number clickable, so anyone can double-click into a figure and see exactly how it was built.
That turned out to matter most after sign-off. A spreadsheet forecast is a number you hit or miss. This one is a record of reasoning. If new MRR comes in short mid-quarter, the answer is a click away: the deals that were supposed to close, and the run rate that was assumed.
“Even while we're in the middle of the quarter, I can come back here and understand, oh, it's because we're expecting this deal to close.”
Quarterly MRR forecast
Built on HubSpot data · three cases · month-by-month breakdown
How this number was built
- Deals expected to close this quarter, pulled from HubSpot
- Close dates and run rate behind each deal
- The assumptions tab, signed off by leadership
Quarterly goals that update themselves every morning
A forecast tells you where the quarter should land. It doesn't tell you what to do this week.
So the next step was a plan. The pipeline target for next quarter, the KPIs behind it, three quarterly rocks, and the tasks to get there were worked out in a long back-and-forth with type.com. Only once the plan held up did it become an app.
It was built on a Friday and in use by Monday. Every morning at 7 AM it pulls fresh numbers from HubSpot and Metabase, and it's now the agenda for weekly one-on-ones: one screen showing where the quarter stands and what's next.
Moovs didn't take it on faith. The rule is the same one any good operator uses with a new data source: check it against what you already know, and earn trust over time.
“After a month, if it's accurate with what I have, then I'll start trusting it.”
Pulls from HubSpot and Metabase
- Company goalWhere Moovs needs to land this quarter
- KPIsIndividual targets, refreshed from live data
- RocksThe three quarterly priorities behind the KPIs
- TasksPlanned with type.com before the app was built
Used in weekly one-on-ones to see where the quarter stands.
Every new customer gets onboarding follow-up, automatically
Moovs serves everyone from owner-operators to enterprise fleets, and none of them get value until they're set up. With a small customer success team juggling everything else, onboarding follow-up wasn't happening as consistently as it should.
So the team stopped relying on memory. An automation now sends the onboarding email from each customer success manager's own Front inbox, so the customer hears from a real person and replies land with them. Then it writes the result back to HubSpot.
Along the way it created two HubSpot fields that didn't exist before: onboarding stage and engagement status. Whether a customer is onboarded, never onboarded, or has gone quiet is now a field anyone can filter on, not a hunch.
One automation sends the email and keeps the CRM honest.
- 01
New customer lands
A new account in HubSpot starts the onboarding automation.
- 02
Email from their CSM
The onboarding email goes out from the customer success manager's own Front inbox, so replies land with a real person.
- 03
HubSpot stays current
Onboarding stage
- New
- Onboarding
- Onboarded
- Never onboarded
Engagement
- Engaged
- Dormant
24 of 25 teammates on type.com in ten weeks
The biggest result isn't one app. It's that the whole company is using type.com, not just one or two power users, and it happened without a formal rollout.
Ten weeks after the first thread, 24 of Moovs' 25 teammates had used type.com, and AI work was running in 32 Spaces. The bigger change was who starts the work. Most of it no longer waits for someone to ask: 59% of all AI work at Moovs is now kicked off by automations, not people.
“We're enjoying it. Things are changing daily, and it's keeping up.”
- July 30
Day one
First AI thread and first scheduled task on type.com.
- End of Q3
The forecast
The quarterly MRR forecast moves out of a spreadsheet and into an app, built in about a day.
- Late September
The routine
A goals and KPI app goes live and starts refreshing every morning at 7 AM.
- October 8
Ten weeks in
24 of 25 teammates have used type.com, and 11,981 automation runs have shipped.
And it's not a launch spike. Moovs ran 5,528 automations in the last 30 days, level with the 30 days before, while AI threads grew 2% to 6,206. Reliability improved as usage held: 98.9% of AI messages completed without error, and failures fell 63% month over month.
For a team that sells operators on spending less time on manual work, that's the point. Customer replies that used to take days now take hours, by the team's own estimate, and the quarterly forecast takes a couple of hours instead of ten.
AI messages since July 30, 2026
- Started automatically
- 11,981
- 59% of all AI work
- Started by people
- 7,846
- Across 24 teammates
Source: Moovs' type.com usage analytics, as of October 8, 2026.
- Teammates active in the last 30 days
- 22 of 25
- Spaces with AI activity
- 32
- AI messages completed without error
- 98.9%
- Drop in failures, month over month
- 63%
In Moovs' own words
Rough estimates from the Moovs team, not measured figures.
- Quarterly MRR forecast
- About 10 hoursA couple of hours
- Customer response time
- DaysHours
Let type.com set up your first space for you.
In just a few minutes you'll be rolling with your first agent.
Start a 2-week free trial“This one was really helpful, and I keep going back to it.”
Moovs revenue team