Product strategy
Clarify what to build, in what order, and why. Lightweight discovery, decisions documented in writing.
- Problem framing & user research reads
- Opportunity sizing and roadmap drafts
- Lightweight RFCs and decision memos
Independent · Dallas, TX
Thoughtful product and engineering work, for teams who care.
I'm an independent consultant pairing with small product teams on web applications that need to feel considered, not generic.
- Based in
- Dallas
- Available
- Q1
- Response
- < 1 day
- Clients
- 1–2 at a time
What I do
Three kinds of engagements.
Most projects are a blend of these three. Sometimes you need a thought partner for a quarter; sometimes you need another pair of hands for a sprint. We'll figure out the right shape together.
Hands-on engineering
Modern web applications with TypeScript, React, and the Next.js app router. Static or dynamic, deployed on Cloudflare or Vercel.
- Next.js, React, TypeScript, Tailwind
- APIs and edge workers on Cloudflare
- Databases: Postgres, SQLite, Durable Objects
Design partnership
Pair with your team to turn Figma into production-ready components without losing taste along the way.
- Design-system component implementation
- Interaction and motion detailing
- Accessibility and performance passes
Selected work
A few recent engagements.
A sample of the kind of work I take on. Details change by project; the shape is consistent — small, senior, honest.
Next.js · Tailwind · Cloudflare
Event venue platform
A statically rendered marketing site and inquiry pipeline for a Southern California wedding venue, built on Next.js and Cloudflare Pages Functions.
TypeScript · Postgres · Edge functions
Internal tools, done right
Replaced a sprawling spreadsheet workflow with a focused internal web app — auth, forms, reporting, and audit — in a single quarter.
React · Figma · Motion
Design-engineering partnership
Embedded with a design team to translate a complete Figma library into production React components with motion and theming.
How I work
Small team of one, with the discipline of ten.
Written-first thinking
Every project starts with a short memo — the problem, the approach, the trade-offs. If we can't agree on paper, we're not going to agree in code.
Boring, reliable tools
TypeScript, Postgres, Next.js, Cloudflare. Tools your team can maintain after I'm gone — not frameworks that force a rewrite in 18 months.
Design-aware engineering
Pixels, motion, and interaction states get the same care as the data model. If it isn't elegant to use, it isn't done.
Narrow focus, fast feedback
One or two engagements at a time. Weekly demos, async updates in between — you always know what's happening and why.
Accessible by default
Semantic HTML, keyboard support, reduced-motion respect, color contrast that holds up in dark rooms and bright sun.
Clean handoff
Documented decisions, a running changelog, deploys that your team can own. No tribal knowledge, no hidden dependencies.
Common questions
A few things worth saying up front.
Still have a question? Email is the fastest way to get an honest answer.
I take on one or two engagements at a time. Short, well-defined projects work best — four to twelve weeks is the sweet spot. I'll always start with a short discovery call to make sure we're a good fit before anything else happens.
Mostly TypeScript, React, and Next.js on the frontend, with Node and Cloudflare Workers on the backend. For data I lean on Postgres and SQLite. I pick tools that are boring, reliable, and easy for your team to maintain after I'm gone.
I can, if there's a clear scope. For ongoing work I prefer a monthly retainer with a defined set of outcomes — not a seat-at-the-table arrangement. That keeps us both honest about what's getting done.
Anything where the brief is 'build whatever you think is best' with no clear owner or decision maker on your side. Great work needs a partner, not just a budget.
Email is best — write a few sentences about what you're working on and what you'd like to change. I read every message and reply within a business day.
Have something in mind? Let's talk.
A short note is enough — tell me what you're working on and what you'd like to change.
I reply to every message, usually within one business day.