Service · Ongoing
Support & Maintenance.
Optional monthly plans for work we have built, picking up after the 30-day stabilisation that ships with every Build. Monitoring. API-change patching. AI-module upkeep. Adjustment hours. A named contact during lodgement, EOFY, and settlement weeks.
Automation is a relationship, not a one-shot delivery. Platforms update. AI providers change rate limits. Your practice evolves. Monthly plans keep the work running, adapt it when it needs to change, and put a named contact on the phone when your calendar hits a crunch.
Three plans
Three tiers. Six-month minimum.
Six-month minimum on all tiers, so monitoring, patching, and adjustment hours have time to be useful. Plans pick up after the 30-day stabilisation that ships with every Build.
Essential
- Up to 3 workflows monitored with alerting
- Platform and API-change patching within 5 business days
- 2 adjustment hours per month (unused hours don't carry over)
- Named email contact, 1 business-day response
Standard
- Up to 6 workflows monitored with alerting
- Platform and API-change patching within 3 business days
- 5 adjustment hours per month (unused hours don't carry over)
- Named phone line during your industry's crunch periods
- Quarterly optimisation review (30-minute call, written summary)
Advanced
- Up to 12 workflows monitored with alerting
- Platform and API-change patching within 1 business day
- 10 adjustment hours per month (unused hours don't carry over)
- Named phone line with direct business-hours access
- Monthly optimisation review (1-hour call, written report)
- AI-module drift monitoring with prompt revisions as required
Tier fees are indicative entry points. Final monthly figures are confirmed based on workflow count, platform mix, AI-module coverage, and crunch-period expectations. Plans are for work YTG has built, or existing automation reviewed and approved for maintenance.
Named contact and crunch periods
We pick up when it matters.
Standard and Advanced plans include a direct-phone line to your named contact during your industry's crunch periods.
Without a plan
Without a plan. Three risks.
A plan is optional after the 30-day stabilisation. These are the three things we see most often when a practice chooses to run unsupported.
Integrations can fail without anyone noticing.
Karbon, Salestrekker, and Rex ship API changes on their own schedules. Without monitoring, a failing integration can run for days before anyone notices. The first symptom is usually a client calling about information that never arrived.
AI output quality shifts with every provider update.
Frontier providers update their models without explicit notice, and behaviour drifts in ways the workflow cannot predict. Without monitoring, the drift surfaces months later as general dissatisfaction, long after the cause would still have been quickly fixable.
A 30-minute adjustment takes two weeks outside a plan.
Inside a plan, adjustment hours absorb small changes quickly. Outside one, every small change requires a scoped mini-engagement with a minimum charge, a written scope, and a turnaround that starts from our next available window. The work is the same. The cost and the wait are not.
What it is not
Honest about availability.
a 24/7 hotline. We pick up during your crunch periods. Outside those, we respond on your plan's SLA.
unlimited adjustment hours. Each plan includes a fixed adjustment budget. Additional work is scoped separately.
a replacement for new Builds. A plan maintains what is built. New workflows are new Automation Build engagements.
Common questions
Before you pick a plan.
Can we bring you in for work someone else built?
Yes, but we need to audit it first. A one-off review engagement (scoped like a mini Workflow Audit) establishes whether the existing work is eligible for maintenance under our SLA. Sometimes we find that rebuilding parts is cheaper than maintaining them. We say so honestly.
What counts as 'adjustment hours'?
Small changes to existing workflows: a new field captured, a branching logic tweak, a notification recipient added, a threshold changed. Work that requires redesign or adds a new workflow is a Build, not an adjustment. Unused adjustment hours do not carry over to the next month.
What's your average response time?
Standard tier: three business hours to first response during crunch periods, one business day outside them. Advanced tier: one business hour during business hours, four business hours outside. API-change patching timelines are in the tier table above.
What if you lose the team member who knows our stack?
Every engagement is documented in a runbook your practice owns. Your named contact is not the only person who can work on your stack. At minimum, two YTG operators have walked through it before handover. We publish our team's coverage model in the plan agreement so you are not exposed to single-person risk.
Related services
Keep exploring the practice.
See all five services →Workflow Audit
$1,500 fixed. Two weeks. Credited against your first Build within 30 days.
Continue →Automation Build
Native features configured first. Integration and exception handling layered around them.
Continue →AI-Assisted Operations
Document extraction, classification, policy lookup, review-first drafting. No autonomous agents.
Continue →Orchestration & Exception Handling
The runbook, fallback flows, operator surfaces, and alerting for after the happy path breaks.
Continue →Discuss a plan.
Happy to talk even if YTG did not build your current automation stack. We will audit and say honestly whether we can maintain it.
Get in touch →