01
Website & web-app care
Dependency and CMS updates, broken forms, content help, SEO hygiene, SSL, hosting check-ins, and the ‘can you just change this’ list that never qualifies as a new project.
Service 06
We keep the product running after the launch week is over.
Most companies do not need a new build every quarter. They need someone who understands the stack to keep it current.
Typical start
Handover read in the first week
Shape
Monthly retainer: planned hours, not emergencies only
Best for
Live sites and apps that still have to work
The problem
The original developer disappears. Plugins go stale. The SSL expires. A form stops sending. The app will not build on the new Xcode. Staff are afraid to touch the CMS. There is no one to call except a freelancer who has never seen the repo.
What you walk away with
A monthly care arrangement: monitoring, updates, backups, small changes, and a person who already knows the product. The site or app stays current without a new project kickoff every time something breaks.
Who this is for
- Companies that launched a site or app and now have nobody owning it
- Operators tired of paying emergency rates for a form that stopped working
- Teams that need small features and store updates without a full rebuild
- Companies that want a retained engineering team, not a ticket queue abroad
What this service actually includes
02
Mobile app care
Store listings, OS and SDK updates, crash fixes, a new build when Apple or Google demand it, and the small feature that keeps the app in the stores.
03
Security, backups, uptime
Patches, restore-tested backups, uptime checks, and a short note when something actually needs your decision, not a flood of alerts.
04
A dedicated project team
Engineers who already know the product, not a rotating bench. Hours are reserved each month so the work is planned, not begged for.
Typical company engagements
Company website on retainer
Updates, content changes, form and SEO hygiene, and a person to call when the domain or SSL needs a decision.
App still in the stores
SDK bumps, crash fixes, a store screenshot pass, and a release when iOS or Play policy changes.
After a Tech Vibes launch
The same team that shipped v1 stays on for the ‘can it also’ list, instead of vanishing at go-live.
How the work runs
Step 01
Handover read
We take the repo, hosting, stores, and secrets as they are. You get a one-page picture of what is healthy, what is risky, and what should be in the first month.
Step 02
Agree the retainer
A monthly hour block, a response window, and what is in vs a separate build. No surprise invoices for a button colour.
Step 03
Run the cadence
Updates, backups, small tickets, and a short written note each month so you can see what the hours went on.
Step 04
Escalate when it is a project
If the next request is a revamp or a new module, we say so and scope it properly, maintenance does not quietly become a rebuild.
Deliverables
What a company can put in a statement of work.
- A written picture of the current site, app, or API
- Monthly update and backup cadence
- A shared list of small work, with what shipped
- Access sitting in your accounts, not ours
- A clear line for when work should become a project
What the company keeps
Ownership and handover are part of the professional standard.
- A dedicated project team and a monthly written note
- Updates and backups on a cadence, not a hope
- Small changes without a new contract every time
- Access and hosting in accounts the company owns
How a company starts
Send this and we can quote.
You do not need a 20-page RFP. A messy but honest brief is enough for a scoped proposal.
- 01
URLs, store listings, or a repo, whatever exists today
- 02
Who built it, and whether they are still reachable
- 03
What is currently broken or embarrassing
- 04
How often you need changes (weekly, monthly, ‘only when it dies’)
- 05
Hosting, domain, and store accounts, do you have the logins?
Stack
Tools we actually ship with. We will work inside yours if that is the cheaper path.
Next.jsReactWordPress / CMSFlutterNode.jsLinux / hosting
What this is not
Saying no is how companies know we are not selling everything.
- Unlimited redesigns disguised as ‘small tweaks’
- 24/7 phone support or a helpdesk for your customers
- Maintaining a product we have told you is unsafe to keep
Questions companies ask
Do you only maintain what you built?+
No. We take over sites and apps other people left behind, after a short read so we are not guessing. If the codebase is unsafe to touch, we will say a revamp is cheaper than care.
What is in a typical month?+
Updates, backups, a few small tickets, store or hosting hygiene, and a written note. A new feature that needs design and architecture is scoped as a project, not hidden in the retainer.
Can you host the site for us as well?+
We can run it on your cloud or a hosting account in your name. We do not lock the company onto a mystery server we refuse to hand over.
What if nothing breaks one month?+
Then the hours go to updates, hardening, and the small list you have been postponing. Care is cheaper than the month something breaks and nobody has seen the repo in a year.
Is this 24/7 support?+
No. You get a response window on business days and monitoring that tells us when the site is down. If you need a call centre, that is a different vendor.
Discuss maintenance with us
Tell us what you need: a new product, a revamp, or ongoing maintenance. You will receive a clear response on fit, scope, and next steps.