Maintenance & Support

Yes, after a paid code review — a fixed-price exercise where we map the codebase, dependencies and risks. You get an honest written assessment either way: continue, refactor, or rebuild. If the code is in worse shape than expected, we say so before you commit to a plan, not after.

Standard plans include next-business-day acknowledgement; priority plans include same-day response for critical issues, with fix targets agreed per severity. The exact numbers go in your agreement in writing — an SLA that lives in a salesperson’s memory is not an SLA.

Plans are sized to the product: a small tool needs a light monthly plan, a revenue-generating SaaS with real uptime stakes needs more. All plans run month to month with no long-term contract — we will recommend a tier after seeing your product, and downgrading is always allowed.

The invisible work — dependency updates, security patches, backup and uptime checks — plus your bug fixes, and a plain-language monthly report listing everything done and anything found. If a month is quiet, the report says so; you should always know exactly what you paid for.

Both. Each quarter we plan a small feature roadmap with you, sized to your plan, and ship it in releases. This is exactly how our own products improve — steady quarterly releases beat rare big-bang rewrites, for desktop software and SaaS alike.

Often, yes — this situation is more common than you would think. If any code, credentials or database access survives, we start the recovery from there; if truly nothing remains, we assess whether rebuilding beats reverse-engineering. Either way, the first deliverable is making sure you can never be stranded like that again.

No. Plans run month to month, and the documentation we maintain means you can move in-house or to another team whenever you choose. Escrow protects project payments; for ongoing plans, the exit-anytime terms are your protection.