I've been trying something for the past few weeks. Pick a specific problem, build a working full-stack app with Cursor, package the source code, sell it on Gumroad. No SaaS, no subscriptions — just source code people can download and run themselves.
This week I finished the second one: FreelanceFlow.
What it does
Tracks clients, projects, time entries, and generates printable invoices from the browser. Dashboard shows earned this month, outstanding invoices, active projects, hours logged. 12-month revenue chart included.
Nothing revolutionary. But it's a complete working app with a real database, a real API, and a UI that doesn't look like a tutorial project.
Live demo: https://freelanceflowweb-production.up.railway.app
The stack
React 19 + Vite + Tailwind v4 + shadcn/ui on the frontend. Express 5 + TypeScript + Drizzle ORM on the backend. PostgreSQL via Supabase free tier. OpenAPI spec with auto-generated React Query hooks via Orval. pnpm workspaces monorepo.
Cursor did most of the actual coding. I directed, reviewed, fixed bugs, made architecture decisions. Maybe 10% of the code is mine by hand.
The monetization angle
Full source code on Gumroad for $39. MIT license — use it commercially, build on it, white-label it, whatever.
There's also a PDF guide included covering how to add Stripe payments, how to turn it into a multi-tenant SaaS, and what that realistically looks like revenue-wise.
Gumroad: https://ibrh96.gumroad.com/l/bcsufq
Honest state of things
My first product, SubSaver (a subscription tracker), is also live and also hasn't sold yet. So I'm 0 for 2 right now. I'm sharing anyway because I think the process is worth documenting even before there's a win to report.
The freelance tracker space has a lot of free options. The person I'm hoping buys this is a developer who wants to skip the 2-3 days of boilerplate setup and get straight to building their own version of it. That's a specific person. I don't know how many of them are looking for this.
Two questions for anyone who's done this before:
This is a strong direction because you are not just building another content helper. The sharper idea is that a founder’s existing work can become an inbound loop without them having to manually turn every update into content.
The part I would pressure-test early is the brand frame.
SubKitt works for v1, but it still feels a bit like a toolkit. If the product starts becoming “the system that turns my work into users,” the name may need to carry more platform weight than SubKitt can.
That matters before launch surfaces harden: emails, GitHub connections, landing page copy, user memory, and founder referrals all start locking the brand in.
For the bigger platform direction, Xevoa .com feels cleaner to me. Short, serious, workflow/platform-like, and broad enough to carry distribution, inbound, and automation without sounding limited to content drafts.
Not saying change it today. Just saying if this becomes more than a v1 experiment, the brand shell is worth deciding before product memory hardens around SubKitt.