01
Website revamp
New information architecture, performance, SEO-preserving redirects, and a visual system that can sit in a procurement thread. Built to be edited and hosted in your name.
Service 07
Your product already exists. It should look and work like it belongs to this year.
Revamps are for companies that already have a site, a web app, or a mobile app, and have outgrown it.
Typical start
Audit in week one, before a rebuild quote
Build length
4–12 weeks depending on what must move
Best for
Sites and apps that already have users or rankings
The problem
The brand moved on. The stack is five years stale. Mobile is an afterthought. The app will not pass the next store review. Staff still use WhatsApp because the web app is slower than paper. A ‘redesign’ from a graphics person did not fix the architecture.
What you walk away with
A current website, web app, or mobile app: faster, clearer, maintainable, and launched with redirects, stores, and a handover, not a pretty staging link that never replaces the old one.
Who this is for
- Companies whose public site no longer matches the work they sell
- Teams stuck on WordPress, a dead freelancer build, or an abandoned Flutter app
- Operators whose web app is used daily and is now the bottleneck
- Founders who need iOS and Android current without hiring two native teams
What this service actually includes
02
Web app revamp
Dashboards, portals, and admin tools that staff actually use, rebuilt around the real workflow, with auth, roles, and the data you already have.
03
Mobile app revamp
A Flutter or React Native rebuild (or a hard stabilise) of an app that is crashing, failing review, or stuck on one platform. Users and store listings stay yours.
04
Migration, not amnesia
URL maps, data exports, user accounts, and a cutover plan. The old thing is allowed to die only after the new one is live.
Typical company engagements
Company website rebuild
Old WordPress or brochure site → a fast Next.js site with the same (or better) URLs, a real enquiry path, and pages the team can update.
Web app that staff actually use
Slow admin or portal → roles, clearer flows, and performance work, on the data you already have.
Mobile app brought back to the stores
Crashes, a failed review, or a one-platform app → a current Flutter or React Native product with the existing users carried over.
How the work runs
Step 01
Audit the current product
We use it like a customer and like staff. You get a short read: what to keep, what to kill, what is unsafe, and whether a rebuild is cheaper than more patches.
Step 02
Define the cut
v1 of the revamp is a product, not a museum of every old page. Redirects, data, and store users are planned before screens multiply.
Step 03
Rebuild in the open
Staging site or TestFlight beside the live one. You compare, not wait for a big reveal that cannot replace production.
Step 04
Cut over & care
DNS, stores, redirects, monitoring. Then a maintenance retainer if you want the same engineer to stay on the new version.
Deliverables
What a company can put in a statement of work.
- A written audit of the current site or app
- The rebuilt product on your domain or in your store accounts
- Redirects, data migration, or user carry-over as needed
- Source and a short operations note
- A recommendation for maintenance after go-live
What the company keeps
Ownership and handover are part of the professional standard.
- The new product live, not a parallel demo that never cut over
- Rankings, users, and data treated as assets, not leftovers
- A stack someone can maintain after we leave
- A clear recommendation: care retainer, or we are done
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
Live URL, store listing, or both
- 02
What you hate about it today (slow, ugly, cannot edit, fails review)
- 03
What must survive: URLs, users, content, brand, data
- 04
Repo and hosting access, or a note that neither exists
- 05
The date the old one has to come down, if there is one
Stack
Tools we actually ship with. We will work inside yours if that is the cheaper path.
Next.jsReactFlutterReact NativeNode.jsExisting APIs
What this is not
Saying no is how companies know we are not selling everything.
- A visual refresh with no engineering when the architecture is the bug
- Keeping a dangerous stack alive because someone is fond of it
- A six-month ‘phase 1’ that never replaces the live site
Questions companies ask
Will we lose our Google rankings?+
Not if we do the unglamorous work: URL map, 301s, metadata, and a sitemap. A revamp that ignores that is just a new site with amnesia.
Can you revamp only the look, and keep the backend?+
Sometimes. If the API and data model are sound, we reskin and restructure the client. If the backend is the reason staff hate the product, we say so and rebuild that too.
Our app is only on Android. Can you add iOS as part of a revamp?+
Yes, that is a common brief. Flutter or React Native lets us take the product to both stores from one codebase, instead of starting a second native team.
Do you need the original developer?+
Helpful, not required. We need the repo if it exists, store and hosting logins, and an honest list of what is broken. If there is no repo, we treat it as a rebuild from the live product.
Is this the same as maintenance?+
No. Maintenance keeps a healthy product current. A revamp is when the product itself is the problem. We will tell you which one you actually need, they have different prices and timelines.
Discuss revamps 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.