Stripe Projects lets solo makers collect real payments without forming a company, cutting setup time from weeks to minutes.
I used to need a GmbH, a business bank account, and 2000 EUR in fees before charging for a side project.
Projects works with a personal account and keeps earnings separate, so three side bets can each run their own books.
This changes pricing math for micro SaaS, one-off digital products, and any project under roughly 50000 EUR a year.
The bottom line: the excuse of "I need to incorporate first" is dead, which means more makers will ship paid products this year.
Stripe Projects changes the math for anyone running a side project solo. Until this week, collecting money for a side project meant forming a company, opening a business bank account, and burning about 2000 EUR in setup fees before the first sale. Projects skips that whole runway and lets a personal Stripe account hold several tiny businesses under one roof.
What Stripe Projects Actually Is
Projects is a new layer inside a standard Stripe account that lets you run several independent ventures without spinning up separate legal entities. Each Project gets its own payment methods, its own products, its own reporting, and its own payout schedule. Think of it as clean folders for each stream of earnings, with real accounting walls between them.
The important part is who it works for. The old flow assumed you had a registered company, a VAT ID, and a bank account that matched the business name on the Stripe onboarding form. That worked fine for a real SaaS team with a lawyer on retainer. It was brutal for anyone shipping a 19 EUR product on a Thursday night.
With Projects, a personal Stripe account can host a Chrome extension, a Notion template shop, and a weekend API, all at once, without legal paperwork for each one. Taxes still apply, because taxes always apply. But the threshold for "let me just try charging for this" drops from a few weeks of admin to a few hours of setup.
I tested it with a small digital product pack I had been sitting on for three months. From signup to first test charge took 41 minutes, most of it spent writing the product description. That is the part that matters. Friction is what kills side projects, not ideas.
One caveat worth naming up front. Projects is not a replacement for incorporating once the numbers get serious. Once a project clears a certain size (roughly 50000 EUR a year, depending on your country), the accountant bill, liability exposure, and tax structure start pushing you toward a proper company anyway. Projects is for the zero-to-first-paying-customer stretch, which is exactly where most makers get stuck.
Why This Rewires Solo Maker Economics
The old stack for a tiny paid product looked like this. Register a sole proprietorship or equivalent. Open a business bank account (100 EUR setup, monthly fees). Get a VAT number if your country requires one. Hook up a payment processor. Write a privacy policy and imprint. Wait two weeks for verification somewhere. Then, finally, ship.
If the product flopped, that 300 to 500 EUR and forty hours of setup were gone. So most makers never shipped. They built the thing, got scared at the admin wall, and moved on. I've done it myself more times than I want to admit.
Projects flips the equation. Setup cost for a new paid idea drops to effectively zero, because you are reusing your existing account. The break-even point on trying something new moves from "this has to make 500 EUR before it was worth bothering" to "this just has to make 20 EUR to be net positive."
That sounds like a small shift. It isn't. Most indie products die at zero, not at 500 EUR. The distance between "I have an idea" and "someone paid me for it" is where most side projects quietly get buried. Shrinking that distance means more things actually hit the internet and get a chance to find an audience. That chance is the whole game.
There's a secondary effect. Because each Project is its own ledger, I can run three experiments in parallel without my books turning into a spreadsheet nightmare. Last year I had two little products sharing the same payment flow and it took me six hours every quarter to untangle them for tax reporting. This year, with Projects, that goes to about 15 minutes.
The net effect on the maker economy is simple. More shots on goal, cleaner books, and fewer excuses to wait. I've been watching this shift happen slowly for years through things like Gumroad, Lemon Squeezy, and Paddle, each of which chipped away at one piece of the admin wall. Projects is the first time the payment processor itself has said, out loud, that solo operators are a real customer.
Who Wins and Who Barely Notices
The biggest winners are the smallest operators. A developer charging 9 EUR for a Figma plugin. A writer selling a 29 EUR prompt pack. A designer running a 49 EUR starter kit. Anyone whose first year looks like 500 to 15000 EUR from a single product. This group used to face the same legal overhead as a VC-backed startup, which made no sense.
Second tier of winners: portfolio makers. People who ship five small things a year instead of one big thing. Under the old model, each new project meant fresh paperwork or awkwardly mixing everything into one company's books. With Projects, a portfolio maker can treat each launch as its own mini P&L without the overhead.
Who barely notices? Anyone already running a real company with employees, contractors, or enterprise customers. If you have a GmbH, an Inc, or a Ltd, Projects is a nice organizational feature but it doesn't change your economics. You already paid the incorporation tax and set up the bank account. For you, this is just better folders.
Also barely affected: anyone selling physical products at scale. If you're running a Shopify store with inventory, suppliers, and shipping logistics, the bottleneck was never Stripe onboarding, it was the rest of the supply chain. If you want the cleanest path for physical goods, Shopify still handles the end-to-end flow better than a raw Stripe setup, and the economics of inventory dwarf the payment processor question.
The group I'm most interested in is the one in the middle. People with one product making 500 EUR a month, who have been too overwhelmed to launch a second. That second product is now a one-evening decision instead of a three-weekend decision. That's a real behavior change.
What I'm Changing in My Own Stack
I had two paid products in the pipeline that I'd been putting off because the thought of another round of admin made me tired. Both are shipping this month now, under Projects. One is a 19 EUR Claude Code template bundle. The other is a small internal tool I'd been running for myself.
My new workflow looks like this. When I have a product idea that might earn money, I spin up a Project in under an hour, attach a minimum viable landing page, and push a test charge through before bed. If it gets any traction in the first two weeks, I keep going. If not, I archive the Project and lose nothing but an afternoon. That ratio, afternoon-to-decision, is the thing I've been wanting for years.
I'm also rethinking pricing tiers on things I'd previously skipped because the take-home didn't justify setup effort. A 7 EUR thing that sells 50 times used to not be worth the admin. Now it is, because the admin is gone. Same logic applies to experimental pricing on existing products. If you can spin up a Project-level A/B without polluting your main books, you can test a 29 EUR tier against a 49 EUR tier with clean reporting.
If you're building for yourself, I'd recommend one rule. Don't mix Projects across wildly different audiences. Keep one Project per clear audience or theme. If you sell to developers in one Project and consumers in another, your accounting stays clean and your tax position is easier to explain later. You can see how I structure my own experiments over on the lab if you want a reference.
The tooling around Projects will get better fast. Expect third-party dashboards, accounting integrations, and tax-filing helpers to show up within a quarter or two. I'll probably write about whichever of those I end up using, once I've run real money through them for a few weeks.
Bottom Line
The excuse of "I have to set up a company first" is officially dead for anyone shipping small paid products. That was the single biggest piece of friction between an idea and its first paying customer, and Stripe just took a saw to it.
This doesn't mean every side project is now a business. Most will still flop. But the cost of finding out drops from hundreds of euros and weeks of admin to an evening. That shifts the math for any solo maker who has been sitting on ideas.
My practical take: if you've had a paid product in the back of your head for more than six months, ship it under a Project this week. Skip the perfect landing page. Skip the logo. Get one real customer paying 9 EUR, and then decide if the idea has legs. That first transaction teaches you more than three months of planning ever will, and Projects just made it roughly as hard as setting up a Netflix account.
Top comments (0)