How I deliver
Five promises, no fine print.
Five-day refund
If in the first five days you feel this is not working, tell me and I refund what you paid.
Why this matters: In fifteen years the few engagements that needed a refund all showed it within two or three days, so five days is a promise I can keep.
A small first milestone
We start with one or two weeks of work. If either of us wants to stop at the end of it, we stop — you keep everything built so far.
Why this matters: You don't have to commit to months of work before we know the collaboration is right.
You own everything from day one
Code, accounts, servers and keys are in your name.
Why this matters: Your product is your asset. Nothing about how I work should get in the way of you taking it wherever you need it.
Weekly working software
You see working software every week, with a short written update. Calls when they help, not on a schedule for its own sake.
Why this matters: You always know where the project stands, without sitting through meetings that do not move it forward.
Free bug fixes for 30 days
Bugs in what I delivered are fixed free for 30 days.
Why this matters: I stand behind what I build. If something I shipped breaks, I fix it on my time, not yours.
Pricing: fixed price when the scope is fixed, hourly when the work is open-ended. A change to scope gets a quote before I start on it.
AI-augmented execution
Human-owned architecture + spec-driven development. Two rules I keep, two alternatives I avoid.
What "human-owned" means
Every architectural decision is made by me, not by a model. I draft specs, choose stacks, and own the system diagram. AI assists with boilerplate, refactors, and test scaffolding — the parts where consistency matters more than judgement.
What "spec-driven" means
Every change starts as a written spec — a brief paragraph on intent, edge cases, and acceptance criteria. Code follows the spec, not the other way around. If the spec changes, the diff includes the spec update first, so reviewers can reason about intent before implementation.
Vs vibe-coding
What "AI owns the architecture" looks like
Ask an LLM to "build me a SaaS", paste the output, ship it. No system diagram. No stack rationale. Three weeks in: tech debt the model can't see, dependencies it picked for vibes, auth flows it hallucinated. You own the codebase. Nobody owns the decisions in it.
Vs code-first
What "ship now, spec later" looks like
Move fast, write code, document when there's time. There is no time. Six months later, no one remembers why the auth flow skips email verification for legacy users, or why that one table has no foreign key. The spec lives only in Slack threads and ex-employers' heads.
Stack I work with: Deno, Preact, TypeScript, PostgreSQL, Docker, MCP, self-hosted infra. See my infrastructure setup for proof.
Frequently Asked Questions
Honest answers to the questions I get most often.
What if we start working together and it is not a good fit?
That is exactly why I offer a five-day refund. If in the first five days you feel this is not working, tell me and I refund what you paid. We also start with a small first milestone: we start with one or two weeks of work. If either of us wants to stop at the end of it, we stop — you keep everything built so far.
Do you work fixed price or hourly, and what happens when the scope changes?
Both. I work fixed price when the scope is fixed, and hourly for staff augmentation, code reviews, or when the work is open-ended. If the scope changes once we have started, you get a quote for the change before I start on it — no surprise costs.
Do you work with clients who already have a development team?
Yes, that is one of the most common scenarios. Founders come to me when their existing team is moving too slow, building the wrong thing, or the technical debt is piling up. I step in as a tech lead to set direction, review code, and get things back on track — without replacing your entire team.
What if I don't have a clear idea yet?
Book the free 30-minute intro call, or send me a paragraph about your idea or problem through the form on the home page and I will write back with 3 concrete recommendations. No cost, no pitch.
Send me your ideaWhat if my project needs more work after launch?
Bugs in what I delivered are fixed free for 30 days. For ongoing needs after that there is the Ongoing item in my catalog ($150/hour or from $3,000/month), which covers post-launch support. You can also fund a new milestone at any time; if the scope changes, I quote it before I start.
Ongoing: Fractional CTO, Hourly or on Retainer