Yours From Day One

Ask a founder what worries them about hiring outside engineering help and the answer is rarely the rate. It is the arrangement. The contractor’s org holds the repo. The invoice counts hours nobody can audit. And the day the payments stop, you find out how much of your product you actually own.

The worst version is a codebase that took months to build, sitting in an account nobody at the company can log into. Leaving costs more than staying, which was the design all along.

If you are choosing between an agency, a full-time hire, and an embedded senior engineer, this arrangement question matters more than the choice between them. These are the terms I run my studio on. Three of them, and none of them is generosity. Each belief is protection for the buyer.

You own the code from day one

Everything I build lives in your repos and your accounts from the first commit. Your GitHub org, your cloud account, and the credentials to all of it. If we part ways, you lose an engineer. You do not lose the codebase, and there is no negotiation about what gets handed over.

Day one means day one. By the time I write the first line, you already have the repo and the deploy target. There is no handover phase at the end, because there is nothing to hand over. It was yours while it was being built.

This is the term that decides what happens after an engagement ends. Lock-in never shows up in the sales call. It shows up months later, when migrating the code out costs more than keeping a vendor you are unhappy with. Working inside your accounts takes that situation off the table. The default is that the client holds the assets, and it stays the default for the whole engagement.

The rate is flat, and the invoice comes first

The rate is $5K per week, billed before each sprint, same rate for everyone.

Billed after, an engagement pays for time spent. Billed before, it pays for a week that has to earn the next one. A flat week gives me no reason to stretch anything, because there is no extra revenue in a week that drags. Finishing is what pays.

Nobody holds anything back until an invoice clears. The code and the credentials are already yours while the work happens.

Paid for outcomes, not occupancy

The deliverable is shipped, reviewed work. Not hours on a timesheet, not seats filled. Occupancy billing pays someone to be present. Outcome billing pays for the diff that merged and the feature that runs in production.

You can test any arrangement against this term. Ask what shipped last month and where the code lives. An occupancy arrangement answers slowly. An outcome arrangement answers with a link.

Every diff crosses my desk before it reaches yours, and my name is on what ships. Agents write most of the code in my working week now. The review layer is where the value sits, and I wrote about why in When AI Gets Faster, Verification Becomes the Bottleneck.

What a week actually looks like

Because the pricing is weekly, the work runs in weekly sprints. Monday to Thursday are build cycles. You see commits and deploys as they land, every day. Friday is a review: everything that shipped, where the project stands, what comes next. You approve, adjust, or redirect before Monday, and the rhythm repeats. Tasks are organized as Now, Next, Later. One week at a time.

The Friday review is the outcomes part made visible. And everything produced that week already sits in your accounts, so there is nothing to collect later.

The shape is the same across everything I build. What changes is the work inside it. That predictability is part of what you are buying: a rhythm you can plan a company around.

What these beliefs do not replace

None of this means cheap. A senior engineer at a flat weekly rate is a serious line item.

It does not mean unaccountable, and it does not mean no contract. There are real terms in writing, and a named person responsible for every change that goes out.

What the beliefs change is the default position. The code lives with you from day one; the reviews and the paperwork run on top of that.

Where this leaves you

If you are weighing an embedded senior engineer, negotiate hardest on the two terms that decide what happens when things end: who holds the repo and what the invoice pays for.

My answers fit on one page. /tldr is the short version of how this studio runs, pricing included.