Skip to content

Service 06 · Existing projects

Fix, finish or extend the software you already have.

Bug fixes, new features, cleanup and maintenance for websites, apps and systems that someone else built, or that were never finished.
Discuss your project

For example

  • A bug that keeps coming back
  • A feature your current site or app is missing
  • A project the previous developer left unfinished
  • Code that has become slow or hard to change

Who it is for

Usually, people in one of these situations.

  • A business whose developer is no longer available
  • A team with a working product and a list of things to fix
  • A founder with a half-built project and no one to finish it
  • Anyone who needs a second opinion before spending more on a project

Problems it solves

What it fixes.

Something broke and nobody knows why

We find the cause first, explain it in plain language, and then propose the fix with its cost.

Every change takes longer than the last

Code that grew without a plan becomes expensive to touch. Restructuring the worst parts can make the next features cheaper.

The project was never finished

We review what exists, tell you honestly what is usable, and scope what it takes to get it working.

What we build

What we can build or change.

Bug fixing

Finding and fixing faults in websites, web apps, bots and desktop tools.

New features

Adding functionality to a product that already works.

Cleanup and restructuring

Improving code, performance or structure so the project is easier to change.

Maintenance

Updates and ongoing support, under a clear agreement if you want one.

A typical project

What a project includes, and what we need from you.

The exact list is written into your proposal. This is what it usually covers.

We handle

  1. 01Reviewing the code and setup before quoting anything
  2. 02A written list of what we found, what we propose and what it costs
  3. 03Fixes and changes made against that list, with review points
  4. 04Testing that the change works and did not break something else
  5. 05Notes on what was changed, for you and for whoever works on it next

You provide

  • Access to the code, hosting and any services the project uses
  • A description of the problem or the feature, with screenshots if possible
  • Any documentation or notes from the previous developer
  • A way to test changes safely, or permission for us to set one up

Do not have all of this yet? That is normal. Send what you have and we will work out the rest together.

After launch

What happens once it is live.

Bug fixes in the work we do are free for 30 days after we deliver it. If you want someone to keep looking after the project, ongoing maintenance is optional, monthly or as needed, and priced in the proposal.

Questions

Questions about existing projects.

Will you work on code someone else wrote?

Yes. We review it first so the proposal reflects what is really there. If something cannot be fixed sensibly, we will say so before you pay for an attempt.

Do you need access to my server?

Usually some access is needed. We agree what is required and how it is shared during scoping. Please do not send passwords in your first message.

Can you take on ongoing maintenance?

Yes. Maintenance is optional, either monthly or as needed, and priced in the proposal, with what is covered written down. Mention it in your brief if you need it.

Next step

Tell us what needs fixing.

Describe the problem in your own words. We reply within one business day with questions, then a written scope and price. No commitment until you accept it.