Who can take over and maintain automations and integrations someone else built for us?
We can, and below is the order in which we would do it. We have taken over a website that an outside team built and hosted, and we took over the upkeep of a set of workflows already in a client's account. The first step would be a read-only look.
How we would do it
- 1
Inventory who owns what
We list every system, account and login: where each automation runs, who holds the account, what it connects to and who can get in. Lost access is common, and we want to find out early. Anything held by a former builder is listed as a question for you.
- 2
Audit without changing anything
We read before we touch. Read-only access first, then a written list of what exists, what is active, what is dead and what has no error handling.
- 3
Put failure alerts in first
Before fixing anything, we make sure failures reach a person. A workflow that fails silently looks fine until someone notices missing results. Alerts come before improvements because they show what else is broken.
- 4
Write it down
Each automation gets a short description: what starts it, what it changes, what it depends on and what to check when it fails. It is kept where you can read it.
- 5
Fix in priority order
Security first, then silent failures, then anything that blocks money or customers, then tidying. We would change one thing at a time and agree each change with you before it goes live.
- 6
Hand over or keep upkeep
You can take the documented system back, or we keep it updated and monitored on terms we agree with you.
How we work inside someone else's code
When we work inside another developer's codebase, we work on our own branches, changes go in as pull requests the owner of the code merges, and nothing reaches production without approval.
Closest work we have done
For a real estate agency in the US, the website had been built up and hosted by an outside development team, and access to the hosting had been lost. We moved it to a server we run, and now keep it updated and monitored. One thing went wrong: after the move, a hidden admin account came in through a plugin we had inherited. We found it some time later and removed it.
For the same agency, a set of chat-to-CRM workflows was already in the account (we have not confirmed who built them), and we took over their upkeep. Error handlers were added where they were missing or pointed at a deleted workflow, a stalled step was found and cleared, and failure alerts were added where there had been none.
What you give us
- A list of what you know exists, even if it is incomplete.
- Admin access, or the name of whoever holds it, so we can ask them.
- Read access first. Write access only when we agree what we will change.
- A named person who approves changes and receives alerts.
What it costs to start
We quote a fixed price after a short look at your setup.
- Taking over automations
- Fixed price, quoted after a short look
Frequently asked
What if we do not know where everything runs?
Do you need the original developer?
Will you rewrite everything?
Can you work alongside our developer?
Who is behind this
Clutch Top Company 2023 · Upwork Top Rated, $500K+ delivered on Upwork · Fortune 500 work delivered under NDA.
Fixed price after a short look at your setup.
Tell us what someone else built.
Book a 30-minute diagnostic and tell us what runs where, even if the list is incomplete.