status: available for one engagement

Senior engineering, at the speed the tools now allow

AI has made building software dramatically faster. It has not made judgement optional — it has made judgement the entire job. I've spent 22 years developing mine. I use the tools to move fast; I'm the reason what they produce is correct.

$ see-the-method $ talk-to-me

the shift

What changed, and what didn't

what changed

The time it takes to build collapsed.

Wiring, scaffolding, the thousands of small deterministic decisions underneath a system: work that used to take a team weeks now takes days. This is real, it is here, and it is not a marginal gain. On a build with one person deciding and nobody to wait for, it lands directly on your delivery date.

what didn't

Knowing what should be built didn't get easier.

The tools will confidently produce something that runs and is quietly wrong: an access model that doesn't hold, a data design that traps you in eighteen months, an assumption nobody validated. They cannot tell you that. Experience can.

the consequence

The saving exists. It just isn't reaching you.

You're paying for two things. People to build it, and everything that keeps them in step: meetings, sign-offs, handovers, waiting. Building got faster. The waiting didn't. And no firm can hand you that saving without giving up most of what it bills for, so your number looks much like it always did.

where the leverage is

I'm the engineer. AI expedites.

method.logthe short version

        // the engineering
        Mine. The system design, the data model, the access model and the failure cases are decided by me, before anything is generated. I use AI here too, but as an adversary — I ask it to attack my design and tell me what I've missed. Interrogating a decision isn't delegating it.
         
        // the acceleration
        This is where the tools earn their place. Once the shape is fixed they fill it in, and that filling-in is most of what you're billed for in a conventional quote.
         
        // the review
        Nobody reads fifty thousand lines, and anyone who tells you they do is selling something. What gets read closely is where the risk actually sits: authentication, permissions, anything touching money or the data model, anything at a system boundary. The rest is proven by behaviour — it does what the specification says, under test, or it doesn't ship.
         
        // no black boxes
        There is no part of your system I can't sit down and explain to you. That's a different claim from having typed it, and a harder one to meet.
         
        // accountability
        My name is on the contract. "The tool wrote that part" isn't a defence available to me, so I don't build as though it were.
      

$ read-the-full-method

what you get

A working system, in your account

I design and build systems on AWS end to end — the API, the identity and access model, the data layer, the infrastructure that runs it — as one coherent thing, defined in code, deployed into accounts you own. Not a prototype you then have to have hardened by someone else.

A number and a date, before you commit.

Fixed price and fixed delivery date in writing, agreed against a scope we sign. Not an estimate that drifts. Not hours billed as they accrue. Bring your own scope document and that step is mostly me checking and signing it — I'd rather build your system than write about it.

One person, holding the whole picture.

No account manager, no coordination layer, no juniors learning on your budget. The person who designs it is the person who builds it and answers your email.

Yours from the first commit.

Your repository, your AWS account, every resource defined in CloudFormation. Nothing about this engagement leaves you dependent on me afterwards.

who this is not for

Straight, no hedging

eligibility.tsguard clauses

        if (you_need_a_team_not_an_engineer) return null;
        If your procurement requires a vendor with staff redundancy and a balance sheet, I'm not that vendor — and I'd rather say so now than waste your onboarding cycle.

        if (scope_is_still_moving) return null;
        A fixed price requires a fixed scope. If you're still deciding what the thing is, that's a real and legitimate stage — it just isn't this one.

        if (you_want_the_cheapest_number) return null;
        There will always be someone quoting less by generating code nobody senior has read. You can buy that. You'll pay for it later, and not to me.
      

get in touch

Tell me what you're trying to build

A paragraph is enough to start. If you've already been quoted, send that too — I'll tell you plainly whether I can do it better, and roughly by how much, or that I can't. No cost, no pitch deck.

$ mail --to quoteme@definitionofdone.dev $ why-the-quote-doesnt-work