The Basics
What is Advance Continuous?
Advance Continuous is Enable's flat-rate subscription for Run work — the ongoing advisory, maintenance, monitoring, ticket support, and light enhancements that keep your Zoho environment healthy and improving. You commit to a tier, and Enable provides agreed capacity continuously — no per-task billing, no meter running.
It comes in three tiers — Orchestrated Advisory Active — each with its own capacity, inclusions, and SLA.
How is this different from just calling you when something breaks?
Project-by-project means every request starts from a standing stop: something breaks, you contact us, we scope it, quote it, you approve it — and only then does work begin. You pay three times on every cycle: once for the fix, once in the delay while the quote cycle runs, and once — invisibly — because whoever picks it up has to re-learn your system before touching it.
Continuous flips that. Capacity is already reserved, so work starts when the issue arrives, not when the quote clears. The response time is contractual. And Enable already holds the operating knowledge of your environment, so you never pay re-discovery.
"Break-fix means you pay whenever something goes wrong, whatever it costs, whenever we can get to it. Continuous means a fixed quarterly number, a guaranteed response time, and a team that already knows your system."Isn't break-fix cheaper? Some months nothing goes wrong.
Break-fix feels cheaper only in the months nothing happens. You're not saving money — you're carrying unpriced risk. When something does break, you pay whatever it costs, whenever we can get to it, with no response commitment and a scope-quote-approve cycle in front of the work.
The real question isn't which is cheaper. It's whether the system you invested in has an owner, or whether ownership is improvised every time something goes wrong.
How does project-by-project compare, side by side?
| Project-by-project / break-fix | Advance Continuous | |
|---|---|---|
| When work starts | After scope, quote, and approval | On arrival — capacity is reserved |
| Response time | No commitment exists | Contractual SLA by tier |
| System knowledge | Re-learned (and re-paid) each engagement | Held continuously by Enable |
| Budget shape | $0 for months, then surprise invoices | Fixed quarterly, CFO-plannable |
| Relationship | Reactive — you call when it's broken | Includes advisory, planning, roadmap |
Does Continuous replace project work?
No — and it isn't meant to. Continuous covers Run work: keeping the system operating, improving, and aligned to your business. Anything that creates a new deliverable — a new module, integration, workflow, or application — is Build work and converts to a Project Sprint at the Project rate ($350/Unit), budgeted separately and approved in writing before work begins.
The advantage: Continuous clients get priority Sprint scheduling and streamlined scoping, because Enable already knows the system. Scoping and planning for upcoming Sprints is included in your Continuous fee, within your tier's calibration limits.
Budget & Billing
How is Advance Continuous billed?
Continuous subscriptions are annual commitments billed quarterly in advance — four payment events per year. Two other elections exist: annual prepay (full year at signing, ~10% discount) and monthly billing (by exception, ~10% premium, requires executive approval).
Billing frequency determines when invoices land — not the length of the engagement. The annual commitment is the contract term regardless of election.
How do I justify this budget internally?
The line for your CFO: Continuous converts an unpredictable series of emergency invoices into a fixed quarterly operating expense — a known number that can be planned, with a response-time guarantee attached.
It also captures spend that break-fix hides: re-discovery costs on every engagement, delay costs while quotes cycle, and the business cost of revenue-impacting outages sitting in a queue with no SLA. Those costs are real either way — Continuous just makes them visible, bounded, and budgeted.
What do the tiers cost?
| Tier | Monthly rate | Shape |
|---|---|---|
| Orchestrated | from $3,850 | Co-managed infrastructure oversight — shared PM, bi-annual business reviews, API health monitoring, 10 hrs/week admin |
| Advisory | from $2,800 | Strategic platform co-pilot — roadmap planning, creative solutioning, uncapped Sprint scoping, 5+ hrs/week admin |
| Active | $1,428 | Proactive upkeep — monitoring, ticket support, workflow and reporting updates, 3 hrs/week admin |
Published configurations are operational baselines — your exact plan is tailored to your ecosystem (admin hours, connected apps, custom API volume, design requirements) during onboarding.
What if my needs don't fit any tier?
Advance Custom is the composer of last resort: when no standard tier matches, Enable composes a flat-rate program from the Baseline Service Catalog around exactly the services, admin hours, and advisory depth your environment requires. Common cases: post-acquisition environments, PE portfolio companies, non-standard stacks. Custom is never the standard motion — if every client got it, it wouldn't be custom.
What's Included
What kind of work is covered by the subscription?
Everything on the Run side: system monitoring and routine maintenance, ticket-based support (bugs, configuration questions, minor fixes), user access and permission management, workflow rule updates and automation adjustments, reporting and dashboard changes, light configuration enhancements, and dedicated weekly admin hours per your tier.
Higher tiers add strategic advisory and roadmap planning, creative solutioning and UX-led design, continuous Sprint scoping, shared PM allocation, bi-annual business reviews, and active API/webhook health monitoring.
What's explicitly NOT covered?
Build work — anything that creates a new deliverable. A new module, a new integration, a new portal, a data migration: these convert to Project Sprints at $350/Unit, scoped and approved in writing before work begins. Your Continuous program makes those Sprints faster and cheaper to start (scoping is included, and Enable already knows the system), but the build itself is budgeted separately.
What are the response-time commitments (SLAs)?
| Tier | Revenue-impacting | Standard tickets | Advisory / strategic |
|---|---|---|---|
| Orchestrated | 4-hour response | 4–24 hrs | Next session / BAbR |
| Advisory | 2–24 hrs | 4–24 hrs | Next scheduled session |
| Active | 4–48 hrs | 4–48 hrs | Next scheduled session |
All SLA clocks run Monday–Friday, 9 AM–6 PM Eastern. Issues submitted outside hours queue for the next business day. Without a Continuous subscription, no SLA exists — response commitments are a feature of the ongoing relationship, not something a one-off project can carry.
Is design and creative work included?
On Orchestrated and Advisory tiers, creative solutioning and UX-led module interface design are included. On Active, creative work is available at Sprint pricing. This matters more than it sounds: most partners deliver functional systems — Enable delivers systems that get adopted, because they look and feel right to the people using them daily.
Getting Started
We're an existing Enable client. How do we move to Continuous?
If you came through Advance Launch or a prior Enable project, the transition is streamlined — the System Architecture Audit is waived, because Enable already engineered and knows your environment. You select a tier, and the subscription begins on its annual term with quarterly billing.
For Advance Launch clients specifically, the Continuous transition was signed at day one — it's a contractual transition at the midpoint, not a new sale.
We're new to Enable. Can we start on Continuous directly?
Yes — with one prerequisite. Because Continuous carries legally binding, SLA-backed response commitments, Enable requires a one-time System Architecture Audit first ($5,000–$10,000 fixed price depending on footprint, 2–3 week delivery). We cannot responsibly assume operational liability for custom logic, workflows, and API layers our team didn't engineer without a baseline discovery.
You receive two deliverables either way: a Pristine System Architecture Summary and a Prioritized Findings Report — yours to keep regardless of what you do next.
Can we change tiers mid-program?
Tier changes are an executive-sponsor decision on your side and are handled as a program change, not a renegotiation of the relationship. Your program is also calibrated during onboarding — admin hours and inclusions can be configured within a tier before a tier change is needed. Talk to your Enable account contact; the escalation path runs through Mike Lauer (Account) and Jeff Kroeker (Client Success).
What does the cadence of the relationship look like?
Weekly or bi-weekly service delivery check-ins during active phases; Sprint review and planning every two weeks when build work is in motion; and on Orchestrated, bi-annual business reviews with technical roadmapping. Scope ideas that surface mid-stream go to the Parking Lot — captured commitments to review at the next planning session, not surprise invoices.