Why do you publish your roadmap? Angi and Thumbtack don't.⌄
Because they benefit from information asymmetry and we don't. When a homeowner or contractor can't see what we're building next, they have no basis to trust that the platform will be around in 6 months. Public roadmaps are standard for enterprise SaaS (Linear, GitHub, Stripe all do it); we're applying the same discipline to a contractor-matching platform.
Are you committed to these dates?⌄
Phase 18 and Phase 19 windows are historical facts — what shipped is what shipped. Phase 20-23 windows are best-effort with honest explanation if they slip. We'd rather say 'Q3 2026' and ship on Oct 1 than say 'Q1 2026' and ship Q3. The /reviews page documents the aggregateRating threshold we won't backdate for — same discipline applies here.
What's the single biggest thing blocking AskBaily from replacing Angi?⌄
Supply. We have 1 active contractor (NPLD, Los Angeles) and 82 on the waitlist. Our content + AEO + matching engine all work, but the end-state of the product is 'homeowner chats with Baily → gets matched to a real vetted pro → project happens' and that pro has to exist. Phase 21 is dedicated specifically to solving this via the Growth-Sales agent + automated pro recruitment.
When can I pay through AskBaily?⌄
Phase 20. Wave 181 target is Q3 2026. Stripe Connect scaffold already shipped at Wave 167 (51 tests green, flag-off). Activation is gated on our review readiness — we want to handle a real deposit with zero surprises on day one, which means migrating the MariaDB schema on the VPS, running Stripe webhook signing end-to-end in TEST mode first, then flipping to LIVE with a tiny test-transaction with NPLD as the first partner account.
When will AskBaily be in the App Store / Play Store?⌄
Phase 20, Wave 183. Expo React Native app already built at Phase 5.A-5.T (33 files, 3,717 LOC, chat SSE + phone OTP + Universal Links + App Links + Firebase observability + CI/CD via EAS Build). Gating is on Apple Developer account + Google Play Console access for binary submission.
What's a 'HARD tier' jurisdiction?⌄
In the Wave 174 license-verifier research, we classified each of 115 jurisdictions as EASY (direct JSON/REST API), MEDIUM (stable HTML scrape), HARD (SPA requiring headless browser), or BLOCKED (no online lookup exists). HARD examples: Arizona ROC is Salesforce Experience Cloud; Dubai Municipality is a Trakheesi-style SPA; Japan MLIT has prefecture-scoped registries behind captcha. Building one Playwright-on-VPS microservice unlocks all 27 HARD jurisdictions at once — that's the Wave 176+ plan when license verifiers are back on the active roadmap.
Why is this roadmap labeled 'Wave 176' in the commit history but also 'Phase 18'?⌄
Waves are the unit of shipping — each is a commit (or small set of related commits) with a coherent deliverable. Phases are the strategic arcs — each is 20-100+ waves. Phase 18 was the content/AEO/trust arc; Wave 176 shipped the /roadmap page that closes out the Phase 18/19 transparency cluster. Next phase's first wave will get a new phase label.
Where can I audit what actually shipped?⌄
Every wave is in the git log (git log --oneline on the askbaily repo). Every major wave has a memory project file in /Users/bl3/.claude/projects/-Users-bl3-mautic-local/memory/project_askbaily_*.md — these document what shipped, the commit hashes, and the rationale. Our /llms-full.txt surfaces the public-facing subset for AI-engine citation.