Phase plan: two launches on the fishing calendar

Part of the «Waze для рыбалки» wiki · Strategy, 2026-07-06 · Status: draft for Piotr's review — not yet wired into nav
Related: Roadmap · Segments & calendar · Latvia market · Fishbrain: Baltic region · Wedge verification (working draft)

Why these dates

The Latvian fishing year has four predictable traffic spikes — first ice, May 1 (boats open), Jun 1 (zander opens), Oct 1 (salmon-river closures + autumn coast) — see the activity calendar. Decision (Piotr, 2026-07-06): time the two launches to the two spikes we can still reach this year. Phase 0 goes live Oct 1 — the utility floor, shipped quietly. Phase 1 launches on first ice — the liquidity bet, with all the noise. Every date below derives from those two.

Numbering note: roadmap.md currently calls the July validation work "Phase 0". On this page validation is the critical path before Phase 0, and the Oct 1 release takes the Phase 0 name. If Piotr confirms this plan, the roadmap needs the matching renumber.

Phase 0 — Oct 1: the utility rehearsal

Oct 1 is the year's hardest rules-regime change. Salmon/trout rivers close Oct 1–Dec 31 with intensified VVD + Zemessardze day/night patrols (€715 in damages per illegal salmon), the autumn coastal season peaks (flounder from September; six coastal species carry a 24h e-registration duty since Jan 2026), predator season starts, boats get winterized. This is the moment "Can I fish here right now?" is worth the most: 2023's €22,883 in fines were mostly ignorance-level violations.

What ships — deliberately feed-less. The "Can I fish here right now?" engine: species closures by date, licensed-water overlay, boat bans, card check, deep links into Mana Cope / e-Loms for the actual purchase — integration, not aggregation, because the permit-aggregation wedge is dead. PWA, no store app, read without registration, LV+RU.

Distribution: quiet. Seeded via the known channels — Fishing LV FB group (30k+ members), copeslietas.lv, the YouTube pair (Cope Latvijā TV / FISHING LV с Виталием). Zero marketing spend; all the noise stays in the Phase 1 magazine.

What Phase 0 buys:

