Services · Takeover
Your agency is gone, or your system has grown too old to change. We pick it up.
We first make sure your company holds every account the system depends on, then review the code, keep what works and finish or replace the rest. After that, the same team keeps it running.
Before you start, see the website handover checklist.
What you get
What a takeover includes
A takeover has three parts: secure the accounts, review the code, then finish the work.
An account and access check
In plain words: the web address, where the site lives, the code itself, and every service you pay for. We check each one is in your company’s name, and help you move the ones that aren’t.
A review of the code
We read the code, run it and tell you in writing what works, what could break and what is missing. A deeper audit of code and servers is scoped after the call.
A written plan
What to keep, what to fix and what to finish, in order. You approve it before we start.
Checks around what we touch
Automatic checks added to the parts we change, so a fix in one place doesn’t break something that already works.
The missing work, done
Features the old team didn’t complete, or parts of an old system replaced, built and released in small steps while the rest keeps running.
Ongoing support after
The system moves to support and maintenance with the same team, if you want that.
You own the code, the data and every account. If you leave, you take all of it.
Proof
What we can show
The systems we have taken over are covered by NDAs, so there is no case page for them. The work we can show is built with the same checks and weekly reports. Building on Next.js and Supabase? Ampifex, our own product, runs on that stack.
GuideWebsite handover checklistWhat to collect from an agency or freelancer before the contract ends.Read the checklistHow it works
Tell us what you have
Who built it, what works and what doesn’t.
Call and first look
A free call. If the site is public, a free first look with XRay, our own audit tool.
Accounts and code review
We check who holds each account and review the code. Then a written plan.
Finish and run
We fix and finish in the order you approve, then keep the system running.
One hourly rate for the whole team, whatever the role. You approve the scope before we start, and weekly reports show every hour.
Agency gone, or a system nobody dares touch?
Tell us what you still have access to. We’ll tell you what to secure first.
Limits
What this doesn’t include
No access we can’t get legally. If the old team holds the domain or hosting in their name, we can’t move it for you. We tell you exactly what to ask for, and our guide on taking over a website when the developer has gone quiet covers the recovery routes.
No promise to keep every line. We keep what works. Parts that are unsafe or can’t be maintained are rewritten, and we say so in the plan first.
No rewrite into our stack by default. The plan says which parts stay, which get tests and which get replaced, and why.
No free deep audit. The call and the outside first look are free. A full audit of the code and servers is scoped and billed after the call.
FAQ
Questions about takeover
What if we don’t have the passwords?
Start with the domain, then the hosting and the code repository. Our website handover checklist lists what to ask for and how to check you have it.
Can you finish a project another team started?
Yes. We review the code first and tell you what we would keep, fix and finish. We’ve taken over and finished systems other teams left half-built.
Our system is old but still runs. Is that a takeover too?
Yes. We keep the old system running while we work and replace it piece by piece, with tests around each part we touch, so the business doesn’t stop. You approve the plan before we start.
Our agency left in the middle of a migration. Where do you start?
With the accounts and the live system. We make sure orders still arrive and broken addresses redirect, then review the new build and tell you in writing what it takes to finish.
How long does a takeover take?
The first part is fixed in shape, not in length: we list every account and who holds it, read and run the code, and send a written review and plan. Your system keeps running unchanged meanwhile. Moving accounts is usually the slow part, so we start there.
Our shop runs on a platform that no longer gets updates. Can you take it on?
Yes. We read and run the code first. The written plan says which parts stay for now, which get tests around them and which get replaced, and in what order. We have no case on an unsupported platform to show.
Left with a half-built or ageing system?
Tell us who built it and what state it is in. The first thing we check is who holds the accounts.
We reply within one business day, Tallinn time (EET), usually within a few hours, and set up an online call. No obligation.