Care plans
Keep dependencies current, reduce security drift, and reserve capacity for fixes and improvements—without hiring a full-time maintainer. Care plans are retainers scoped in writing so budgets and expectations stay aligned.
Who it’s for
If you own a live marketing site, storefront, or web app and want predictable help each month, a care plan is the right lane. Typical clients already host with us or inherited a codebase they don’t want to babysit alone.
WordPress, Shopify, or Node-backed stacks we’ve built—or we’ve completed a structured handoff from your prior vendor.
Stakeholders who want written scope: what’s in the monthly bucket, how to request work, and how fast we respond.
Organizations that value async updates in a shared workspace over ad-hoc DMs when production is on the line.
What’s included
Exact tasks are listed in your care agreement; below is the shape most teams choose. Everything rolls up to stability, security hygiene, and small improvements inside your monthly allowance.
Framework, runtime, and dependency updates where safe; coordinated WordPress/Shopify/plugin cadences; smoke checks after upgrades.
Review advisories relevant to your stack, tighten obvious misconfigurations, and patch small issues before they become incidents.
Bug fixes, regressions, and minor UX or accessibility corrections that fit the hours and channels in your tier—scoped so triage stays fast.
Short release notes you can forward internally, async status in your project thread, and escalation paths when something breaks badly.
How it works
We start with discovery on your stack, hosting, and risk areas, then put the retainer in writing: tier, hours, channels, and response targets. Invoices align to the billing rhythm in that agreement.
We document what’s in production, who approves changes, and what “done” means for routine care. You get a written tier and assumptions—not a vague “we’ll watch it.”
You file work in the FineWebs client workspace: threads, attachments, and approvals stay in one place—no lost email chains when you need an audit trail.
We batch changes sensibly, verify on staging when it matters, and leave short notes your team can forward. Quarterly reviews (on applicable tiers) keep the roadmap honest.
Illustrative tiers
Illustrative tiers—actual hours, rates, and response targets are set in your care agreement after discovery. We’ll say no to a tier if your stack needs more capacity than the bucket allows.
Light production surfaces with infrequent change but real upgrade needs.
Custom
Active sites or apps with regular content, promos, or integrations.
Custom
Revenue-critical flows, tight compliance, or leadership visibility.
Custom
FAQ
Straight answers before procurement asks for the PDF.