CRM and contacts
Keep people, conversations, and commercial context closer to the operating layer.
Fleet Pro feature
Operating Hub is the founder operating layer inside Fleet Pro. It brings CRM, tasks, schedule, documents, reports, and activity into one place so the owner can act without bouncing across disconnected tools.
Value driver
Operating Hub
Calmer founder operations and fewer scattered handoffs.
Package fit
Fleet Pro
Operating Hub access belongs inside Fleet Pro and is not positioned as a separate product.
Current state
Partially live / in progress
The portal-first operating environment exists now, while the fuller packaged client-facing hub continues to deepen.
What it is
Operating Hub is not an ERP replacement. It is the founder operating layer that sits around the most important actions, records, and rhythms inside the business.
What it drives
It reduces context switching, makes follow-through easier, and connects the visibility layer to the day-to-day operating rhythm that actually moves the company forward.
What sits inside
Keep people, conversations, and commercial context closer to the operating layer.
Move from loose reminders into a clearer working rhythm for the founder and team.
Put the important operating artefacts near the actions they should influence.
See where the business is moving and where systems can take work off the founder.
Keep people, conversations, and commercial context closer to the operating layer.
Proof block
The current founder portal gives honest proof for the Operating Hub story: cash flow, tasks, pipeline, and upcoming work in one operating environment.
Revenue
$12,890
Pipeline
$16,980
Open tasks
3
Upcoming
2
Open tasks
Configure Meta Ads attribution
Coastal Retail, Q2 Growth Sprint
Build weekly briefing template
Coastal Retail, Q2 Growth Sprint
Connect Xero data source
BrightPath, Data Integration
Upcoming rhythm
Weekly sync, Coastal Retail
2026-04-07T10:00:00
BrightPath, Xero integration deadline
2026-04-10
Current founder portal surface used as operating-layer proof.
Current state
Partially live / in progress
The portal-first operating environment exists now, while the fuller packaged client-facing hub continues to deepen.
Next depth
What this expands into.
Vertical-specific depth and heavier workflow systems remain Implementation territory until they prove repeatable enough for the product layer.
Next step
Vivacity works best when the product story stays grounded: start where the business needs clarity, move into recurring Intelligence when the rhythm matters, and scope Implementation only when the systems should be built.