Marc Lou: The Week ShipFast Changed Everything
How a Next.js boilerplate launched after years of failed projects and became the foundation of a multi-product indie business.
- MRR
- Was high five-figures; now lower but still active
- ARR
- $1.3M+ lifetime
- Users
- Thousands of makers
- Founded
- 2023
- Team
- Solo
- Stack
- Next.js, Stripe, Auth, Email
What was different about ShipFast compared with the earlier projects?
I had launched many products that made almost nothing. Some were interesting technically. Some solved problems I only thought people had. ShipFast was different because it solved a problem I had myself, repeatedly.
Every time I started a new SaaS idea I rebuilt the same foundation: authentication, Stripe subscriptions, transactional email, a basic dashboard, SEO basics, a landing page structure. After doing that for roughly two years across many experiments, I finally packaged the internal stack into something other developers could buy. The product was the shortcut I had already paid for in time.
I built the first version in about a week. I did not run a long waitlist or a formal interview process. I launched it to the audience I had been talking to publicly for years and treated the live launch as the test.
What happened in the first days and weeks?
The first 48 hours produced more revenue than I had made in the entire previous year. The first month reached around $40k. Over the following months the product continued to sell strongly. Lifetime revenue eventually crossed well over a million dollars. For a period it was the clear center of the portfolio.
The buyers were other makers who wanted to skip the boring setup and start building the actual product. The positioning was simple: ship your startup in days, not months. The price was high enough to signal seriousness and low enough that an individual developer could decide quickly.
Why did this one work when so many others did not?
Three things lined up. First, the problem was real and repeated — I had felt it myself dozens of times. Second, the distribution was already there. Years of posting failures, experiments, and small wins meant that when something useful appeared, people were ready to look. Third, the product delivered immediate value. Buyers could clone the repo and start working the same day.
I had also learned to charge from the beginning and to treat the launch itself as marketing. There was no multi-month stealth phase. The public nature of the launch created urgency and social proof at the same time.
What happened after the initial peak?
Revenue stayed meaningful for a long time, then the market changed. More boilerplates appeared. AI tooling reduced some of the setup pain. Competition increased. ShipFast did not disappear — it continued to generate sales on a lower but still positive trajectory — but it stopped being the majority of income.
That was expected in a portfolio approach. The cash and the audience from ShipFast funded and accelerated the next products: CodeFast, DataFast, TrustMRR, and others. The win was not only the revenue of one product; it was the platform it created for everything that followed.
What should other founders take from the ShipFast story?
Package the work you keep repeating. If you have solved the same infrastructure problem five times, other people are probably solving it too and would pay to skip it.
Build the audience before you need it. The followers who watched the failed projects were the same people who bought the successful one.
Do not marry a single product. Use a big win to fund the next experiments. Markets shift. Tools improve. The founders who keep shipping after the first success are the ones who stay relevant.