The page says ongoing support is optional and that most clients use it for the first two to three months after an Implementation Sprint, then step down. This is a described common path, not a required prerequisite.
Commitment
The selected support offer is optional, month-to-month, and cancel-anytime. The page does not name a longer minimum.
Support and follow-up
For Ongoing Workflow Support, the page says the workflow is kept tuned as team, volume, and tools change. It gives no response-time commitment or named maintenance hours.
Ending the engagement
The selected Ongoing Workflow Support offer is described as month-to-month and cancel-anytime. No refund, proration, notice period, or effective-date rule is stated.
Keep the work, accounts and next owner connected. Ask what you can operate when this engagement ends.
Questions to settle before you commit
Are you accepting this kind of engagement, and when could it start?
Who needs to participate, and what access or examples should we prepare?
Which software, model, hosting or usage charges would we pay separately?
Which accounts, code, prompts and documentation would we receive?
Optional post-launch monthly Workflow Concierge for maintaining and tuning a live system, adding one workflow build per quarter, and quarterly business reviews. The initial system build is a separate fixed-scope purchase.
Monitoring, tuning and small changes for previously implemented automations, with a monthly report. The homepage claims same-day response Monday through Friday; initial implementation is separately priced.
Provider describes custom agents for maintenance, leasing, tenant support and back office, connected to existing PM software and operated with ongoing tuning.
PricingPage says $150/month starting for one fix and $200/month for whole-portfolio automation, but also uses an $8/unit example at 150 units; confirm because figures do not reconcile.