Taking over a site
New hands on your site, all of it still yours.
You keep the site, the hosting and the code. A new team reads what the last developer left and tells you in writing what it found. Then you decide what happens next.
Short answer
How does a new team take over my WordPress site?
werun.dev takes over WordPress sites another developer built, and most of the sites it looks after started that way. You gather the access you have, and the team reads the site before touching it. You get a written note of what works, what to fix first and what each fix costs. Your code goes to your repository, under your licence. Then Care, from $1,200 a month per site, or a Retainer keeps it running.
- First step
- A look at your site, in writing
- Your code
- In your repository, with a note
- Then
- Care from $1,200 a month
- Plugins we have written
- 80+
In your words
What inheriting a site feels like, and what a clean handover changes.
What happens: Your developer left and nobody knows how the site was built.
What changes: You get a written note of what is there: plugins, theme, hosting and backups.
What happens: Passwords live in old emails, and one person has them all.
What changes: Logins move to your Client Portal, and our team signs in without your passwords.
What happens: Custom code has no notes, and every change feels like a gamble.
What changes: The code goes to your repository with a written note on how it works.
What happens: You fear a new team will want to rebuild everything.
What changes: The note says what works and what needs fixing, and you choose what we do.
How it works
A handover in five steps, with you deciding at each one.
Each step lights up in order. Under it, what you hold once that step is done.
You gather the access you have
The WordPress admin, the hosting and any code repository. Partial is fine: tell us what you have.
You getA list of what is missing and how to recover it
Someone reads your site before touching it
Plugins, theme, custom code, hosting and backups. Your live site stays exactly as it is.
You getA written note: what works and what to fix first
You choose what happens first
Each fix in the note has its price. You approve what we do, and when, in your Client Portal.
You getThe price of each fix, approved by you before it starts
Your code moves to your repository
Every file we keep or change lives there, under your licence, with a note on how it works.
You getYour code in your repository, with a note on how it works
Care or a Retainer looks after it
Updates tried on staging, checked backups and a report each month. The first report records the site as we found it.
You getA first report: your whole site as we found it
What changes for you
What you hold once the handover is done.
A handover is done when you could hand the site to anyone. These three things show it.
Your code in your repository
Under your licence, with a note on how it works. If you ever leave us, all of it stays with you.
Access you control
Our team signs in from our CRM with a link that works once. Your admin passwords stay yours.
A starting point on record
The first monthly report records the whole site as we found it. Every later one is compared with it.
What it costs
What looking after an inherited site costs, from the first month.
The look comes first. Then you pick how the site is looked after, and you can change from one month to the next.
Care
$1,200 a month per site
The inherited site updated, backed up and watched, with a report every month.
- 10 hours of work a month
- Every update tried on a staging copy first
- Backups checked, so a restore works
- A first report of the site as we found it
Retainer
$4,800 a month
For a site with custom code that keeps growing: care plus new work every month.
- 40 development hours a month
- One engineer who learns your code
- Updates and backups handled for you
- New pages, features and fixes
Ad hoc
$120 per hour
For fixing what the look found, one task at a time.
- Minimum task length: 30 minutes
- Every hour logged against its task
- No monthly commitment
Custom plugins or a custom theme can need more hours. The written note says how many before you choose. See every engagement
Your next step
Tell us your goal, we reply within 2 hours.
Write it the way you would tell a colleague. A person reads it and answers on business days.
- A written answer with what it takes and what it costs
- You decide before anything starts
- We sign an NDA if you need one
Free first look
Tell us what you need.
Proof
What a site we take over gets, and you can see it now.
These are ours. They go onto the sites we take over, as they do on the ones we build.
The free SEO and AI audit
A first look from outside, in about a minute: speed, broken links, missing pages and how Google reads your site.
See itwerun. Toolkit
Installed on the sites we take over to run, at no charge. It keeps a record of who changed what, and when.
See itThe monthly report
The hours, the updates and the checks of each month. The first one is your starting point.
See itWorking with us
You stay on the job, we keep you in the loop.
Your project, approvals and invoices live in the Client Portal. You ask for a change by clicking on your own site. With Care, a written report arrives every month.
01Client Portal
Projects, requests, invoices, proposals and contracts in one place. Ask it a question and it answers from your own records.

02Monthly report
Every month, in writing: what we changed on your site, what we watched over and what comes next.

03Client Feedback
Click anything on your own site and say what you want. That's it: the team gets it as a task with a screenshot, and you watch it get solved.

What clients say
Teams like yours, in their own words.
“The client portal, the feedback extension and the WordPress security alerts have been very intuitive, pretty turnkey. Just this past week getting comfortable with it, it’s been really helpful. We’re rolling it out to our core team. Nice job.”
WordPress maintenance questions
What should I ask my previous developer for?
The WordPress admin, the hosting account and the code repository, if there is one. Ask for the domain login and any premium plugin licences too. Notes on custom code help most. Send us what you get, and the written note lists what is still missing and how to recover it.
What if my previous developer is unreachable?
Start from what you still control, such as the hosting account or one admin login. The hosting account can be enough to recover the rest. Tell us what you have, and the written note says what is missing and how to get it back. Your live site keeps running while this happens.
Is it better to rebuild my site or keep what was built?
Keeping it is the starting point, and a rebuild is your call once you read the note. The note says what works, what needs fixing first and what each fix costs. A rebuild makes sense when the theme or the code costs more to keep than to replace. Nothing changes until you approve it in your Client Portal.
How long does it take to take over a WordPress site?
It depends on what you have: access, a repository and notes make it quicker. The first reply comes within 2 hours on business days, with the first step. The look at your site happens before anything changes. The written proposal then states how long each step takes, and Care starts once you approve it.
What does it cost to take over a WordPress site?
Looking after it costs what any site costs: Care is $1,200 a month, a Retainer $4,800. Fixing what the first look found is $120 per hour, or a sized price you approve first. Custom plugins or a custom theme can need more hours. The written note says how many before you choose a plan.
Who owns the code and the site after the handover?
You do. The code lives in your repository, under your licence, with a note on how it works. It is GPL, like everything we write for you. The site and the hosting stay yours too. If you ever leave, all of it stays with you, and werun.Toolkit keeps working on your site.
How does your team sign in without my passwords?
From our CRM, with a signed link that works once and expires in two minutes. It works through werun.Toolkit, so no admin password is shared or stored. Someone who leaves werun.dev loses access to every site within the hour. Any logins you do share are saved in your Client Portal, and each view is logged.
Can you look after custom plugins someone else wrote?
Yes. We have written more than 80 plugins ourselves, so reading another developer's code is everyday work. Each custom plugin gets a note on how it works and goes into your repository. Its updates are tried on the copy like any other. If one needs rewriting, the note says why and what it costs.
Keep reading
More answers on this topic.
Ready to hand your site to a new team?
Tell us your site address and what you have from your last developer. We reply within 2 hours on business days with the first step.


























