Response by end of next business day, business hours. Suits a marketing site or an internal tool.
KeevaathTech/Services/Product lifecycle
RUN · KRN
Product lifecycle
Keeping something running once it exists. Priced on how fast we answer instead of on hours logged, and always beginning with an audit.
What this is
Keeping something running once it exists. Upgrades, modernization, maintenance and support, priced on how fast we answer instead of on hours logged.
Every engagement begins with an audit. Taking a monthly fee for a codebase nobody has examined serves neither side, and that rule has no exceptions.
Response time tiers
Standard
Business
Response within four business hours, plus a monthly patch and dependency review. Suits an application that carries revenue.
Critical
Response within one hour for a production outage, extended hours, with a named escalation contact on both sides.
You are buying availability, not a bucket of hours. Each tier includes a monthly allowance, and work above it bills at day rate in half day increments. An annual commitment reduces the price; month to month increases it.
What is covered
Keeping it current
Core, framework and plugin updates. Dependency and version risk managed before it becomes urgent.
Keeping it up
Security monitoring, scheduled backups, uptime monitoring, performance optimization and caching configuration.
Keeping it moving
Production deployment, launch monitoring, content updates and technical support.
Infrastructure
Cloudflare, DigitalOcean, GitHub and GitLab, release pipelines and staging environments.
Named migration routes
The upgrades people are actually stuck in, quoted as defined pieces of work.
React 16 to 19
Including the rendering and effect changes that break silently and not loudly.
Node to current LTS
Where the runtime is unsupported and the dependency tree has to move with it.
Express to Next.js routes
Consolidating a separate API onto the framework already serving the front end.
WordPress to headless
With the content, the URLs and the editorial workflow preserved.
Website care plans
Quoted separately from platform and software maintenance, because they are a different service bought by a different buyer, and pricing them together drags the whole line down.
Three tiers. Updates, backups, uptime monitoring and security patching at the base. Performance monitoring and a monthly content allowance above it. A larger allowance and faster response at the top.
If a plan starts consuming attention it was not priced for, we will tell you and raise it or decline it. Volume does not fix a thin margin.
Questions we are asked
Why do you insist on an audit first?
Because the tier that is sellable depends on what state the thing is in, and quoting a monthly fee blind means one of us is going to be unhappy by month three. The audit is fixed scope and fixed price.
What counts as a production outage?
The service is unavailable, or a critical path is failing for all users. Agreed in writing at the start, with examples, because that definition decides when the one hour clock starts.
Can you maintain something you did not build?
Yes, and most of it is. It starts with the audit, which is how we find out what we are agreeing to.
What happens to unused hours?
They do not roll over, and the price reflects availability, not consumption. If your usage is consistently far below the allowance, we will move you down a tier.
Do you offer twenty four seven cover?
Extended hours on the Critical tier, with a named escalation contact. Genuine round the clock cover needs a rota we do not currently staff, and we will say so instead of promising it.
Start with the audit.
It is fixed scope and fixed price, and it is what lets us quote a maintenance tier honestly. Send the questionnaire and both come back together.