Est. MMXXVIClearwater, FL
Solo StudioAvailable — 1 Slot

IshipMVPsforfounders
raisingmoney.

— What I do

Solo designer-engineer. I turn a pitch deck into a working product investors can open, tap, and feel. Shipped in weeks, not quarters.

Scroll
01 — What I do

Most MVPs die in the deck. I make the one that ships.

You have a pitch deck and no engineer. Dev shops quote you six figures and six months. You need something investors can open on their phone next Tuesday.

I’m a solo designer-engineer. I do the product thinking, the interface, and the code — in the same head, no handoffs, no agency middle layer. One person who owns the whole thing from whiteboard to App Store.

I shipped an app called Learnin solo in six months — design, auth, database, payments, iOS, the whole stack. That’s the exact muscle I bring to your MVP.

02 — Case study— Ongoing

Learnin

The AI tutor that builds career courses for you.

— Overview

A mobile app that generates a structured career course for working professionals — role, goal, and prior knowledge in, lessons and quizzes out.

Designed, built, and shipped solo. Live on uselearnin.com, iOS in review at Apple, 49 friends-and-family users onboarded.

Stack

Expo / React Native / TypeScript on the client. Supabase for auth, Postgres, edge functions, and realtime. RevenueCat for subscriptions. OpenAI for course generation. Shipped to the App Store.

What was built

Onboarding flow, persona-aware lesson generator, quiz engine, streak & XP system without dark patterns, paywall, course-sharing links, admin dashboard, feedback pipeline, Telegram bot for user signals.

The point

Every layer of this app — the copy, the auth flow, the DB schema, the pricing, the iOS build — is one person’s work. If I can build Learnin solo, I can build your MVP solo.

6 mo.Solo build
1Founder
49F&F users
iOSIn review
$0Team cost
Endlessly complex
03 — Case study— MVP shipped

Bounty

Crowdfund the dare. Escrow enforces delivery.

— Overview

A platform where creators post challenges to their audiences, backers crowdfund them, and funds only release when the community confirms delivery.

Designed and shipped solo, end to end. Full Stripe escrow infrastructure, Postgres schema with row-level security, and a community vote resolution system — all built for one non-technical founder who needed proof of concept before raising.

Stack

Next.js App Router + TypeScript on the web. Supabase for Postgres, auth, storage, and row-level security. Stripe Connect for escrow, payouts, and refunds. Resend for transactional email. Deployed on Vercel.

What was built

Challenge creation flow, crowdfunding progress tracker, Stripe PaymentIntent escrow, webhook reconciliation, community delivery voting with 66% / 50% thresholds, refund path on dispute, creator profile & onboarding, explore feed with category filters, mobile-first funding sheet.

Hardest part

Designing the escrow state machine so funds are captured safely, voting resolves without gaming, and disputes open a manual review path — all in a schema that passes RLS inspection and reconciles with Stripe’s async webhooks.

The point

The hardest MVPs involve money. Bounty shows I can ship real payment flows — not just a pretty marketing site. If your MVP needs Stripe, auth, or a vote/approval engine, this is the evidence.

8Weeks to MVP
1Founder
5%Platform fee
66%Vote threshold
StripeEscrow
RLSSecured
03 — Packages

Flat fee. Scoped. Shipped.

Three ways to work together. No hourly billing, no scope-creep games, no “while you’re in there” freebies. Fifty percent up front, fifty on delivery.

01

Pitch Prototype

$3,500
2 weeks

Clickable front-end. One core user flow. Hosted on a real URL. No real backend — but it looks and feels like the product. Perfect for investor demos.

02

Launchable MVP

$9,500
4–6 weeks

The real thing. Auth, database, one-to-two core flows, deployed to production. Real users can sign up and actually use it. The version you put in a pitch deck without apology.

03

Retainer

$2,500/mo
Month to month

For after the MVP ships. Ongoing feature work, iteration from user feedback, demo-day preparation, investor-update support. Cancel anytime.

* Scope locked in writing before we start. Change orders are fine — silently creeping scope is not.

04 — Process

How it actually goes.

Week 0

A conversation.

30 minutes on a call. I ask what you’re building, who it’s for, and what investors need to see. You ask me anything. If we’re a fit, I send a scope and a fixed price the next day. No forms, no questionnaires, no account manager.

Week 1

Kickoff and shape.

Fifty percent wired. I share a Figma link within 48 hours — usually a rough version of the hero flow. We iterate fast over text. No hour-long review meetings.

Weeks 2–5

Build in public.

You get a staging link from day one and can open it anytime. I push updates as I go, not at milestones. Weekly summaries on Fridays. You see the thing becoming the thing.

Ship day

It goes live.

Deploy, hand over the keys, 30-day bug support, and a clean loom walkthrough of the codebase. Final fifty on delivery. If you want to keep going, we move to retainer.

05 — Start

Got a deck.
Need the product.
Let’s talk.

30-minute intro call. I’ll ask what you’re building and who it’s for. If we’re a fit, you get a scope and a fixed price the next day.