Paying monthly vs calling when it breaks: the actual math

Care plans are priced on what keeps working, not on blocks of someone's time. There are no hour caps and no timesheets: which makes the honest question sharper: when does a monthly plan cost less than fixing things one at a time? Here is the break-even math for my care plans, when one-off wins, and when neither fits.

What the plans actually are

Three care plans, from the services page:

• Essential Care: $299/mo. Uptime and error monitoring, dependency and security patching, a monthly speed audit, automated backups, and an emergency hotfix SLA: first human response within 8 hours, any day. No feature-build hours are included: this is production insurance, deliberately.
• Growth Sprint Plan: $899/mo. Everything in Essential, plus two shipped conversion or feature updates a month, a sub-1.4s load-time target on the pages I touch, and 48-hour turnaround on UI/UX tweaks.
• Fractional Product Partner: $2,200/mo. Everything in Growth, plus a continuous feature queue shipping every 48–72 hours, full architecture ownership, and a weekly async walkthrough.

Advisory is separate, and it is the one place hours are quoted, because senior judgement is literally what it sells ($600/mo for up to 4 hours, $1,200/mo for up to 10). Most maintenance decisions still run through the three care plans.

The break-even math

Use pay-per-fix Quick Fixes as the baseline: $100–$500 per issue, 48 hours to a week, 30-day bug-fix warranty.

• Light user: one small fix per quarter (~$150). That is ~$50/mo equivalent. Essential Care is roughly six times the fix cost, so buy it for downtime exposure, not for the fixes: if a bad week would not cost you more than $299, stay one-off.
• Steady site with production risk. Essential Care is not a bundle of fix hours: it does not replace Quick Fixes one-for-one. What it buys is the work pay-per-fix does not cover at any price: monitoring, dependency and security patching, backups, a monthly speed audit, and an 8-hour emergency response SLA. If an outage during a launch or campaign week would cost more than $299, it is the cheaper line item; if not, stay pay-per-fix and I will say so.
• Active storefront: a monthly iteration. Growth at $899/mo competes with per-fix work ($100–$500 per issue) plus a separately quoted iteration (Web Development starts at $600): and adds two shipped updates a month, 48-hour turnaround and a load-time target. Growth wins outright, and the iteration ships sooner because context already exists.
• Continuous ship: weekly improvements. Per-fix quoting overhead alone eats days. The Fractional plan wins on throughput before price.

Rule of thumb: under about one fix a month and no downtime exposure, stay pay-per-fix. A steady site where a bad week costs more than $299, take Essential. One monthly iteration on top, take Growth. Size your case with fix frequency first and revenue math second.

There is a second, quieter saving: prevention. Monitoring, dependency updates, and small performance passes stop the emergency rewrite. One avoided checkout outage during a campaign week can cover months of plan cost. I cannot promise a specific revenue figure for your business, so size it yourself with the same math: your traffic, rate, and order value, then halve the implied lift for a stress test.

One-off: when it wins

Pay-per-fix is the right call when:

• Needs are sporadic and well-bounded ("fix this form," "speed up this page")
• You have internal capacity for content and want a specialist only for code
• You are pre-product-market fit and scope changes monthly
• You want to trial working together before committing

One-off terms here: $100–$500 per fix, 48-hour to 1-week turnaround, 30-day bug-fix warranty on the fixed issue: the same window full builds carry. Get the same in writing from any vendor: scope, turnaround, and warranty window.

Care plans: when they win

A plan fits when the site is a revenue channel, not a brochure:

• Weekly content, product, or pricing changes that need design-safe implementation
• Campaign calendar where "next week" is too late and same-day critical response matters
• Backlog of small improvements nobody prioritizes: speed, SEO hygiene, accessibility, funnel tests
• A roadmap: landing variants, CMS expansions, checkout experiments shipped monthly

Agencies sell this as "your outsourced team" with account-manager overhead baked in. The solo version is simpler: the same senior who scopes also ships, no handoff, no status-theatre meetings.

When neither fits

Honest noes, from the site FAQ and the brief guide:

• Game engines and console builds. Not my stack.
• "Clone X in two weeks" briefs. Needs a team or a timeline I will not fake.
• Full-time workload disguised as a plan. These plans ship scoped work, not a full-time hire. If you need daily full-time output, hire in-house.
• Compliance-heavy builds needing dedicated legal and audit processes beyond a solo practice.

Saying no early is part of the model. The brief guide helps you scope either path so a $600 job does not become a $6,000 rescue.

How months actually run

1. Planning. Ranked list from your backlog plus monitoring findings. Top fixes first, then iterations.
2. Ship in small batches. No big-bang releases for routine months. Each change reviewable, reversible.
3. Progress notes. What shipped, what moved the grader score, what is next. No vanity metrics.
4. Pause or cancel when the backlog empties. A plan that fights to keep you without work is a subscription trap, not a service.

The bottom line

Sporadic needs: pay per fix, $100–$500, no commitment. Steady site with production risk: $299/mo for monitoring, patching and an 8-hour response SLA. Monthly iteration: $899/mo for two shipped updates. Continuous ship: $2,200/mo for a permanent feature queue. Size your case with fix frequency first and revenue math second.

---

Deciding? Book a 15-min fit call with your fix frequency and backlog, or get a one-off quote for the single issue in front of you right now.