Landing page (greenfield journey) user journey - landing redesign
Persona
The non-engineer builder - a solo founder, indie hacker, or hobbyist with a product idea and no engineering team or bandwidth. Lives in chat tools, is skeptical of AI vaporware, and needs honesty about maturity before investing time. Success for them: they open the dashboard and start a conversation.
Entry points
| Entry | Arrives via | State of mind |
|---|---|---|
| GitHub README pointer | evaluating the project | "show me what this actually is" |
| Docs navbar "Website" link | a developer sharing with a PO | half-briefed, verifying |
| Direct / shared URL | cold link | 5-second attention budget |
The journey
1. Hero + conversation demo (0-5s)
- They see/do: H1 "Your next product starts as a conversation", the Public Beta badge, and the mock Bloom interview card - a real discovery exchange ending in "PRD draft ready - awaiting your approval".
- They're asking: "What is this, and is it real?"
- Decision to win: the demo card, not adjectives, convinces them the conversation IS the product.
2. Journey check (5-10s)
- They see/do: the switch strip - "Bringing an existing repository? See the adoption path."
- They're asking: "Is this page for me?"
- Decision to win: greenfield visitors continue; org visitors route to the adopt journey instead of bouncing.
3. The artifact trail (10-45s)
- They see/do: six real artifacts - PRD, milestone plan, UI design studies (their pick gates the UI work), GitHub issue, reviewed PR, deployment awaiting approval.
- They're asking: "What do I actually get, and where does it live?"
- Decision to win: every artifact maps to a tool they recognize - no slideware.
4. Control and honesty (45-60s)
- They see/do: "You stay the approver" (PRD, plan revisions, go-live) and "What Bloom won't do" (replace judgment, decide architecture alone, code ad-hoc).
- They're asking: "Do I stay in charge? What's the catch?"
- Decision to win: the stated limits read as honesty, converting the skeptic.
5. Exit (60s+)
- They see/do: "Start with a sentence" + three CTAs, with the Google sign-in disclosed up front.
Exits and CTAs (ranked by intent)
- Open the dashboard - the conversion this page exists for
- Read the developer docs - the technical evaluator
- View on GitHub - the skeptic verifying the project is real
Drop-off risks (accepted)
- The dashboard CTA lands on a Google sign-in wall with no tour - accepted; the sign-in is disclosed on the page ("The dashboard signs in with Google").
- The Public Beta badge will turn away users wanting finished software - accepted; honesty about maturity is the brand.
- The mock interview must be maintained as capabilities evolve - accepted, with content traceability enforced at design review.
Success signals
- The dashboard CTA is the dominant exit for non-technical visitors; docs and GitHub absorb the technical ones.
- Org-shaped visitors exit via the adoption path instead of bouncing.
- No analytics exist on the page today; click telemetry remains a future, privacy-respecting enhancement.