How it works

Four stages. Price before code.

You see a fixed price in writing before I build anything. Small, clear jobs under $7,500 can skip the Build Plan.

Stage 1 · Free · 20 minutes
Fit call
We talk through what happens today and what it costs you.
You get: A written recap within one business day, with a recommended path.
Stage 2 · From $1,500 · 1–2 weeks
Build Plan
I map the process, review your systems and write the scope.
You get: Acceptance checks, risks and a fixed quote. Yours to keep; credited toward the build if you sign within 60 days.
Stage 3 · Fixed price
Build
I build against the written scope. Changes are priced and approved first.
You get: A written update every week and a working demo at each milestone.
Stage 4 · Included
Handoff
Docs, code and accounts, all in your name.
You get: 30 days of fixes for anything that misses the agreed scope.

Payments

Up to $3,000: Half to book, half at delivery.
Larger projects: 40% to book, 40% at a working midpoint demo, 20% at acceptance.
Invoices: Due in 14 days. Vendor subscriptions are billed to you directly.

Who owns the code?

You do. I work in repositories and cloud accounts that belong to you, and you keep full access after handoff.

What if the scope changes?

I write down the change, its price and its effect on the schedule. Nothing extra starts until you approve it.

How do you use AI?

AI coding tools help me work faster. I build AI features only where they test well on your real examples, and your data never trains anything.

How long does it take?

A Build Plan takes one to two weeks. Most automations take two to four. Product builds are scheduled in the quote.

Why no case studies?

I’m new as an independent. The first project is this business, and that write-up publishes after launch. I won’t invent the rest.

What happens after launch?

Thirty days of fixes are included. Then a Care plan, hourly help, or nothing. You’re never required to keep me.

The method behind every stage is public at opchain.dev.