Maintenance & support
Maintenance is the per-site care plan that keeps a shipped system healthy: monitoring, dependency updates, small changes, and incident response — priced per site, billed monthly, under your agency’s brand.
For agencies that resell ongoing care plans — or that just shipped a build and want the 2 a.m. problem to have an owner.
- Per site / month
- $200–$500
- Pilot to proof
- 2 weeks
- Defect warranty
- 90 days
What the care plan actually covers.
Software doesn’t stay shipped: dependencies age, APIs deprecate, certificates expire, and small change requests arrive forever. Maintenance gives that work a place to go — a monthly, per-site care plan your agency resells under its own brand, at whatever markup you choose.
The deliverable your client sees is the monthly report: what was monitored, what was updated, what changed, what’s recommended — formatted for your letterhead, sent to you, never to them.
Maintenance covers systems we built. For a system we didn’t build, the pilot is the on-ramp: one fixed-scope project — an audit, documentation, the first fixes — to take ownership properly before we commit to keeping it healthy.
When a care plan beats a rescue.
The build just shipped
Handover day is when the ownership questions start: who watches it, who updates it, who answers when something breaks. A care plan turns those questions into a line item your agency sells.
The care plan is the product
Agencies package hosting-plus-care at a monthly price; the engineering behind it has to be real. We’re the bench behind that plan — your brand on the report, the four-hour reply behind your inbox.
Small changes, forever
Copy tweaks, a new field, a report column — too small to scope individually, too real to ignore. Maintenance absorbs them as part of the plan instead of a quote each time.
What a maintenance month includes.
Included in the per-site care plan ($200–$500 / site / mo, billed monthly). The exact per-site price is fixed in writing when a site comes under coverage.
Monitoring & incident response
Uptime and error monitoring with alerting. When something breaks, the goal is that you hear it from us — with the fix underway — not from your client.
Updates & dependencies
Framework, dependency, and platform updates applied on a schedule, so the system never gets old enough for an update to be scary.
Small changes
The running list of little requests — handled inside the care plan, logged in the monthly report, without a scoping ceremony each time.
How maintenance runs.
Every site under maintenance has a documented runbook from handover: what it is, where it lives, what watches it, and what to do when it misbehaves. Nothing lives in one person’s head — that’s the continuity promise, kept boring on purpose.
The commitments hold here like everywhere else: replies inside four business hours, a written report every month, month-to-month terms you can stop anytime. If a request outgrows “small,” we say so and scope it separately rather than letting the care plan quietly absorb project work.
The mechanics are the same on every line we ship:
- 01Pilot first — Every relationship starts with one real project: $1,000 flat, two weeks, fully credited toward month one of any retainer.
- 02Scoped in writing — Scope, milestones, and — on fixed-price work — the price, signed before work starts. The spec is the contract QA runs against.
- 03One point of contact — Javid scopes every project and answers inside four business hours; every active engagement gets a written status each Friday.
- 04Founder QA — Every deliverable is checked against the signed spec before you see it — behavior, edge cases, and security.
- 05White-label handover — Repos, credentials, and docs transfer to accounts you or your client control. Nothing we ship carries our name.
- 0690-day warranty — If a delivered build doesn’t match its signed spec, we fix it free for 90 days after handover.
Questions about maintenance.
What counts as a “small change”?
A rule of thumb we put in writing: if it changes copy, a field, or a setting, it’s maintenance; if it changes behavior, data structures, or scope, it gets a quote. Ambiguous cases get asked, not assumed — you’ll never find project work smuggled into a maintenance invoice.
How is this different from the 90-day warranty?
The warranty is free fixes when a delivered build doesn’t match its signed spec — defects, our cost, 90 days. Maintenance is paid, ongoing care for a system that works: updates, monitoring, small changes. One covers our mistakes; the other covers time and entropy.
Can our client pay you directly?
No — the relationship, the invoice, and the markup are yours. We bill your agency; what you charge your client is your business, in both senses.
What if we cancel?
Month-to-month means you can. You get the runbook, the credentials are already in accounts you or your client control, and the last report notes anything in flight. Leaving is designed to be safe — that’s what makes staying a choice.
Related service lines.
Web applications
Client portals, dashboards, booking systems, and internal tools — Next.js/TypeScript by default, deployed to accounts your client owns.
Workflow automation
Multi-step business processes — intake, enrichment, reporting, back-office ops — built to run without a person pushing them.
Start with one real build.
Scope your first project as the pilot — $1,000 flat, two weeks, fully credited toward month one of any retainer. If the work isn’t retainer-quality, you keep the deliverable and walk.