Ongoing operating support
Managed Ops is the post build operating layer for gym owners who need recurring monitoring, controlled changes, data hygiene, and clear accountability without making the owner the systems administrator.
Direct answer
Managed Ops does not replace the gym team and it does not manufacture a new strategy every month. It keeps approved systems clean, monitored, documented, and aligned to the operating cadence after implementation.
$2,000 CAD
Monthly per location
Locked commercial term for Managed Ops, subject to approved scope.
One queue
Change control
Requests, defects, and improvements enter one prioritized operating queue.
Weekly
Metric review
The cadence reviews exceptions and decisions, not vanity reporting.
Documented
System ownership
Changes are reflected in SOPs and the system register.
Operating lane
Critical automations, pipeline states, calendar events, and integrations are monitored against the approved operating path.
Failed trigger and stale stage review
Calendar and CRM reconciliation
Exception queue ownership
Controlled reruns and incident notes
Operating lane
The CRM remains usable because duplicates, dead stages, missing ownership, invalid fields, and outdated records are handled deliberately.
Duplicate and merge controls
Field and tag governance
Pipeline stage hygiene
Contact ownership review
Operating lane
Reporting is useful only when each number has a source, owner, threshold, and defined decision. Managed Ops maintains that control loop.
Metric source reconciliation
Exception and trend review
Owner decision register
Priority change recommendations
Operating lane
Every approved system change is tested, recorded, and reflected in the operating instructions before it becomes the new normal.
Change request intake
Pre release QA
SOP and Loom updates
Access and dependency register
Decision table
The Core build establishes the system. Managed Ops maintains the approved operating condition and controls changes after handoff.
| Criterion | Core build | Managed Ops |
|---|---|---|
| Commercial term | $3,000 CAD one time | $2,000 CAD per location per month |
| Primary job | Map, configure, test, document, and hand off | Monitor, reconcile, document, and control approved changes |
| Change boundary | Implementation scope | New systems or material expansion require separate approval |
| Ownership | Staff handoff and operating instructions | One Ardent queue owner plus one client decision owner |
Execution standard
The account stays clean because recurring work is bounded by a queue, a cadence, and acceptance criteria.
Define which workflows, integrations, dashboards, and systems are inside the managed scope.
Assign one owner for business decisions and one Ardent owner for the operating queue.
Prioritize incidents before improvements and improvements before cosmetic changes.
Record every material change, test result, dependency, and rollback note.
Review data exceptions and operating metrics on the agreed cadence.
Move new builds or material scope changes into a separately approved project.
Buyer questions
No. The Core build is a one time implementation and handoff. Managed Ops is a separate monthly operating engagement.
The locked term is two thousand Canadian dollars per month per location, subject to an approved scope.
No. Monitoring, hygiene, controlled changes, reporting, and documentation are managed work. A new system or material expansion requires a separately approved scope.
No. Response expectations belong in the signed scope. This page does not publish an unapproved SLA.
A new system or material expansion requires a separately approved scope. Managed Ops covers the agreed monitoring, hygiene, decision cadence, controlled changes, and documentation.
Managed Ops starts after the systems, decision rights, operating queue, and monthly scope are explicit.
Continue the system map
See the implementation scope before ongoing management begins.
Review the full Ardent GSI service architecture.
See the operating standard for a common integration failure.
Read the approved answers on scope and engagement structure.
Send the location count, systems, and recurring operating load.