Work With Me
I make complicated product work feel simple. Companies hire me to cut through complexity and ship one clean, focused product — product, backend, frontend, data, and infrastructure, owned by one engineer.
One engineer across the whole stack: fewer handoffs, fewer meetings, one person who takes a problem from framing to production.
What I Do
- Build the v1 — Turn an idea into a working product in production. Architecture, data model, backend, frontend, infra, deploy. Real users, real load, real numbers.
- Cut through complexity — Sprawling system, tangled product, stalled migration, data nobody can untangle. I find the real problem, narrow the scope, and ship something clean in its place.
- Be your fractional founding engineer — own the technical arc with a founding team through the next milestone. A few days a week, async, no standups. Set the bar, ship the hard parts, hand off cleanly.
- Data and geospatial systems — Postgres, PostGIS, H3, DuckDB, large spatial workloads. SQL-first, years of production scars.
Engagement Shapes
- Project build — Fixed scope, fixed end date, working software at the end. Priced as a fixed fee against the agreed scope.
- Sprint — One to three weeks. A working proof, not a deck. Weekly rate, paid weekly.
- Embedded — A few days a week, ongoing, treated as part of the team. Monthly retainer with a defined scope per month.
- Advisory + hands-on — System design and architecture, with me in the codebase when it matters. Weekly or monthly retainer, depending on cadence.
Rates start at $150/hour, with a 10-hour minimum to start — enough to onboard and ship something real. Sprints and project builds are quoted as a fixed fee against scope, so you get a number before any call, not after.
Who I'm a Fit For
- Operators with a product or system that has grown messier than the business needs it to be.
- Founders pre- or post-PMF who need a real builder on the v1 — not a team to manage.
- Companies between hires who want one person who ships, not another seat to fill.
- Teams with a hard, narrowly scoped problem — messy real-world data, scale, geospatial, performance.
Who I'm Not a Fit For
- Pure architecture roles where I don't write code.
- IC seats with no ownership.
- Layers of approval before anything ships.
- Maintenance with no room to simplify.
What You Get
- Someone who treats the work like an owner, not a contractor.
- Working software, fast. A POC same-day where it makes sense; production quality on the timeline we agree.
- Collaboration that matches your team. Async-first to keep your meeting load and costs down — written updates, demos, SQL, and data samples carry the work — with calls, pairing, or daily check-ins whenever they move things faster. (One engagement has run entirely in writing for two years and kept shipping; I flex to your cadence, not the reverse.)
- A clean handoff. Code, docs, and decisions in a state your team can actually run with.
- References from current and recent engagements available on request.
Start a Project
If you have a product to build, a system to simplify, or a data layer that needs to actually work — send a short note covering:
- The problem and what "done" looks like
- Rough timeline and any hard deadlines
- What's already in place (stack, data, team, repos)
A few sentences is enough. I'll write back with whether it's a fit, what an engagement would look like, and the next step.