Cast Wide, Then Stay
On the methodology in founder translation, the deepening that the fishing allegory hides on first reading, and how to read what the world tells you back when you finally put a line in the water.
The first three essays have been about orientation. See the landscape in Essay 1. Know your shape in Essay 2. Decide whether to begin in Essay 3. This essay is about doing the actual work — the practice that follows when the orientation is clear and the decision has been made.
The work has three parts that are usually conflated. The first is the methodology, which is essentially the deep-sea fishing allegory rendered in founder vocabulary. The second is the inversion the methodology hides on first reading — the part that distinguishes founders who compound from founders who keep moving and never compound. The third is how to read what the world tells you back, which is the only honest version of validation.
The methodology, plainly
Let me give you the methodology in its simplest founder translation. The cleanest contemporary version comes from Young Zhao, an entrepreneur whose podcast I processed recently, and whose 30-day playbook for launching a calling-shoal business sits at exactly the right level of abstraction.
The 30-day playbook is the deep-sea fishing trip translated for people who own spreadsheets.
Days 1 through 7: publish three essays anywhere friction is lowest. Substack. Email list. LinkedIn under your real name. The platform doesn’t matter. What matters is that something is in the water — that you have cast at least one bait into a place where a reader can encounter it. You are not building anything yet. You are not designing the perfect website. You are not crafting the bio. You are publishing.
Days 8 through 14: observe the response. Not the surface metrics — likes, claps, public reactions — those are the noise. The actual signal: who returned to read another piece without being prompted? Who emailed you? Who shared it with one specific friend? Who said something to you in person that made you realize the work landed somewhere? The early reader signal is small and quiet. You have to be paying attention for it.
Days 15 through 21: build the platform. Now, after the first essays have been published and the early signal has been observed, you can build the website. You build it informed by what the early publishing revealed about voice, audience, and angle — instead of building it blind around assumptions you would have had to redo in month three.
Days 22 through 30: distribution and proprietary thinking. What channels actually reach the readers who responded? What email-list growth strategy fits your specific work? What would a long-form proprietary asset look like — a course, a digest, a book in slow accumulation — that the first month’s signal suggests is worth building?
This is the corrected order. The natural instinct of an analytically-trained mind is to build the platform first — buy the domain, install the theme, configure the database, set up the deployment pipeline, write the about page. The platform comes first because the platform is the visible object, the legible deliverable, the thing that looks like progress to an analytically-trained body. The corrected order says no. The platform absorbs energy that should be going to publishing. The platform built before any reader signal has been observed is a platform built blind. The body that fears being seen will reach for the build instinctively because the build is invisible labor. Build the visible deliverable around the signal once the signal exists, not around the assumption of a signal you have not yet generated.
This is the methodology, then, in the simplest founder vocabulary: cast wide, observe what comes, build the boat that fits the catch you are actually getting, expand from there. The same shape as Eric Ries’s build-measure-learn in The Lean Startup (Ries, 2011), Steve Blank’s get out of the building in customer-development (Blank, 2005), and Rob Fitzpatrick’s principle that what people do beats what they say in The Mom Test (Fitzpatrick, 2013). The fisherman knew it before any of them did.
The inversion the allegory hides
There’s an inversion the deep-sea fishing allegory does not announce on first reading but contains, and it has to be made explicit, because reading the allegory wrong on this point produces a year of motion with no compounding.
Read at the surface, the fisherman’s lesson sounds like broaden — try many baits, fish many waters, sample many things, don’t just do one thing. Read more carefully, the lesson is deepen — stay out longer than the others, in the water you committed to, casting many baits into the same waters across many seasons, until you know those waters in your sleep.
The width is at the level of bait variety inside the same shoal, not at the level of shoal variety across the whole ocean.
This matters because most early-stage founders, having heard the fisherman’s lesson, mistake it for a license to keep moving across categories indefinitely. Today I will write about productivity. Tomorrow about parenting. Next week about geopolitics. The fisherman said try many things. The fisherman did not say that. The fisherman said cast many baits in the water you stayed in long enough to know. The water is one. The baits are many. The seasons are years. The compounding requires staying.
The forager understood this all along, which is one reason the contemplative cousin is helpful. The forager doesn’t walk a different forest every morning. She walks her forest, the one she grew up in, and she walks it across all four seasons across all the years of her life. Each morning is a new walk in the same forest. The variety is in what the forest has decided to offer that day. The constancy is in the forest itself.
For the writer, deepening looks like this: one calling shoal, named clearly enough that you can recognize its boundary, fished daily for years, with as many bait shapes as your life can supply. Essays this season. A book the next. A course the third. A retreat the fifth. A fellowship the seventh. The shoal is constant. The forms vary because the work matures.
For the founder, deepening looks like this: one well-defined unfair-advantage water, served through one clear primary product first, then through adjacent products that emerge from your maturing knowledge of the customers in that water — who are the same customers the whole time, whose problems you understand more deeply each year, whose language you speak more natively each year. The customer base is constant. The product portfolio expands because the relationship deepens.
The wrong move — and this is the move most beginners make — is to treat the fisherman’s try many baits as license to try many shoals until something works. This is the surface read. It is also the read that produces decade-long careers full of motion and no compounding. The compounding lives in the staying. The variety lives in what the staying allows you to discover.
To pivot the methodology from check-and-broaden the surface to deepen and discover, the move is structural and simple. Identify your calling shoal as carefully as you can with the information you have today. Commit to it for a defined window — a year is honest; six months is too short; three years is the place where compounding starts to be unmistakable. Treat every subsequent question of should I try a different water? as a foundation-gambit warning rather than a legitimate exploration. Within that window, vary the baits as freely as you like. Outside that window, do not vary the shoal.
The truest passion is not found at the surface of many waters. It is found at the depth of one water, eventually. The surface is where you decide which water to commit to. The depth is where the work that wanted to come through you finally comes through.
How to read what the world tells you back
The methodology has cast baits. The deepening has held you in one water. Now what?
The naive version of validation — the one most popular advice teaches — counts surface metrics. Page views. Likes. Subscribers. Open rates. These are easy to measure, which is why they get measured, which is why they crowd out the metrics that actually matter.
The honest version of validation is harder to count and easier to feel. Validation is to get something back from the world. The world cannot give anything back if you haven’t sent anything out — which is why the methodology insists on publishing first. But once you have sent something out, the data lives one or two layers deeper than the metrics.
For a calling-shoal business specifically, three signals are worth more than any surface count.
The unprompted return test. Cast a small bait — a single essay, a single voice memo, a single conversation. Note who comes back without being prompted. In a phantom shoal, no one returns; the fish were never there. In a calling shoal, even small early casts produce someone who keeps showing up, asking when the next one is, sharing it with one specific friend. The number is small. It is enough. One returner is more validation than a hundred shimmering likes.
The unprompted articulation test. When someone in your calling shoal encounters your work, they will often respond by trying to articulate something they had previously been unable to articulate, often using your language to do it. I had no words for this. You said the thing I have been trying to say. The phantom-shoal response is interesting! and silence afterward. The calling-shoal response is I have been needing this, and now I can finally say what I needed.
The behavioral change test. Two weeks after the bait is cast, observe what your reader has done that she would not have done without the bait. Has she written something she had not been able to write? Started a practice she had been deferring? Made a phone call she had been postponing? Phantom-shoal work produces no behavior change because it does not address actual decisions. Calling-shoal work changes small behaviors quickly and visibly.
What is not a valid signal is to assume calling-shoal correctness exempts you from validation altogether. The calling does not relieve you of the duty to test. The most painful failure mode in the calling-shoal category is the founder who, having correctly identified her water, refuses to actually cast because she feels her water deserves to be fished without the indignity of having to prove itself. The water owes her nothing. The casting must still happen. The calling shoal is not a verdict; it is a hypothesis with much better priors.
A note on plan B, since the question always comes up. Common wisdom says have one. Emerging research from Jihae Shin and Katherine Milkman (2016) suggests the framing matters more than the existence: participants who simply thought through a backup plan performed worse on their primary task — the effect mediated by reduced desire to attain the primary goal. The implication is precise. Have plan B as structure (income source, savings, support); refuse it as cognitive rehearsal of failure. The honest version: keep the structural safety net; refuse the daily mental visit to it.
What you do not do
There are three moves that look like work and are actually delay, and they are worth naming so you can recognize them in yourself.
The build-first move. You spend two weeks designing a website before you publish anything. The website is invisible to anyone yet because there’s nothing on it. The build absorbed the energy that should have gone to writing. Recognize this as foundation gambit, not preparation.
The endless-research move. You read a fifth book on methodology before you write your first essay. You take a sixth course on copywriting before you launch the email list. The research replaces the practice. Recognize this as avoidance with the body language of diligence.
The credentialing move. You enroll in a certification program because you don’t yet feel qualified to begin. The certification is a real thing — it gives you something — but it usually delays the only thing that produces actual qualification, which is the practice itself. Recognize this as a permission slip you don’t actually need.
None of these is bad on its own. The website matters eventually. The reading matters. The credential might matter. The problem is the order. All three become problems when they precede the actual casting. Cast first. Build the platform once you know what shape it should be. Read the books once you know which questions you actually have. Get the credential once you know whether you need it.
What the work actually looks like, day by day
I want to close this essay with the most honest description I can give of what the work looks like inside one ordinary week.
You wake before light. You make tea. You sit at the page in the dark, with a cat on your lap if you have one, and you write what wants to come. Sometimes the writing is good. Often it isn’t. Some mornings nothing comes and you sit with what doesn’t come and that is also the work.
Once a week, possibly twice, you publish one of the things you wrote. You don’t promote it heavily. You don’t engineer the launch. You put it in the water and you go on to the next morning’s writing.
You watch, quietly, for the small specific signals — the unprompted return, the articulation, the behavior change. You don’t refresh the analytics page. You let the signal come to you in the form it actually comes (an email, a forwarded link, a stranger mentioning your essay in conversation).
You stay with this for a year.
After a year, you assess. Probably the work has compounded. Probably one or two specific reader-types have emerged whose return is reliable. Probably an angle has clarified that you didn’t have when you began. You build the platform now, around what the year’s signal actually showed.
Then you stay with it for another year.
This is the work. There is nothing more dramatic than this. The drama is for the open-ocean founder, whose metabolism wants the chaos of new beginnings. The home-water founder works inside this quieter rhythm, year after year, until eventually — usually around year five or seven — the catch is no longer occasional but reliable, and the working life she had been building has, without her noticing the moment of arrival, arrived.
Where these ideas come from
The 30-day playbook framing is Young Zhao’s (Mogilko, 2025), in his conversation with Marina Mogilko. The build-order inversion (publish before build) was applied here on 2026-05-10 as the corrective for my own draft WordPress TODO that had the build at days one through two.
The deepening-not-broadening argument is mine, written here on 2026-05-10 as the inversion the deep-sea fishing allegory hides on first reading.
The three calling-shoal signal tests (unprompted return, unprompted articulation, behavior change) are mine, calibrated for what actually distinguishes a calling shoal from a phantom shoal at the level of reader response.
The build-measure-learn / customer-development / what people do beats what they say lineage runs through Eric Ries (Ries, 2011), Steve Blank (Blank, 2005), and Rob Fitzpatrick (Fitzpatrick, 2013) — the modern founder translation of an older fisherman’s wisdom.
The plan-B research is Jihae Shin and Katherine Milkman (Shin & Milkman, 2016).
The naming of foundation gambit (the recursive upstream-cause pivoting that disguises itself as legitimate preparation) is mine, from earlier work, named on 2026-05-08.
Bibliography
Blank, S. (2005). The Four Steps to the Epiphany: Successful Strategies for Products that Win. K&S Ranch. ISBN 978-0976470700.
Fitzpatrick, R. (2013). The Mom Test: How to Talk to Customers and Learn if Your Business is a Good Idea When Everyone is Lying to You. Founder Centric. ISBN 978-1492180746.
Mogilko, M. (Host). (2025, December 29). $215M AI CEO: How I’d Build a Profitable AI Startup in 30 Days (2026 Playbook) [Audio podcast episode]. In Silicon Valley Girl. Guest: Young Zhao, OpusClip.
Ries, E. (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Currency. ISBN 978-0307887894.
Shin, J., & Milkman, K. L. (2016). How backup plans can harm goal pursuit: The unexpected downside of being prepared for failure. Organizational Behavior and Human Decision Processes, 135, 1–9.