Skip to content

(SW® — 01) Service

The contractor vanished, nobody understands the code, there is no access. We audit it, bring it into order and hand over all access to you.

Taking over an existing site: we pick up projects left without a developer

(SW® — 02) Terms

Price
from $25/hour
Timeline
starts with an audit
Fill in the brief 5 min
  • 210+ projects since 2016
  • 3 steps: audit, order, growth
  • 100% of access handed to you

(SW® — 03) Diagnosis

Someone else’s project becomes a problem when…

  1. 01

    The access stayed with the contractor.

    Domain, hosting, admin. Until you have them, the site is not really yours.

  2. 02

    Every change breaks something else.

    It happens when the code has no order and nobody knows how it is built.

  3. 03

    Nobody knows what state the site is in.

    Versions, backups, security: without an audit it is unknown, and you find out at the worst moment.

  4. 04

    You fear a new contractor will rewrite everything.

    Or the opposite: start fixing what would be cheaper to rewrite. We tell you honestly before work begins.

We do not judge the previous developer. We assess the state of the project and pick the cheapest way forward.

(SW® — 05) What is included

What is included

Price
from $25/hour
Timeline
starts with an audit

001. Step

Collecting access and context

We gather the domain, hosting, admin and repository and find out the project’s history.

  • Domain, hosting, admin, repository
  • What has been done and what was promised
  • Who pays for what and who holds which rights

You getA complete list of what exists and who is responsible for what.

002. Step

Audit of code, versions and security

We look at the state of the platform, code and server before changing anything.

  • The state of the code and platform
  • Versions, dependencies and security
  • Speed and backups

You getAn honest verdict: fix or rewrite.

003. Step

Plan and estimate

We build a plan from critical to nice-to-have and estimate each stage separately.

  • Priorities: critical, important, nice to have
  • An estimate for every stage
  • Options: fix or rewrite

You getA plan that lets you decide what to do first.

004. Step

Putting it in order

We remove critical problems, set up backups and basic security and put the project in order.

  • Updates and fixes for the critical
  • Backups and basic security
  • Work on a copy, not on the live site

You getA site in a stable state with no surprises.

005. Step

New features and improvements

We add what you need in 1–2 week iterations so you see a working part after each one.

  • Stages of 1–2 weeks
  • A demo after every stage
  • Integrations: CRM, payments, messengers

You getA project that grows again instead of fading.

006. Step

Documentation, handover and support

We describe how everything works, hand over the access and, if you wish, stay on for support.

  • A description of the architecture and deployment
  • All access in your hands
  • Support on a subscription with no minimum period

You getA project anyone can pick up, and peace of mind about its condition.

(SW® — 04) Who it is for

Who it is for

© — 001.

The developer has vanished

The domain is not in your name, someone else pays for hosting, nobody remembers the admin password. We give you control of your site back.

© — 002.

Code nobody understands

The site works, but any change breaks something else. We audit it and tell you honestly whether to fix or rewrite.

© — 003.

A project stuck halfway

The previous contractor did not finish the job, or the site needs new features. We pick it up and finish it.

(SW® — 06) Comparison

Take over blindly or with an audit?

Taking over without an audit Working with SWEB
Start They dive straight into the code An audit of the code, versions and security first
Decision Everything is patched, even when rewriting is cheaper We say honestly when rewriting is cheaper than fixing
Access Stays scattered We collect and hand over the domain, hosting, admin and repository
Risk Changes go straight to the live site Changes are tested on a copy first
Knowledge Lives in one developer’s head We document the architecture and deployment so anyone can pick it up
Afterwards The contractor vanishes and you start over Support on a subscription with no minimum period

(SW® — 07) Stages

How we take a project over

We always start with an audit, so we never name a price blindly.

© — 01 Start here

Project review

We look at the code, versions, security and access.

free

Start: before work begins

  • The state of the code and platform
  • Versions, backups, security
  • What is going on with domain and hosting access
  • An honest verdict: fix or rewrite

© — 02

Putting it in order

We fix what is critical, collect access and document.

from $25/hour

Start: after the review

  • Updates and fixes for critical problems
  • Backups and basic security
  • Collecting and handing over all access
  • A description of the architecture and deployment

© — 03

Growth and support

New features, changes and support on a subscription.

from $25/hour

Start: within a day

  • New features in iterations
  • Content changes and small tweaks
  • Support on a subscription: updates, backups, monitoring
  • No minimum period

(SW® — 11)Client reviews

Client reviews

What the companies we have worked with have to say.

All reviews

We sold dancewear through Instagram and were drowning in DM orders. The team built a store where the customer picks size and colour themselves, and orders finally stopped getting lost. Worth adding: we have run the catalogue ourselves ever since, without coming back for small changes.

Anna Founder

(SW® — 09) Guarantees

No drama, no surprises

  • 01

    Honest about the project’s state

    We say plainly when rewriting is cheaper than fixing, and show what exactly is wrong.

  • 02

    All access is yours

    After the work the domain, hosting, admin and repository belong to you. No dependence on us.

  • 03

    No picking apart others’ mistakes

    We care about the state of the project and the plan, not about finding someone to blame.

  • 04

    No minimum period

    Support is monthly, you can leave at any time and the access stays with you.

(SW® — 10) FAQ

Questions about someone else’s project

001. Do you work with sites built by someone else?

Yes. We audit first: we look at the code, versions and security. If the state is critical, we bring it into order first and then take it on for support.

002. The domain and hosting are not in my name. What now?

We will advise on the steps and help you gather access to the domain, hosting and admin. There is a detailed walk-through in our article about a contractor who vanished and left no access.

003. What if the code is in terrible shape?

We will say so plainly. Sometimes rewriting is cheaper than fixing. We show what is wrong and offer options with an estimate.

004. What platform do you work with?

Any common one: WordPress, WooCommerce, OpenCart, Shopify and others. If the platform is rare, we first check whether we are a fit and say so honestly.

005. How much does it cost?

Hourly work from $25/hour. We name the scope and the sum after the project review, once it is clear what needs doing.

006. Why not hand someone else’s code to AI?

AI can explain a piece of code, but it does not know the project’s history, cannot see your hosting and is not accountable when something breaks. We use AI as a tool, but a person stays responsible for the result.

007. Can we stay on support afterwards?

Yes. Support is on a subscription with no minimum period: updates, backups, monitoring and changes within the package hours.

(SW® — 12) Next step

We will show your project’s state and what to do with it. For free.

Send the site address and briefly describe the situation. We will look at its condition and tell you honestly which route is cheapest.

Fill in the brief
No commitment and no prepayment.
Discuss Project