Service 04

Software Consulting & Code Refactoring

Sometimes the highest-leverage work is understanding what is already there. I help identify the source of friction, prioritise improvements and make focused changes without unnecessary rewrites.

  • TypeScript
  • React
  • Node.js
  • Git
  • Docker

Typical timeline

1–3 weeks for an audit

What you get

  • Codebase and architecture reviews
  • Performance and UX improvements
  • Legacy modernisation plans
  • Focused bug fixing and technical direction

Step one · Requirement analysis

Before any code, we get the requirements right.

Most project overruns come from building the wrong thing. A short, structured analysis makes the scope, price and timeline clear before development starts.

  1. Symptoms

    What feels slow, fragile or expensive today — bugs, slow pages, risky deploys or hard-to-change code.

  2. Codebase walkthrough

    Structure, dependencies, tests and the parts nobody wants to touch.

  3. Business priorities

    Which improvements matter most to users and revenue, not just to developers.

  4. Constraints

    Team size, deadlines and how much change the product can absorb at once.

The process

How I'll deliver your consulting & refactoring.

Seven clear steps — you always know what is happening, how long it takes and what you get at the end of each one.

  1. 01

    Discovery call

    30 minutes · free

    We talk through the idea, the people it serves and what success looks like. No preparation needed.

    A shared understanding of the goal

  2. 02

    Requirement analysis

    2–5 days

    I map users, workflows, data and integrations, and separate must-haves from later ideas.

    Requirement document + feature list

  3. 03

    Proposal & estimate

    1–2 days

    A fixed, itemised quote for the first milestone with timeline, tech stack and payment stages.

    Signed scope, timeline and price

  4. 04

    UX & architecture

    1–2 weeks

    Screens for the core flows plus the database and API plan, reviewed with you before building.

    Approved screens and technical plan

  5. 05

    Build in sprints

    Weekly demos

    Features ship in small increments to a staging link you can try every week.

    Working software, every week

  6. 06

    Test & launch

    3–7 days

    Cross-device testing, performance and SEO checks, then deployment to your domain or the app stores.

    Live product + handover

  7. 07

    Support & grow

    30 days included

    Bug fixes and small tweaks are included after launch; ongoing improvements are optional.

    A product that keeps improving

Deliverables

  • Written audit with prioritised findings
  • Quick-win fixes applied
  • Refactoring plan with effort estimates
  • Performance before/after report

A good fit for

  • Founders inheriting a codebase
  • Products with recurring bugs
  • Teams planning a rewrite

FAQ

Questions about consulting & refactoring

Does a review automatically mean a rewrite?

No. The goal is to understand the friction and recommend focused improvements; a rewrite is not the default.

What can we look at together?

The codebase, architecture, performance, user experience, or a technical decision that is slowing you down.

Can you help implement the improvements too?

Yes. The work can include focused refactoring, bug fixing and technical improvements where they are useful.

What should I share before a review?

A short explanation of the product, the issue you are seeing, repository access and any constraints.

Contact

Let's plan your consulting & refactoring.

Share a rough outline — I'll come back with questions, a suggested first milestone and the next step.

Hi! Who am I talking to?

What do you need help with?

Service needed

What's your estimated budget?

Project budget

What kind of team are you?

Team type

Tell me a little about your project.

Your project details are only used to respond to your enquiry.
If form delivery is unavailable, your details will stay in the form.