5 builders who never spoke to each other · contested
Ship on a cadence you cannot negotiate with
Commit to a fixed release rhythm, daily, weekly or monthly, and let the date rather than your judgement decide when something goes out, because the deadline is often the only reason it ships at all. Automating the release down to one command matters here, since ceremony is what quietly lowers the frequency. Two members push back: a public deadline attached to a revenue target produced burnout, and a standing release habit can become a way to avoid marketing.
Where this splits
A forced shipping rhythm is credited with most of what got released, and also blamed for burnout when tied to a public revenue deadline and for substituting for the marketing that actually sells.
side 01 · 11 claims
Let a fixed release date decide when you ship
Cory Zue · Jack Ellis · Justin Jackson · Luca Restagno · Peter Steinberger · Pieter Levels · Rand Fishkin · SparkToro
- 1Hold a monthly release commitment even when you would rather skip it, because the deadline is often the only reason the release ships.
- 2Set a hard publish date and ship on it, because the piece will never feel good enough and the alternative is not shipping.
- 3The habit that matters is putting something out every day rather than saving it for occasional large pushes.
- 4Run a counted streak of daily releases and review at the end of it what the streak actually produced.
- 5Increase release frequency rather than release size - small frequent updates make the next one easier.
side 02 · 3 claims
A forced cadence burns you out and replaces marketing
Cory Zue · Florin Pop
- 1Do not attach a short public deadline to a revenue goal; the compression pushes you to chase one improbable breakout instead of shipping steadily.
- 2Watch out for a monthly release habit becoming a way to avoid marketing; shipping is promotable, but it is not the same as promotion.
- 3Choose a streak length you can actually serve alongside paid work; 30 days done properly beats 100 days of thin output.
What it returned
- 2021
September 2021 brought $7,611.61 across products, with Pegasus at $5,455.38 and Place Card Me at $2,099.77, and Zue credited the forced monthly release with getting version 0.18 out
- 100
A streak of 100 consecutive days of shipping.
Zue decided on the month's final working day to publish his essay regardless of quality, crediting the monthly goal and retro process for forcing it out.
Rand Fishkin lists iterative quick launches of smaller features among the things SparkToro got right, and notes each new one produced a bump in engagement, coverage and subscribers.
Sources
- How I built 100 Projects in 100 DaysFlorin Pop · florin-pop.com · What would you do differently? · 2019-12-26 · dissenting
- I failed beforeFlorin Pop · florin-pop.com · What is different this time? · 2024-08-30 · dissenting
- You don't learn until you shipJustin Jackson · justinjackson.ca · You don't learn until you ship · undated
- @levelsio's blogPieter Levels · levels.io · Most important skill I learnt is to keep shipping day in day out · 2017-09-27
- No, I Will Not A/B Test That - SparkToroSparkToro · sparktoro.com · undated
- SparkToro's Year One Retrospective - SparkToroRand Fishkin · sparktoro.com · How Did Our First Year Go? · undated
- Code Signing and Notarization: Sparkle and Tears | Peter SteinbergerPeter Steinberger · steipete.me · Automated Everything · 2025-06-05
- 2020 Year in Review - Fathom AnalyticsJack Ellis · usefathom.com · Looking forward · 2020-12-23
- Shifting PerspectivesCory Zue · coryzue.com · Griffin · 2022-05-03 · dissenting
- The QuarantineCory Zue · coryzue.com · This Month’s Goals · 2021-09-06 · dissenting
- MomentumCory Zue · coryzue.com · Last Month’s Profit · 2021-10-01 · dissenting
- Week 21 RetrospectiveCory Zue · coryzue.com · Comments · 2017-08-14 · dissenting
- From 0 to $1.5k MRR: lessons from our first year building BlackTwistLuca Restagno · solopreneurtofreedom.com · 💬 Final thoughts · 2025-07-21
the second source
Three plays a week, for the phase you are in
No roundup of links, no news. Three tactics more than one builder arrived at separately, with the numbers each one returned and the disagreements left in.
More in product
- Give away a tool that pulls its own audience7 unconnected
- Take many small shots instead of one big bet6 unconnected · contested
- Get it into real hands, or shape it first6 unconnected · contested
- Cap the hours and let the ceiling design the business6 unconnected · contested
- Set the bar for writing code deliberately high6 unconnected
- Buy nothing until there is revenue6 unconnected