What I
Build.
Four service lines, sharply scoped. Engagements run two to twelve weeks with weekly demos, quoted per project, and full handoff documentation at the end.
Web
Development
Marketing sites, SaaS dashboards, and full-stack apps. Built fast, built to last, built to be handed off.
Full details & FAQ →What This Looks Like
You give me an idea, a Figma file, or a competitor I should beat. I give you a working URL in seven days and a launched product within two months. Most of my web engagements are landing pages, founder-led SaaS MVPs, and rebuilds for teams that have outgrown a no-code stack.
You should hire me for this if your product is the website, you need a senior engineer in your corner without the cost of a hire, and you want the codebase to be something a future team can actually pick up.
Deliverables
- Production codebaseTyped end-to-end, deploy-on-push, with sensible defaults baked in.
- Component libraryReusable, documented, accessible by default. No design-system debt from day one.
- CMS & content workflowEditors should never need me. Sanity, Payload, or just MDX — whatever fits.
- Performance budgetLighthouse 95+, Core Web Vitals green, real-user numbers tracked from launch.
- Launch + 30-day supportI monitor, I fix what breaks, I write the runbook your team takes over with.
Stack & Tooling
AI
Automation
Custom agents, intelligent workflows, and the connective tissue between LLMs and your real business systems.
Full details & FAQ →What This Looks Like
Most AI work in the wild is theater — a chatbot pinned to a homepage that nobody uses. The work that actually pays for itself is unglamorous: drafting outreach, classifying support tickets, summarizing meeting transcripts, drafting first-pass legal review. Boring, repetitive, expensive when humans do it. That's what I build.
You should hire me for this if you have a clearly identified bottleneck where the same kind of work happens a thousand times a week, and the people doing it would rather be doing something else.
Deliverables
- Workflow auditI shadow your team for a week, find the three best automation candidates, and pick one.
- Agent pipelineProduction-grade prompts, retries, evals, and observability. Not a Notebook held together with hope.
- Human-in-the-loop UIApproval queues, edit-before-send, override controls. Nobody should ever lose trust in the system.
- Cost ceiling & monitoringHard budget caps, per-request logs, weekly cost reports. No surprise OpenAI bills.
- ROI reportI measure hours saved against hours spent. If the math doesn't work, we stop.
Stack & Tooling
No-Code /
Low-Code
When custom code is the wrong answer. Production-grade builds on visual platforms, delivered in days.
Full details & FAQ →What This Looks Like
Not every product needs a codebase. A founder validating an idea, a studio launching a campaign site, an internal tool nobody outside the company will ever touch — visual platforms ship these in a tenth of the time and cost. I treat them like grown-up engineering: typed schemas, version control, real CI.
You should hire me for this if you've been told “we can't afford a developer” and your idea is bleeding time, or you have a working app that needs an internal admin tool yesterday.
Deliverables
- Platform selectionAn honest call on which tool fits your problem. Sometimes the answer is "actually, code this."
- Production buildPixel-perfect, mobile-tuned, animation-polished. Looks bespoke, not template.
- Backend & logicDatabase schemas, conditional flows, integrations — the parts the marketing site never shows.
- Loom-recorded handoffSo your team can edit without ever messaging me. Onboarding video included.
- Migration pathAn explicit plan for if and when you outgrow the platform. No lock-in surprises.
Stack & Tooling
API
Integrations
The unglamorous plumbing that makes everything else work. Cleaned up, documented, hardened.
Full details & FAQ →What This Looks Like
Every growing company eventually accumulates a tangle of half-finished integrations: a Stripe webhook that mostly works, a Hubspot sync that drops one in twenty leads, a Slack bot nobody dares touch. The longer it's left, the more brittle it gets, and the more it costs to fix. I come in, untangle it, and leave behind a system your engineers can extend without flinching.
You should hire me for this if integration work keeps sliding to the bottom of your roadmap, or you're shipping a new product that needs to talk to five vendors on day one.
Deliverables
- Integration auditEvery connector mapped, every failure mode catalogued, every silent dependency surfaced.
- Typed API clientsOne source of truth per integration. Generated types, retry logic, idempotency keys.
- Webhook infrastructureSigned, replayable, dead-letter-queued. The stuff your future self will thank you for.
- DocumentationPlain-English walkthroughs for every flow, plus an architecture diagram that's actually current.
- Monitoring & alertingPage someone on real failures. Stay quiet on noise. That's the whole job.
Stack & Tooling
How We
Work Together
Quick
Wins
A focused engagement for a clearly-scoped deliverable. Best for landing pages, single integrations, or a single AI pilot.
- Single deliverable, fixed scope
- Daily async updates
- One round of revisions
- 14-day post-launch support
Full
Build
End-to-end build with weekly demos. Where the bulk of my engagements land — SaaS MVPs, complete rebuilds, AI deployments.
- Discovery, build, launch, handoff
- Weekly demos & staging access
- Unlimited revisions within scope
- 30-day post-launch support
- Full documentation & runbook
Ongoing
Partner
A senior engineer on call for product teams that need consistent capacity without a full-time hire.
- 40 hours / month, capped
- Slack + weekly call
- Priority response time
- Rolling backlog management
- Quarterly commitment, monthly billing
Frequently
Asked
How fast can you start?
+Usually within 1–3 weeks of signing. For Sprint engagements I can often start sooner. My current waitlist is on the homepage and on the About page; if you need it faster than that, mention it in your first message and I'll see what I can shuffle.
Do you work with non-technical founders?
+Most of my clients are non-technical founders. I treat that as a feature, not a bug — it forces me to explain decisions clearly, and it usually means we're aligned on what matters (the product) instead of what doesn't (which framework). I will, however, never let "I don't know" become a way to skip a hard conversation about scope or constraints.
What if my project goes over scope?
+Every engagement has a defined scope document signed before work begins. If scope grows mid-project, we have an explicit conversation: cut something, quote the addition separately, or fork a follow-up engagement. There are no silent overages and no surprise invoices. I would rather lose a sale than poison a relationship over scope creep.
Can you join my team's stand-ups?
+Yes, on retainer engagements. For project work I prefer one weekly call plus async — daily meetings are expensive and rarely move work forward. If your team works in a way that genuinely needs daily sync, we can talk; it'll just be priced as a retainer.
Do you sign NDAs?
+Standard mutual NDAs, yes — usually before our first call if you need it. Custom enterprise legal terms (security questionnaires, vendor risk assessments, MSAs) are fine on retainer engagements and add roughly 2 weeks to kickoff.
What's not a fit?
+Mobile native (iOS/Android), heavy machine-learning research, blockchain-anything, and projects where I'd be the sole engineer on a team larger than five. I'll happily refer you to a specialist for those.