Founder Playbook · The Bootstrapped Founder
11 tactics from Marc Louvion
Marc Louvion — $50k of one-time sales per month
Watch the full episode“I have packed a bunch of failed startups in the past and I would drive my mind crazy I would spend a year building a product that nobody would ever want and so now my marketing is mostly launching and I see how people react”
The launch IS the marketing — ship to see real reaction, not to win
After burning a year on products nobody wanted, Marc inverted the loop: launches ARE the validation. Ship it, watch the reaction. Real traction means go all-in; a couple hundred bucks at launch with no excitement means keep it running and move on — never spend another six months on something probably nobody wants.
“do you have a time limit for this like if a product that doesn't like how long do you work on a product before you think okay maybe it's time to Pivot to something else so there are different stages um in the last year it would be maximum one month I'll never spend more than a month on it”
One-month ship ceiling — never grind past 30 days on a fresh idea
Hard cap: one month from idea to live. Anything longer means burning runway on something the market hasn't asked for. The exception only kicks in once a product has pre-validation — visible questions, feedback, inbound emails — proving demand already exists before deeper investment.
“I build it live on uh YouTube I set up my stream I have my little microphone and I go live every morning and I would spend two to 6 or 8 hours live building the product and then I get people's feedback so they're like they sometime they help debug my code this is my pre pre validation thing”
Stream the build live as pre-pre-validation
Before any launch, Marc builds on YouTube live. Viewers debug code, suggest headlines, and a subset become potential customers asking for specific features. The stream functions as a free QA team, marketing channel, and pre-pre-validation signal — all collapsed into the building itself, not a separate marketing step.
“I spent probably a week Gathering the code making a little documentation and I push it live before going on holiday to Hong Kong and then I just woke up to the lunch and at the time I was making maybe 3 to 4,000 a month and I would wake up to the launch with something like 3K already made within 2 hours”
Extract the boilerplate from your own 15-product pile
After 15 products of repeating the same setup — landing page, domain, payments, support — Marc spent one week packaging it as a boilerplate and shipped it before flying to Hong Kong. Woke up to $3k in two hours, nearly his previous monthly total. Solving his own repeated pain was the entire validation.
“the idea is to have some anchor price where you have a price that is slightly cheaper than another one with one or two or less three features less but it creates some kind of anchor people be like okay so that 169 is the price for the product and so that 199 makes sense afterward”
Anchor pricing with two near-identical tiers
ShipFast offers $169 and $199 tiers separated by a tiny feature delta. The cheaper price acts as a reference point so the higher one feels obviously justified. With a single price, buyers have nothing to compare against — they can't decide if it's worth it. The decoy makes the answer obvious.
“that's how I avoid building unwanted features I have tons of feedback about potential features for p fast and what made it successful is because I built it for myself and if I listen to all those feedbacks I'm going to build a very complex boiler plate and I do not do that instead I use it for myself”
Dogfood as feature filter — ignore the wishlist, eat your own work
Marc gets endless feature requests for ShipFast and rejects almost all of them. The filter: only features he hits while shipping his own products get added back. Customer wishlists bloat boilerplates into Frankenstein products — personal use is the discipline that keeps them lean.
“I decided to go with a one-time payment because you know as you said that it's much easier to sell um a onetime fee for something uh than it is to sell a subscription if if your product doesn't have a really good recurring value um there is no point of charging your recurring Revenue”
Charge one-time when there's no genuine recurring value
Subscriptions only make sense when the product produces ongoing value for the customer. For a finished-asset product like a boilerplate, a one-time fee converts dramatically better — there's nothing to justify a monthly bill. Honest test: would the customer feel ripped off paying again next month? If yes, ship one-time.
“I love what you've done on the homepage too where you show just how recently you updated the product here is the feed of like the GitHub commits that just integrates into to your website”
Show the GitHub commit feed on the landing page
For a $200 one-time purchase, buyers need positive recency signals that the product won't be abandoned. Embed a live GitHub commits feed on the landing page — it turns 'is this still maintained?' anxiety into a positive trigger. Free, automatic, and directly addresses the #1 objection to lifetime-license tools.
“I made it part of the Premium plan and people started to join and like like Shar a crazy help like debug each other out vote each others I get that a lot that says I don't know how to code but I want to be part of the Community”
Bundle a private Discord into the premium tier
Adding Discord access to the higher-priced tier turned ShipFast from 'code dump' into a place buyers stay engaged. Many people now buy partly to get into the community — meaning the community itself does upgrade-tier conversion work the code alone couldn't. Gate the private community behind the upper tier to justify the price gap.
“I built a little identity in my head of who I am and I try to turn off the emotion and just be like okay I like creating stuff and this is who I am since I'm a kid I create stuff I'm just going to keep creating stuff”
Identity beats motivation — 'I'm someone who creates things'
After ShipFast blew up, the hardest part wasn't getting there — it was the pressure that the next launch needed to be a hit. Marc's antidote isn't hype or hustle; it's identity. 'I'm not chasing wins, I create things.' That framing decouples output from emotional outcome — the loop indie hackers break themselves on after one big project.
“this year I have five days allocated for building stuff so from Monday to Friday where I'm offline most of the day I allocate my weekend so Saturday is in Sunday for Content creation Saturday would be for um the I just started the YouTube channel Sunday would be for writing the newsletter”
Five weekdays for building, two weekend days for content
Hard-block content production into its own days rather than squeezing it around shipping. Marc batches Saturday for YouTube and Sunday for the newsletter, with weekdays for code. Avoids the trap of perpetually 'too busy coding' to publish, and forces the batching that makes long-form content actually viable for a solo operator.