01
Week one, the plan is already running.
Hosting, monitoring, and a named owner — not a discovery quarter. You can already raise a change on software that's live.
Software maintenance
Software maintenance services — we don't disappear after launch.
Custom software needs an operator. Hosting, backups, monitoring, security updates, bug fixes, and a path for small improvements are how the product stays a business system rather than a static handover. Maintenance is optional, and it is the natural second phase of the work.
02
10+ years maintaining and growing apps.
That experience is how we keep production software stable and able to change — uptime, patches, and the next small improvement treated as operations, not leftover project hours.
When generic software stops fitting.
Launch is treated as the finish line
Libraries age. Browsers change. The first real customer finds the edge case nobody tested.
Nobody owns uptime
Hosting was 'included' until the certificate expired or the backup was never restored.
Every change is a new proposal
Without a monthly rhythm, small improvements wait months and then arrive as expensive mini-projects.
Security is postponed
Updates pile up because they are nobody's job. That is not an acceptable state for software that holds customer data.
Capability
Built around the workflow, not a template.
The application has a home that is monitored, not a forgotten server someone stood up at launch.
Backups that have been restored, not only scheduled. Recovery is a practised operation.
Uptime, errors, and the signals that mean a customer is already feeling it. Someone is looking before you are.
Libraries and platforms age. Patches are a monthly job, not a project you start after a scare.
The first real customer finds the edge case. Fixes land on software that is already in production.
Slow queries and heavy pages are treated as operations, not as leftover project debt.
A named owner for 'it is down' and 'this screen is wrong'. Support is not a shared inbox with no SLA.
Vendor APIs change. The connection is maintained so a payment or shipping update is not an emergency rebuild.
The next small change does not wait for a new proposal. Growth and Partner plans hold hours for work already in use.
Larger change continues on a monthly rhythm, on a system that is already live — not as a sequel project from zero.
Approach
How the plan actually runs.
01
Care, Growth, or Partner
Three plans: keep it stable; keep it stable and improve it a little each month; or treat it as an ongoing product with a technical review.
02
Hours that are honest
Growth includes 2 development hours a month. Partner includes 5. Work beyond that is billed separately so the plan does not pretend to be unlimited.
03
Production judgement, not a lock-in stunt
You can run hosting yourselves if that is the agreement. The offer exists because most teams do not want to staff this work internally on day two.
Ongoing partnership
Optional maintenance after launch.
Launch is the start of a working system, not the end of the relationship. Maintenance covers the operational work that keeps custom software safe and useful. Additional development beyond the plan is billed separately.
Care
$149/month
Keep the software stable, secure, and online.
- Hosting
- Backups
- Monitoring
- Security updates
- Bug fixes
GrowthMost complete
$299/month
Stability plus a small monthly development allowance.
- Everything in Care
- 2 development hours / month
- Small improvements
- Integration support
- Priority support
Partner
$599/month
An ongoing product partnership after launch.
- Everything in Growth
- 5 development hours / month
- New features
- Integrations
- Priority support
- Monthly technical review
Related services
Custom software development
Maintenance is phase two of a build, not a standalone hosting shop.
Custom software development
Custom CRM development
CRMs change as the sales process changes. Plan for that.
Custom CRM development
Get a project estimate
If you already have software, say so — maintenance of a system we did not build is scoped separately.
Get a project estimate
Questions
- When does the plan actually start?
The first week of a maintenance plan is already operational: hosting, monitoring, backups, and a named owner. You do not wait through a discovery quarter before anyone is on-call.
- Do we have to subscribe?
No. Maintenance is optional. If you have internal engineering, you can take operational ownership after handover, according to the agreement. Custom application hosting and software support after launch are the usual reason teams stay with a plan.
- What do the plans cost?
Care is $149/month, Growth is $299/month, and Partner is $599/month. Additional development outside the included hours is billed separately.
- Can you maintain software you did not build?
Sometimes, after a review. Unfamiliar codebases need an assessment before we can offer a responsible plan.
Tell us what the software needs to do.
Share the workflow, the current tools, and the outcome you need. We will come back with a scoped project estimate — not a generic package.