Recurring eggs
Weekly repeatability, strong trust signal, obvious pickup behavior, and a grower identity around the flock.
Bountiful Deep Growth Plan
Make one small place visibly abundant first.
The first Bountiful growth job is not generic users. It is assembling enough beautiful, repeatable harvest supply in Lafayette + Orinda that neighbors understand the product from the harvests themselves.
25high-fit growers identified
10personal contacts, not blasts
5growers activated with a real harvest
3repeatable harvest sources
2-3story-worthy exchanges captured
Working Thesis
Harvests are the ad.
Bountiful should grow by making Lafayette + Orinda feel like the place where nearby lemons, eggs, herbs, tomatoes, starts, and backyard fruit quietly find neighbors. The wedge is not a funnel. It is a real bag of lemons on a counter.
Can we make one neighborhood cluster feel alive with what is already growing nearby?
Start with Lafayette + Orinda. Let Moraga join naturally when a grower or connector pulls it in.
Prioritize repeatable, visible harvests: eggs, citrus, herbs, seedlings, tomatoes, and fruit-tree overflow.
Do not claim density before the product earns it. Small proof beats launch sprawl.
Growth Model
Growers create gatherers.
One strong grower can create many gatherers if the harvest is visible, specific, and easy to talk about. Early grower quality matters more than count.
Grower shares a real harvestEggs, lemons, starts, herbs, tomatoes, figs, citrus, backyard fruit.
Gatherer receives something memorableThe product becomes a thing on a porch, not an abstract app pitch.
Handoff includes a note or QR tagThe card rides with abundance instead of behaving like an ad.
Gatherer sees what else is nearbyDiscovery starts from trust: this came from a neighbor.
Another grower gets invitedThe next best lead is often someone the gatherer already knows.
Product proof, not imagined UI.
The page uses real Bountiful product and field-kit assets. Public copy should stay equally grounded: local, seasonal, and careful about what is already true.
Grower Segments
The first supply wedge.
Look for neighbors whose harvests already have repeatability, story, or local trust. The right first ask is small: try one harvest post.
Citrus and fruit trees
Visually obvious and deeply backyard-coded: lemons, oranges, mandarins, figs, avocados, persimmons, guava, and rare fruit.
Starts, herbs, tomatoes
Seasonal growers who already think in swaps, starts, pruning, and garden conversations.
Connectors
Garden clubs, nurseries, school gardens, chicken circles, farmers markets, and newsletter editors who know the growers.
Channel Strategy
Show up where harvest signals already exist.
The first channels should help find real growers and warm connectors. Avoid broad promotion before the local proof exists.
Craigslist scouting
Use farm & garden, free, and relevant for-sale surfaces to identify high-fit local surplus. Save only specific, human leads.
Garden institutions
Approach Lafayette Community Garden, Lafayette Garden Club, Orinda Garden Club, Montelindo Garden Club, and local market organizers for advice and referrals.
Founder-led email
Send five to ten messages max per wave, each tied to a specific harvest signal. Track replies before sending more.
Density before reach.
The map only becomes magical when a small radius has enough real harvests to feel alive. Lafayette + Orinda is the right first proof cluster.
Porch Loop
The card belongs with the harvest.
Field cards are useful when the physical harvest is already present or a real grower conversation is happening. They should feel like a note attached to abundance, not a generic flyer.
Good uses
Handed to a grower after a conversation, tucked into a bag of lemons or eggs, left with a connector who understands the idea, or used at a garden event.
Bad uses
Random windshields, broad coffee-shop stacks before proof exists, or QR cards with no harvest context.
Offline to online.
The best early loop starts in a real handoff, then sends the gatherer back into nearby discovery.
First Experiments
Four small tests before scale.
Each experiment should create learning, not vanity activity. The target is one real harvest story that can power the next outreach, card, and landing block.
Ten-grower outreach
Three egg growers, three citrus or fruit-tree growers, two seedlings or starts growers, one herb or tomato grower, and one connector.
Garden connector call
Ask for advice and names, not promotion. Success is three local names or one phrase worth reusing in copy.
Porch loop test
One real harvest, one card or note, one QR destination, one follow-up question after pickup.
Harvest story block
Replace abstract landing copy with one real story once it exists. No invented supply, no inflated claims.
Next 7 Days
The first week should stay narrow.
Finish the plumbing, expand the prospect list, draft carefully, send only a tiny wave, and learn from real replies before widening.
Day 1
Email and DNS closeout
Send test emails to Jonathan and Patrick, confirm deliverability, confirm reply behavior, and decide default sender identity.
Day 2
Prospect list expansion
Turn Craigslist category leads into 20 named, specific prospects tagged by harvest type, location, fit, and outreach angle.
Day 3
Outreach drafting
Write 10 personalized drafts split across eggs, citrus, starts, rare fruit, and connector targets. Keep each under 120 words.
Day 4
First tiny wave
Send five messages only. No automation. No follow-up yet.
Day 5
Garden institution touch
Draft one advice-first note to Lafayette Community Garden or Lafayette Garden Club. Ask for a conversation or referral, not promotion.
Day 6
Field card check
Decide QR destination, review print kit against current product truth, and soften any unsupported program language.
Day 7
Learning review
Summarize replies, identify the warmest harvest type, pick the next five prospects, and update language from real words people used.
Recommendation
Earn the first neighborhood.
The sharpest move is to finish email proof, send a tiny founder-led test wave, prioritize eggs, citrus, and rare fruit/tree people, then use one real harvest story to power the next copy and field materials.
1
Finish email plumbing proof
Use Patrick only after sender approval is settled. Keep tests narrow and accountable.
2
Send a tiny founder-led test wave
Five messages, each tied to a specific harvest signal. No broad campaign behavior yet.
3
Prioritize eggs, citrus, and fruit-tree people
They offer repeatability, visual proof, and the strongest everyday neighbor story.
4
Capture one real harvest story
Use that story to make outreach, cards, and landing copy feel earned instead of promotional.