The $299 Code Template Marc Lou Built in a Week, and What It Earns Three Years On

Marc Lou had built sixteen products in about two years and was tired of writing the same code every time: the payment wiring, the login, the emails, the landing page. So he packaged the boring parts into a starter kit called ShipFast, spent roughly a week on it, and put it up for $299 as a one-time purchase. Starter Story's breakdown of the launch records $1,000 in the first seven hours, $6,000 in the first 48, and $528,000 in the first four months, from a product with no employees, no funding and no ongoing delivery cost.

The reason this story is worth reading in 2026 is not the launch. It is what the same product earns now, because Lou publishes it.

The product was already written

ShipFast is a Next.js boilerplate: a repository of pre-connected code so a developer can go from empty folder to a site that takes payments in a day rather than a fortnight. The current product page lists what is in the box: Stripe or Lemon Squeezy payments, Mailgun or Resend for email, MongoDB or Supabase, Google login and magic links, SEO and blog scaffolding, UI components, and lifetime updates.

None of that was research. It was the accumulated residue of sixteen previous attempts, most of which did not work. Lou's own site carries the summary of that period: "I was fired everywhere, so I hired myself."

The mechanism is available to more people than it first appears. If you have done the same job repeatedly, the artefacts you built to survive it, the spreadsheet, the checklist, the contract template, the onboarding sequence, are a product for the people about to do it for the first time. The work is already done. What remains is packaging and a price.

The launch, channel by channel

Starter Story dates the launch to 23 August 2023 and lists the channels: Product Hunt, where it reached second Product of the Day with 941 upvotes and brought around 3,000 visitors in 48 hours; Twitter, where Lou had more than 40,000 followers at the time; Hacker News; and Reddit.

Order matters here. The 40,000 followers existed before the product. Lou spent two years building things in public and failing in public, which is exactly the pattern Builtplain described in the twelve-startups-in-twelve-months constraint: the visible failures are not wasted, they compound into an audience. By the time he had something worth selling to developers, he was already a developer other developers watched. That is the argument for publishing being the moat, stated in dollars.

What the hit earns now

Lou runs a public dashboard of his products on his Indie Page. On 27 July 2026 it showed total monthly revenue of roughly $116,000, with the individual lines like this:

• TrustMRR: $40.4k a month
• Ship or Die: $34.1k a month
• DataFast: $26.2k a month
• CodeFast: $9k a month
• ShipFast: $4.8k a month
• Indie Page: $830, LaunchViral: $258, SuperShrimp: $221, Zenvoice: $138, ByeDispute: $131, WorkbookPDF: $67, Habits Garden: $24
• PoopUp: $0, BioAge: $0

The product that made half a million dollars in four months is now the fifth line on his own dashboard, earning less than a tenth of what his current top product does. The price has come down too: the page now lists $199 for the starter tier, reduced from $299, and $249 for the all-in tier.

Nobody is hiding this. He publishes it, including the two products sitting at zero, alongside the exits (MakeLanding sold for $35k, GameWidget for $4k) and the failure that went furthest before dying (VirallyBot, $4k a month at peak, $80k of total revenue, discontinued).

The lesson inside the decay

A one-time-purchase digital product sold to a professional niche has a predictable arc. Early on, the audience that has been waiting for it buys in a rush. Then the addressable pool thins, competitors copy the format, the underlying technology moves, and the same file needs constant maintenance to stay worth $199.

Read that as neither cynicism nor failure. ShipFast did what a hit is supposed to do: it produced a large amount of cash quickly, bought its maker several years of runway, and funded a portfolio of follow-ups, three of which now earn more than it does. The mistake would be to model your own plans on the four-month figure and assume it persists. The dashboard says it does not.

It also explains the pricing arc. Lou moved from a single $299 tier to $199 and $249 tiers with a bundle, which is what mature digital products do when the early-adopter pool is exhausted. Builtplain's argument about setting a defensible first price holds in reverse here: the launch price was defensible precisely because the audience already trusted the seller.

What 8,378 makers tells you

The ShipFast page displays a counter: 8,378 makers using it, with the discounted pricing framed as available to the first 8,390 customers. Take that as a marketing device, but also as a scale check. Roughly eight thousand buyers at prices that have ranged from $199 to $349 is a business built on a few thousand transactions, not a few million. That is the encouraging part of the whole category.

A product like this does not need a mass market. It needs a defined professional group, a problem that costs them a week of work, and a price that is trivially justified against that week. Developers building a paid side project were exactly that group, and $299 against seven days of setup work is not a difficult sum for anyone who bills for their time.

The same test applies to any niche you know: how many hours does the recurring chore cost, who else does it, and what would they pay to skip it once.

The transferable checklist

1. Look for repetition, not ideas. The saleable asset is whatever you rebuild every time you start a new project.
2. Package in days, not months. ShipFast took about a week because the substance already existed.
3. Charge once, deliver forever. A one-time price on a downloadable asset removes churn, support tiers and billing complexity from the equation.
4. Launch on stacked channels the same day. Product Hunt, your own audience, the relevant forum. The 48-hour spike is most of the early revenue.
5. Have the audience first. The two years of public failures were the marketing budget.
6. Expect a decay curve. Plan the follow-up product while the first one is still peaking.

What was not repeatable

Three things in this story cannot be ordered on demand. The first is timing: August 2023 was an unusually hungry moment for developer tooling, with a wave of solo builders shipping AI-flavoured side projects and needing exactly this scaffolding. The second is the audience, which took two years and sixteen products to build and would not exist without the failures. The third is Lou's tolerance for shipping publicly and being wrong in front of people, which is a temperament rather than a tactic.

The repeatable part is smaller and more useful: notice what you already build for yourself, sell it to the people one step behind you, price it once, and do not assume the first four months are the shape of the next four years. Lou's dashboard is an unusually honest artefact for anyone considering a one-person software business, because it shows the hit and the decay on the same screen.