You get a product in production. Not a deck.
From scoping to production, as one continuous piece of work. The people you talk to are the people writing the code.
The list is broad. The constraint isn't the stack.
Web and mobile apps. Marketplaces. Internal tools and dashboards. SaaS with the awkward parts included: billing, roles, permissions, multi-tenancy, the audit trail somebody asks for in year two. AI features, on-device or hosted. Games in Godot and Unity.
What stays the same across all of it is who does the work. The same people scope it, build it, and are still there for the part where real users arrive.
- Next.js
- React Native
- Expo
- Postgres
- Stripe
- Godot
- Unity
- TypeScript
- GitHub
Most of the work is the parts nobody sees.
- Identity: phone verification by SMS, email confirmation, password reset that can't be turned into an account takeover, sessions that end when they should.
- Abuse: rate limits, reporting and moderation queues, the limits that stop one bad actor ruining the fun for everybody else.
- Money and integrations: payments, subscriptions, webhooks that retry properly, and third-party APIs that tell you when they go down.
- Running it: hosting, environments, deploys, migrations, backups, background jobs, and enough tracking so a bug reported on a Sunday evening is actually fixed on Monday.
SEO: search visibility is decided in the data model.
An indexable detail page per listing is not a setting switched on afterwards: it is a structural decision. That is a fact about how the thing was built, not a promise about acquisition. But it is why the growth work starts with something to stand on rather than nothing.
Shipping is where the work starts, not where it stops.
- Positioning and offer: who it is for, what it is called, and what it costs.
- Acquisition: a brand kit and identity that suits the product, then two or three channels done properly rather than a thin presence on all of them.
- Instrumentation: events that mean something, a funnel readable end to end, and an attribution trail that still makes sense a month later.
- Iteration: copy, pricing and landing pages keep moving after launch, tested and measured rather than frozen on the day the site went live.