1. The de-risking gate — does pure utility earn weekly returns? This is the go/no-go input for everything after.
2. The winter waitlist — "ice mode is coming, leave an address."
3. Channel calibration — which seeded channel actually pulls, measured before we spend the one launch moment.
4. Foundation code — the Oct–Dec salmon-river report-suppression gets built now, so spot governance is production-tested before any social layer exists (the poacher's-map risk from latvia-market).
5. The VVD/BIOR relationship — open the compliance-helper conversation while the app is still safely a rules utility.

Phase 1 — first ice: the liquidity bet

The trigger is weather, not a date. The national ice season opens on the first ~7 cm ice after several days at ≤ −5°C — typically December, and Alūksne-area anglers traditionally open it. From ~Dec 1 we sit armed: launch kit ready, marketing held. We launch the day the season opens.

What ships: ice mode on top of the Phase 0 utility — ice thickness/safety reports, coarse real-time density, spot check-ins. Full app launch; every reserved marketing shot fires here.

Why first ice carries the whole bet:

• It is the recorded peak-traffic event of the Latvian fishing year (calendar, December row).
• Ice is the one context where daily utility self-justifies: "is the ice safe today?" is perishable, hyperlocal, and asked every single morning.
• Spot secrecy is weakest on ice — a crowd on a frozen lake is a public folk event; ice is not spots (roadmap).
• The safety angle buys trust and the media story — 2013 Gulf of Riga: two drifting floes, 223 anglers, helicopter rescue; rescues recur every winter.
• Nobody has an ice mode — not Fishbrain, not Deeper, not any Nordic app, despite Finland's ice culture covering ~10% of its whole population (7-country page).

The moat — what defends this once it works

Definition. A moat (Buffett's term: the business is a castle, the moat is the water around its walls) is protection against replication — whatever stops a competitor from taking your users even when they can see everything you do and have more money. The test: an advantage helps you today; a moat keeps working under attack. A beautiful app is an advantage (copied in a month). A thousand anglers who send their reports to you daily because they trust you is a moat: to take it, a competitor doesn't need to write code — they need to convince a thousand people, one by one.

The 7-country research answers why incumbents lost; this section answers what we'd own. The moat is local liquidity times trust — and the phases are its construction schedule (Phase 0 builds trust, Phase 1 builds liquidity).

1. Regenerating local liquidity (the structural moat). "What's biting / is the ice safe now" is perishable — worth hours, not months. A competitor can't scrape yesterday's data and catch up; they need today's anglers on today's lakes. Once a lake-cluster has live density, every new report deepens the gap — classic local-network winner-take-most (ss.lv, Bolt, ANGLERS). Fishbrain's 15–20M global users demonstrably buy it nothing here.
2. Trust architecture (the social moat). Verify-exact-publish-coarse, salmon-river suppression, k-anonymity heatmaps (principles) — anglers give real data only to a system visibly designed not to burn spots. Trust accrues slowly, transfers not at all, and a global player structurally can't promise it (Fishbrain's privacy tiers got gamed; catch-photo prosecutions made public posting chill). This is why liquidity, once earned, is defendable rather than buyable.
3. Ice-safety authority (the seasonal beachhead). The brand that owns "is the ice safe today?" owns winter; winter owns the year's liquidity spike. Safety data has life-and-death stakes, media pull (2013 floe), and institutional goodwill — none of it copyable by a feature checkbox.
4. Bilingual LV/RU depth. ~36–38% RU speakers concentrated exactly in the lake-rich regions (Latgale). Global players won't ship RU-first community UX in the Baltics; for us it's native.
5. Institutional position. BIOR openly lacks recreational catch data; VVD wants compliant anglers. Anonymized-data partnership + poacher-report pass-through + e-loms integration = a quasi-official standing a foreign app can't replicate quickly (latvia-market).

Explicitly NOT moats: the rules engine (table-stakes, copyable), permit aggregation (dead — Mana Cope owns it, wedge verification), the tech stack (commodity), and hardware-community hopes (Lithuania's lesson: even Deeper's decade of sonars didn't auto-create social liquidity).

The one player who could contest it: Deeper's Waterbody Hub — the only actor with a seed community (sonar owners) and Baltic presence. Counters: speed to first ice (they have no ice mode), secrecy-native trust rules (their Hub is public-feed-shaped), RU/LV depth, and the institutional lane. If they move first in Latvia, the gate criteria (below) get re-read against that fact.

Countdown

The gate between phases

The thresholds below are placeholders — Piotr sets the real numbers after K's answers land. No external benchmark for "liquidity achieved" exists anywhere; the 7-country sweep flags exactly this gap.

Phase 0 must show, by ~mid-Nov:

• Retention — a real weekly-return cohort on pure utility (placeholder: ≥25% of first-week users seen again in a later week).
• Waitlist — winter signups measured in hundreds, not dozens, on zero spend.
• Channels — at least one seeded channel with traceable pull.
• Data integrity — the rules engine survived the Oct 1 regime change with zero "app said legal, it wasn't" incidents.

What failure looks like, and the rethink:

• One-visit users (check once, never return) → utility alone is not a floor. First ice still launches — ice utility is different in kind — but the post-ice roadmap gets rethought: compliance-helper/B2G first, paid-pond booking first (the region's one un-digitized transaction), or hobby pace.
• No channel pull → the Phase 1 launch plan is fiction; recalibrate channels before firing the one shot.
• A rules-data incident → feature freeze, fix the pipeline first. Liability posture beats growth.

The Phase 1 date never moves — the season won't wait. The gate decides what launches (full app vs. ice-only wedge) and how loud.

Risks

Draft for Piotr's review · 2026-07-06 · not yet wired into nav — README and roadmap untouched.