From Enquiry to Launch: A Realistic Timeline for Web and Software Projects
“How long will it take?” depends on scope and decisions. Visual timelines for In...
The day a site goes live, teams celebrate — then six months later the form is dead, PHP is ancient, and nobody has the hosting login. Maintenance is how a business website stays fast, findable, and trustworthy.
This is what Indian SMBs actually need after launch — not an “unlimited changes” package you never use.
Why launch is not done
Day 0
Launch
Looks sharp. Forms work. Everyone is tired.
Day 30
Bugs
Mobile menu, mail routing, a plugin conflict.
Day 90
Drift
Old prices, dead CTAs, new campaign pages never removed.
Month 12
Debt
No backups tested, slow images, staff who left still have admin.
Buyers notice abandoned sites. Search Console does too. Pair upkeep with conversion and SEO: converting websites, SEO + AEO.
The maintenance stack
| Layer | What we check | If ignored |
|---|---|---|
| Uptime & SSL | Loads, HTTPS valid | Trust + ranking hit |
| Backups | Files + DB, restore test | One bad deploy = panic |
| Updates | CMS, plugins, PHP | Known exploits |
| Speed | Mobile LCP, image bloat | Bounce on 4G |
| Forms & tracking | Contact, Analytics, GSC | Silent lead loss |
| Content hygiene | 404s, outdated offers | Wrong prices live |
Design polish is optional. These six layers are not. If you can only afford one habit: monthly form test + backup restore twice a year.
Monthly vs quarterly vs emergency
Call when broken
Looks cheaper
- No one watching SSL or forms
- You pay panic rates at Diwali
- Fine only for a frozen static site
Planned cadence
Predictable
- Monthly: ads/CMS sites
- Quarterly: quiet brochure sites
- Named hours + SLA in writing
Retainer vs call-when-broken
A small retainer is worth it when someone already knows your stack. Spell out hours, response time, and what is a “new page” vs a bug. Unlimited “small changes” without a definition becomes an argument.
Who should have access
- One owner for domain/billing
- One content editor — not five admins
- Agency login with 2FA, stored in a password manager
- Revoke the day someone leaves
A 12-month checklist
Q1
Stabilise
Launch bugs, backups confirmed, form emails in inbox (and spam).
Q2–Q3
Keep current
Updates on staging first if you can. Crawl 404s. Speed pass.
Q4
Prove restore
Restore a backup somewhere throwaway. Review PHP/hosting plan.
- Month 1: launch bugs, backups, forms
- Quarterly: updates, Search Console coverage
- Twice a year: restore drill + image/speed audit
- Yearly: hosting, PHP, who still has admin
Security minimum for SMBs
Unique logins, 2FA, current PHP/CMS. No public installers or phpMyAdmin. WordPress plugin stacks need updates; Laravel apps still need Composer and server patches. Write a five-line incident note: who to call if the site is defaced or mail stops.
When to rebuild instead of patch
Patch when the offer and IA still work. Rebuild when the CMS fights you, mobile is unusable, or every new page takes a week. Treat a rebuild as a project — brief it.
Need aftercare? Talk to 5Stacks with hosting details and how often content actually changes.
Frequently Asked Questions
Do we need maintenance if the site is static HTML?
Yes — SSL, DNS, file backups, occasional content. Less plugin risk, not zero ops.
Is hosting included in maintenance?
Often billed separately. Ask what happens if disk fills or PHP must upgrade.
How fast should someone reply when the site is down?
Agree an SLA. Same-day for outages; next business day for copy is common for SMBs.
Can we maintain in-house?
Yes if someone owns updates and backups. Most SMBs don’t — until something breaks.
Will updates break the design?
Sometimes. Staging and a vendor who knows the theme matter.
What about email on the same domain?
DNS and mailbox issues get mixed with “website down.” Document who handles email.
When is a retainer not worth it?
Frozen site + you accept slower emergency pricing — still keep backups and SSL monitoring.
