Seven things I’m good at. Usually combined.
Most projects mix two or three of these. The brand client also needs the site; the SaaS needs the mobile app; the dashboard needs the marketing page. One thread, end to end, no hand-offs.
A custom dashboard, customer portal, or internal tool — designed and built end-to-end. I write the code, design the UI, and stand it up in production. No agency hand-offs.
- ※Discovery & scoping (1–2 days, no charge)
- ※Custom UI design from scratch
- ※Full-stack build on a boring, durable stack
- ※Deployed, monitored, and documented
You have an idea. I help you decide what's actually in the first version, then build the thing your earliest users will pay for. Auth, billing, data model, the boring scaffolding — all real.
- ※One day on what to cut, before any code
- ※Auth, billing (Stripe), multi-tenant from day one
- ※Live in production with paying-customer plumbing
- ※Hand-off doc so the next dev can pick it up clean
Cross-platform mobile, custom-designed and built to feel native. Usually as a companion to a web product, sometimes mobile-first — either way, designed in lockstep with the rest of the brand.
- ※Native-feeling UI custom-designed per platform
- ※Push, deep-linking, offline state, App Store handling
- ※Shared backend with the web product
- ※TestFlight + Play Internal builds from week one
Real automation that solves a specific small-business pain: invoices that file themselves, leads that route on their own, customer touchpoints that happen without a human remembering to send them.
- ※Map the manual work that's actually costing time
- ※Automate the workflow end-to-end (intake → system → follow-up)
- ※AI in the seams — OCR receipts, summarize calls, route by intent
- ※Plug into the tools you already pay for (QBO, GBP, Stripe, etc.)
- ※Dashboards so you can see what ran and what failed
Editorial, dense, and fast. I custom-design every page — no template kits — build it on a static-by-default stack, and wire it up so marketing can edit without calling me.
- ※Custom design, no theme reuse
- ※Sub-1s LCP at p75 mobile, 100s across Lighthouse
- ※CMS-backed so non-devs can edit safely
- ※Per-post OG images, RSS, sitemap, analytics
Wordmark, color, type, voice doc. I work alongside small businesses to name the thing, draw the mark, and build the voice that the marketing site and the truck wrap both sound like.
- ※Naming workshop (sometimes literally on a napkin)
- ※Wordmark & monogram drawn from scratch
- ※Color, type, and voice system
- ※Truck-wrap-to-favicon spec
Google Business setup, schema, citations, and a review pipeline that turns completed jobs into public reviews automatically. For service-area businesses that want the phone to ring.
- ※Google Business profile setup across metros
- ※Schema.org markup + city-page content engine
- ※Citation cleanup across 40+ directories
- ※Automated review pipeline (Twilio + GBP)
Five steps. No surprises.
- 01A short call
Thirty minutes. You tell me the problem in plain words. I tell you whether I'm a fit. No deck, no upsell.
- 02A small written proposal
One page, two days later. Scope, timeline, fixed price. If we agree, we sign and start. If not, no hard feelings.
- 03Two days of deciding
Before any code, we map the smallest thing worth shipping. The deciding is the work. The code is the easy part.
- 04Build, in two-week sprints
Each sprint ends with something deployed. You see progress every week. Surprises early, not late.
- 05Ship and hand off
Live in production, monitored, documented. The next developer (or you) can pick it up without calling me.
Do you do retainers?+
Rarely. I prefer fixed-scope projects with clean ends. If you need ongoing maintenance, I can usually point you at someone good.
What if scope changes mid-project?+
It will. We re-scope in writing, decide together what gets cut, and keep the deadline. No hourly creep.
Can I see code as you build?+
Yes. Every project lives in your GitHub from day one. You get a deploy preview per PR.
Do you sign NDAs?+
Happily. I default to discretion either way — most of the work I do never gets posted.
What about AI?+
I use it where it makes me faster (autocomplete, prose drafts, sometimes design exploration). I don't ship AI features unless you actually need them.