Skip to content

Services

Product work with a named owner — not a bench of juniors.

I build and advise. You get one person accountable for the technical path: a mobile app, AI in the repo, an agent that has to survive real data, or a vibe-coded project that is 80% there.
  1. 01Pick the job
  2. 02See week-one tasks
  3. 03Get a USD number

Pick the job

What are you actually trying to ship?

Three honest paths. Tap one. You get the week-one tasks I would run — then a quote if it still fits.

01 · Mobile

Something people can install this month

An idea, a Figma, or a half-finished Flutter repo — and no clear path to TestFlight / Play.

I pin the first slice, the stack, and the store work. You get a clickable build, not another prototype on a laptop.

Week-one tasks

  1. 01Name the user and the one job the v1 must do
  2. 02Freeze screens: auth, home, the money path, settings
  3. 03Pick Flutter or native for a reason, not a trend
  4. 04Ship to TestFlight / internal testing in week one if the repo exists
  5. 05Store listing, crash reporting, and a handover you can keep

Not this

  • An unbounded MVP
  • A redesign of the whole brand
  • Six platforms on day one

01

Web & mobile development

Production web apps and native-quality mobile products — Next.js, React, Flutter, and React Native — with a stack that can actually be maintained.

  • MVPs and v1 products for founders who need to ship, not prototype forever
  • Rebuilds and rescue work when an app is slow, fragile, or stuck
  • App Store / Play Store ready builds with analytics, auth, and payments

02

AI coding

I use AI to move faster — then I review, test, and harden the result so you are not shipping a demo that falls over in week two.

  • Feature delivery with AI-assisted engineering, not unreviewed dumps of generated code
  • Codebase cleanup when Cursor / Copilot output has piled up
  • CI, tests, and review habits so the team can keep using AI safely

03

AI agents

Agents that do real work in your product: research, support, ops, and internal tools — with guardrails, logging, and a human fallback.

  • Agent design: tools, memory, permissions, and failure modes
  • Integrations with your CRM, Slack, email, and internal APIs
  • Evaluation so you know when the agent is actually helping

04

Vibe coding helper

You build in Cursor or similar. I keep the architecture honest, catch the landmines, and help you ship something you can show a customer or investor.

  • Pair sessions on your repo: structure, auth, data, and deploy
  • Production checklist: env, secrets, SEO, forms, and monitoring
  • Handover notes so you (or a future hire) can keep going

FAQ

Services, answered

Can you take over an existing repo?+

Yes. A large share of work is rescue, cleanup, and shipping v1 from a half-finished codebase — including AI-generated projects.

Which stack do you use?+

Next.js, React, TypeScript, Flutter, React Native, Node, and Firebase are the defaults. I pick for the product and the people who will maintain it, not for a trend.

Do you do design?+

I ship a professional, usable interface. If you need a full brand system or illustration, we keep the UI clean and bring a designer in, or you supply Figma.

Keep exploring

The site is a map, not a brochure

Next step

Tell me what you are trying to ship.

A short brief is enough. I will come back with fit, a path, and a USD quote.