./i-need-a-feature
One feature, done right.
Payments. Authentication. The AI feature everyone's asking for. The integration your customers already expect.
The product works. What it wants is one well-defined thing, built properly, by someone who leaves your codebase cleaner than he found it.
What I build most often
Payments and subscriptions. Stripe, RevenueCat, App Store and Play billing. Including the parts that only hurt later: proration, refunds, failed renewals, receipt validation.
Authentication. Email, OAuth, Apple Sign-In, magic links, and sessions that keep people logged in.
AI features. Features where a model does something specific and useful. Photo-to-calorie recognition and natural-language document search are both live in my own products. Cost, latency, and the bad response are solved problems here.
Integrations. Third-party APIs, webhooks, and the retry logic nobody budgets for.
Data migrations. Moving off the schema that made sense at the start, with every record intact.
How it works
Fixed scope, fixed price, fixed date. I look at your codebase first, then give you a number. You get a pull request that matches your conventions, with tests, and a handover document your team can read.
Built to last
Everything ships in a way your team can maintain and extend. If a feature needs a pattern that's new to your team, you'll know the trade-off before we start.
FAQ
- Can you work in our existing codebase?
- Yes. I match your conventions, so the change stays maintainable long after I'm gone.
- What stacks do you work in?
- Primarily TypeScript: Next.js, React, React Native, Node, Postgres, Supabase. Native iOS and Android where it's warranted. If your stack is far outside that, you'll hear it from me straight away.
- How fast can you start?
- Usually one to two weeks. Small scoped features sometimes sooner.
- Do you sign NDAs?
- Yes, routinely.