How I work

02
How I work

Four steps take you from a rough idea to a system you own, with the cost and the plan clear before you commit, and something real in your hands after each one.

  1. Fig.01Interview

    01: Interview

    A conversation in plain words, no jargon and no forms, to understand what you actually need.

    Outcome
    Your problem, stated in plain words we both agree on.
    What I need from you
    Explain your business in your own words: the problem you're trying to solve, and what success would look like.

  2. Fig.02Investigation

    02: Investigation

    I dig into the specifics: what exists, what's feasible, and where the real cost and risk sit.

    Outcome
    A clear picture of what's feasible and where the real cost and risk sit.
    What I need from you
    Access to the systems and documentation you already have, and the people who know how they work today.

  3. Fig.03Feasibility report

    03: Feasibility report

    A written recommendation that de-risks the build for you: the direction I'd take, what it involves, and an honest cost, so you commit with confidence. A paid service, at a fraction of what starting the build without it would cost.

    Outcome
    A written recommendation you can take to any developer.
    What I need from you
    Honest steers on priorities, constraints, budget, and timeline, so the recommendation reflects your reality.

    A paid feasibility report, a fraction of the build, before you commit to it.

  4. Fig.04Quote & build

    04: Quote & build

    You approve the plan; I build it end-to-end and stay accountable for the result.

    Outcome
    A working system, delivered end-to-end, with me still accountable.
    What I need from you
    Timely decisions, feedback in one place, and one agreed scope before development starts.

    A fixed quote before any build begins.

Engagement model

  • A paid feasibility report, a fraction of the build, before you commit to it. source: How I work · step 03
  • A fixed quote after it. source: How I work · step 04
  • New ideas mid-build don't quietly inflate the bill: they're planned into the next version, as your decision. source: stated commitment, no ledger exists yet

See how I price a project, in plain words

After launch

After launch, the work can continue

Handover isn't the end of the relationship unless you want it to be. Maintenance, documentation, and making sense of an existing system are all on the table, and where I'm strongest is sizing up a codebase and mapping the road ahead.

Support is arranged per project rather than sold as a fixed tier, and deeper work is scoped for what the codebase actually is, so you get a real plan rather than a blanket guarantee.

source: FAQ · maintenance after launch

A clean exit, by design

Leaving is something you can do at any point, with everything you paid for in hand: the repository, the documentation, and the deployment already sit in your own accounts, and the domain is in your name from day one. What I build is documented and runs on a standard, widely used stack, so a handover reads as an ordinary onboarding for the next developer, not a rescue.

Nothing depends on a private system only I understand, and nothing ties you to me. Moving on to another developer is a choice you're free to make, not a wall you hit.

source: FAQ · who owns it

Tell me what you want to build. I'll find the way that fits your business.

The first conversation is free and in plain words. Then a paid feasibility report gives you the direction, the honest cost, and the right way forward, so you commit with confidence. source: How I work · step 03

Start the conversation