./i-need-a-feature
You have a product. It needs one more thing.
Payments. Authentication. An AI feature everyone's asking for. An integration with the tool your customers already use. A migration you've been putting off.
The product works. You don't need a partner or a rebuild. You need one well-defined thing built properly by someone who won't leave a mess in your codebase.
This is you if
- Your team is at capacity and this keeps getting pushed
- It's outside your stack and hiring for it doesn't make sense
- You've tried twice internally and it's still not right
- You need it done in weeks, not quarters
- It touches payments or auth and you'd rather it were done by someone who's done it before
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, session handling that doesn't log people out at random.
AI features. Not a chatbot bolted onto a sidebar — features where a model does something specific and useful. I've shipped photo-to-calorie recognition (Kolibi) and natural-language document search (Orivela). I know where these break: cost, latency, and what happens on the bad response.
Integrations. Third-party APIs, webhooks, the retry logic and idempotency nobody budgets for.
Data migrations. Moving off the schema that made sense at the start, without losing anything.
How it works
Fixed scope, fixed price, fixed date. I look at your codebase first and give you a number — if I can't scope it confidently, I say so rather than padding the quote. You get a pull request that matches your existing conventions, with tests, and a handover document your team can read.
What I won't do
Ship something that only I can maintain. If a feature needs a pattern nobody on your team knows, either it gets built in a way they can extend, or I explain the trade-off before we start.
FAQ
- Can you work in our existing codebase?
- Yes. I match your conventions rather than importing mine — the goal is a change your team can maintain 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, I'll tell you rather than learn it on your budget.
- How fast can you start?
- Usually one to two weeks. Small scoped features sometimes sooner.
- Do you sign NDAs?
- Yes, routinely.