How I Deliver
Zero micromanagement. Complete transparency. Predictable outcomes.
14-Day Mutual Alignment Guarantee
If within the first two weeks either party feels the communication style, workflow, or technical approach isn't working, the contract is terminated immediately and a 100% refund is issued — no questions asked. Software architecture requires absolute trust. This guarantee makes it risk-free.
Why this matters: I'd rather lose a project than force a partnership that doesn't click. This protects both of us.
Async-First Execution
One structured weekly alignment call (30-60 min). All daily standups, updates, and demonstrations handled asynchronously via text or Loom video. You pay for engineering throughput, not meeting bloat.
Why this matters: Synchronous meetings kill deep work. Async-first means more code shipped, fewer hours billed to meetings.
Clean Handoff & IP Sovereignty
You hold the root infrastructure keys and own 100% of the source code and intellectual property from Day 1. I build on open-source, self-hostable stacks — no proprietary lock-in, no vendor hostage.
Why this matters: Your product is your asset. I build it so you can take it anywhere, anytime.
Fixed-Price Milestones
Once a milestone is funded, the scope is locked to guarantee delivery dates. New ideas or features introduced mid-sprint are automatically captured in a structured V2 Backlog — quoted only after the current version is deployed to production.
Why this matters: No scope creep. No surprise costs. You know exactly what you're paying for and when you'll get it.
30-Day Code Warranty
I patch any bugs or regressions within the delivered scope for free for 30 days post-launch. If something breaks that shouldn't have, I fix it on my dime.
Why this matters: I stand by my architecture. This isn't 'ship and forget' — it's 'ship and support.'
No Jargon Guarantee
Every technical decision gets a plain-English explanation. You will never hear opaque jargon without a clear translation of what it means for your product, timeline, and budget.
Why this matters: You should not need a translator. I speak both business and engineering fluently with founders, technical co-founders, and CTOs alike.
Open-Source, Self-Hostable Stacks
I default to open-source, self-hostable infrastructure — FOSS preferred for cost discipline, performance, portability, and auditability. Bare-metal on Hetzner when the workload justifies it, managed cloud (AWS, GCP, Supabase) when the business calls for it, hybrid in between. Exit costs are documented before they become constraints.
Why this matters: You own the keys, the code, and the choices. No proprietary lock-in, no surprise bills, no vendor hostage.
Post-Launch Support & Maintenance
Ongoing infrastructure oversight after your project ships. Server monitoring, backup verification, disk space tracking, security patch updates, and monthly status reports. Critical issues get an 8-hour response time.
Why this matters: Your software is your asset — it deserves care after launch. Patch cycles, capacity checks, and incident response keep the system healthy.
View details and pricingAI-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 the 14-Day Mutual Alignment Guarantee. If within the first two weeks either of us feels the communication style, workflow, or technical approach is not working, I issue a 100% refund — no questions asked. I would rather lose a project than force a partnership that does not click.
How do you handle scope changes mid-project?
Once a milestone is funded, the scope is locked to guarantee delivery dates. New ideas or features that come up during development are automatically captured in a structured V2 Backlog — quoted separately after the current version is deployed. This protects your timeline and your budget.
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 or Architect to set direction, review code, and get things back on track — without replacing your entire team.
What if the scope is not clear yet?
We start with a fixed-price Technical Discovery Sprint or scoped architecture advisory. You receive defined decisions, risks, and a phased plan before funding implementation. Ongoing technical leadership uses a CTO advisory retainer with explicit outcomes — not embedded labor or screen-tracked hours.
Do you accept hourly engagements?
Yes — hourly is available for staff augmentation, code reviews, or when scope is not fully clear yet. Fixed-price milestones are my preferred default for new projects because they eliminate micromanagement and screen tracking, but hourly remains a real option for the right context. The first conversation is about which fits your situation.
How do you communicate during a project?
We hold one structured weekly alignment call (30-60 minutes). All daily updates, code demonstrations, and questions are handled asynchronously via text or Loom video. You are always in the loop without sitting through daily standups. You pay for engineering throughput, not meeting bloat.
How long does a typical project take?
It depends on the scope. A Codebase Health Audit takes 3 days. A Backend API takes around 14 days. A full SaaS MVP is typically 21 days. The Technical Discovery Sprint (3 days) helps us define the exact timeline before committing to a larger milestone. Every project ships in weeks, not months.
What technologies do you use?
My core stack is Deno/Node.js, TypeScript, Preact/React, PostgreSQL, Valkey/Redis, Docker/Podman, and Traefik. For AI work, I integrate providers such as OpenAI, Claude, and DeepSeek behind explicit application boundaries. Core architecture favors proven, portable tools; provider dependencies and exit costs are documented rather than hidden.
Can you work with my existing codebase?
Yes, I regularly take over existing projects that need architecture improvements, performance fixes, or new features. The Codebase Health Audit is specifically designed for this — I review your code and deliver a prioritized roadmap of what to fix, what to keep, and what to rewrite.
What if I don't have a clear idea yet?
That is what the Free Architecture Audit is for. Send me a paragraph about your idea or problem, and I will send back 3 concrete recommendations within 48 hours. No cost, no pitch. From there, we can decide if a consultation or discovery sprint makes sense.
What if my project needs more work after launch?
Every project comes with a 30-Day Code Warranty — I fix any bugs within the delivered scope for free. For ongoing needs, I offer a Post-Launch Support & Maintenance package that covers server monitoring, backup verification, security patches, and priority support. You can also fund additional milestones from the V2 Backlog at any time.
How do I know you are the right person for my project?
Start with a free architecture audit — send me your tech stack or idea, and I will send back 3 concrete improvements within 48 hours. No cost, no pitch. If you like the quality of the feedback, we can schedule a consultation. If not, you have lost nothing except an email. I have done this for 80+ projects across 15 years, and I am confident I can help you too.