Journey Map

Product: gblock-party Date: 2026-05-27 Based on: research/icp.md, research/competitive-analysis.md, concept briefs

Summary

The Agent Conductor (primary ICP: solo developer / indie hacker running 2-10+ AI coding agents) follows a lifecycle driven by infrastructure scaling triggers and mobile access needs across two tracks: Track A (BYO-client) connects an existing front-end tool (T3 Code, Multica, Claude Code CLI) to gblock-party's managed infrastructure; Track B (Agent Board) uses gblock-party's native Agent Board. gblock-party manages the server infrastructure in both tracks. Five core user journeys map the task-level experience; the customer lifecycle maps the relationship from trigger through advocacy and churn.

The product wins or loses at five critical moments: first setup (5-minute bar), first laptop close (persistence proof), first mobile approval (phone proof), first review bottleneck (scale proof), and first bill (value justification vs. DIY alternatives).

The aha moment, in users' own words: "I started 5 agents, closed my laptop, had dinner, checked from my phone — 3 PRs were ready for review."

User Journeys

Primary persona: The Agent Conductor — solo developer using 2-4 AI coding tools simultaneously. Enters via Track A (BYO-client: existing front-end tool) or Track B (Agent Board: gblock-party front-end).

Journey 1: Scale Past the Laptop

Trigger: Running 3-5 agents locally, laptop CPU/RAM maxes out

Track A: BYO-client
  1. Already uses a front-end tool (T3 Code, Multica, Claude Code CLI)
  2. Discovers gblock-party (blog / HN / Reddit)
  3. Signs up for gblock-party, gets API credentials
  4. Connects existing tool to gblock-party's managed infrastructure
  5. Agents now run on persistent cloud servers
Track B: Agent Board
  1. No existing tool preference — discovers gblock-party (blog / HN / Reddit)
  2. Signs up, clicks "Create Environment"
  3. gblock-party provisions managed environment
  4. Agent Board connects to managed infrastructure
Both tracks converge
  1. Agent Board loads — connected host visible
  2. Start first agent session from the Board
  3. See all agents in one unified view
"Is this meaningfully better than my current DIY setup?"
Agent Board shows all sessions with real-time status, mobile works, sessions persist across devices
Setup friction too high, or orchestration adds latency to agent execution (T3 Code 4x slowdown warning)

Journey 2: Check from Phone

Trigger: Away from desk, agent needs approval or long-running task finishes

  1. Receive push notification on phone
  2. Open PWA — see agent status at a glance
  3. Review approval context (action, risk level, affected files)
  4. Approve or reject with one tap
  5. Optionally review diff before agent pushes
  6. Resume other activity
"Can I actually do useful work from my phone in under 30 seconds?"
Push notification → one-tap approve → back to life in <30 seconds
Mobile UI too cramped for diffs, approval context insufficient to make safe decisions

Journey 3: Close Laptop, Keep Working

Trigger: End of work session, agents mid-task

  1. Close laptop — agents continue running on gblock-party's managed infrastructure
  2. Agents complete tasks, queue approvals if needed
  3. Check next morning from any device (laptop, phone, tablet)
  4. Review "what happened while I was away" summary
  5. Review completed diffs, approve pushes
"Did I lose any state? Can I see exactly what happened?"
All sessions exactly where they were, output captured, diffs ready for review, session recap available
Session state corrupted, output lost, no clear summary of what changed overnight

Journey 4: Parallel Sprint

Trigger: Multiple features/bugs to ship, wants to parallelize across agents

  1. Start 5-8 agents across repos with specific prompts/specs
  2. Monitor progress via Agent Board — per-agent status cards
  3. Handle approval prompts as they arrive (desktop or mobile)
  4. Git worktree isolation prevents merge conflicts
  5. Batch-review diffs across agents
  6. Ship PRs for completed work
"Can I track what each agent is doing without context-switching between terminal windows?"
Board shows per-agent status, worktree isolation works, batch review flow keeps velocity high
Merge conflicts from agents on shared files, review bottleneck overwhelms (can only review so fast), 3-5 agent sweet spot exceeded

Journey 5: First-Time Setup

Trigger: Discovered gblock-party, ready to try it

Track A: BYO-client
  1. Sign up free (self-serve, no procurement)
  2. Copy API credentials from dashboard
  3. Configure existing front-end tool to connect to gblock-party
  4. Tool connects — sessions now run on persistent infrastructure
Track B: Agent Board
  1. Sign up free (self-serve, no procurement)
  2. Click "Create Environment" in dashboard
  3. gblock-party provisions managed environment
  4. Agent Board loads showing managed environment
Both tracks converge
  1. Start first agent session from the Board
  2. Bookmark PWA on phone for mobile access
"How long until I see value?" (target: under 5 minutes)
Signup → connect → first agent running in under 5 minutes, zero config
Track A: API credential setup confusing, tool integration docs missing, connection fails silently. Track B: provisioning takes too long, unclear status during wait.

Customer Lifecycle

Trigger

Scaling past laptop

Discovery

Blog / HN / Reddit

Evaluation

Free signup, try

Onboarding

Connect tool / board

Aha

Laptop close + phone

Conversion

Free → paid

Retention

Daily Agent Board

Expansion

Solo → team

Stage
What Happens
Key Metric
Trigger
Laptop maxes out at 3-5 agents, or first mobile access need (away from desk, agent needs approval). Searches for remote agent hosting solutions.
—
Discovery
Finds gblock-party via blog post, Show HN, Reddit thread, or tutorial search ("run Claude Code remotely", "AI agent orchestration"). Peer recommendation in Discord/Slack.
Traffic source, CTR
Evaluation
Free signup. Track A: connects existing front-end tool, compares to DIY setup. Track B: creates managed environment, evaluates provisioning experience. Solo decision in minutes to hours. Checks GitHub stars, open-source signal. Will not pay before trying.
Signup → install rate
Onboarding
Track A: configures existing tool with API credentials, connects to managed infra. Track B: click "Create Environment", gblock-party provisions managed environment. Agent Board loads. First agent session started. PWA bookmarked on phone.
Time to first agent session (<5 min target)
Aha Moment
"I started 5 agents, closed my laptop, had dinner, checked from my phone — 3 PRs were ready for review." Sessions survived laptop closure + successful mobile check.
Sessions surviving laptop close + mobile check-in
Conversion
Free → paid when hitting free tier limits (host count, advanced features) or when value is proven. Self-serve credit card. $9-29/mo flat rate.
Free-to-paid conversion rate
Transaction
Self-serve billing. Flat monthly subscription. No credit-based pricing (avoid Intent's hostile model). Managed devbox add-on available ($49-199/mo).
MRR, ARPU
Retention
Daily use — Agent Board becomes primary AI coding interface. Session persistence + mobile access create switching cost. Value exceeds free DIY alternatives.
DAU/MAU, sessions/day
Expansion
Solo founder hires first engineers → team tier ($29-79/seat). Or adds managed devbox. Natural PLG land-and-expand motion.
NRR, seat expansion
Advocacy
Blog post about workflow, HN comment recommending gblock-party, GitHub star, Discord recommendation to peers.
NPS, referral rate
Churn
First-party tools close the gap (Claude/Codex ship native multi-agent mobile), or workflow changes (stops using AI agents, switches to Cursor cloud).
Churn rate, exit survey
Recovery
Feature announcement re-engagement ("we shipped X you asked for"). Lifecycle email. Community re-engagement via Discord/HN.
Win-back rate

Critical Moments

The 5 moments where gblock-party wins or loses the user, ranked by impact.

1

First 5 Minutes (Setup)

If setup doesn't work on the first try, the user goes back to DIY (Track A) or abandons signup (Track B). Track A: connecting an existing tool must be frictionless — API credentials, zero server config. Track B: managed environment must provision in under 60 seconds. The 2026 PLG bar is value in under 60 seconds.

Evidence: ICP research — "Will not pay before trying. Need to see value in under 60 seconds."

2

First Laptop Close (Persistence Proof)

The first time the user closes their laptop and successfully resumes from another device is the aha moment. If sessions are lost or state is corrupted, the core value proposition fails entirely.

Evidence: "Close the laptop, pick up where I left off" is the #1 stated desire across VPS+agent articles and ICP interviews.

3

First Mobile Approval (Phone Proof)

The first push notification → approve flow on the phone proves "you don't have to be at your desk." If the mobile UX is clunky or the approval context is insufficient for safe decisions, the user won't trust it.

Evidence: 62% of mobile approvals happen from notification banners without opening the app (competitive analysis — Copilot Remote). 93% auto-approve rate signals approval fatigue.

4

First Review Bottleneck (Scale Proof)

When running 5+ agents, the user hits the review bottleneck. If the diff review UX doesn't help them review faster than raw git diff, parallel agents feel like overhead, not leverage.

Evidence: "The bottleneck shifted from 'AI is too slow' to 'I can only review so fast.'" Flask creator Armin Ronacher limits parallel agents because he can't review fast enough.

5

First Bill (Value Justification)

The moment the credit card charges. If the user can't articulate why they're paying $19/mo instead of using free DIY tools, they cancel. The delta must be visceral: "I literally could not do this before."

Evidence: ICP — "Must be under $30/mo to compete with free alternatives." High individual price sensitivity. DIY is free, T3 Code is free, Emdash is free.

Stage Detail Index

Each lifecycle stage has a dedicated skill for deeper mapping. This overview stays high-level; stage-level detail belongs in these focused docs.

/onboarding-map
Onboarding
Install flow, first agent session, PWA setup, time-to-value optimization
/conversion-map
Conversion
Free tier limits, upgrade triggers, pricing page, payment flow, objection handling
/transaction-map
Transaction
Billing, plan changes, managed devbox add-on, refunds, trust signals
/retention-map
Retention
Daily engagement loops, feature stickiness, churn signals, recovery paths
/expansion-map
Expansion
Solo → team, managed devbox upsell, seat growth, land-and-expand

Journey Gaps

Open questions exposed by journey mapping that need resolution before or during product design.

Gap 1: Approval UX Fidelity on Mobile

How much context can you show on a phone screen for a safe approve/reject decision? No competitor has solved this well. This needs UX exploration — what's the minimum context (action type, risk level, affected files, diff preview) that enables confident decisions without a full terminal view?

Gap 2: "What Happened While I Was Away" Summary

After laptop close → resume, what's the re-entry experience? The Agent Board needs a session recap view: completed tasks, pending approvals, errors, diffs ready for review. No competitor offers this — they all assume continuous presence.

Gap 3: Review Bottleneck Tooling

If the bottleneck is review speed (not agent speed), what does a purpose-built multi-agent diff review flow look like? Batch review across agents? AI-assisted review summaries? Priority ranking by risk? This is a potential differentiator beyond "just show diffs."

Gap 4: Churn Defense Against First-Party Encroachment

Claude Code Channels, Copilot Remote Control, and Codex Mobile all shipped in Q2 2026. If any of these evolve to multi-agent orchestration, the cross-provider gap narrows. The BYO-client + persistence + agent-agnostic combination must be strong enough to retain users who could switch to a single-vendor solution.

Validation Questions

1. Are these the right user journeys?

Five journeys mapped: Scale Past Laptop, Check from Phone, Close Laptop Keep Working, Parallel Sprint, First-Time Setup. Are there missing journeys?

2. Does the lifecycle staging feel right?

Trigger → Discovery → Evaluation → Onboarding → Aha → Conversion → Retention → Expansion → Advocacy → Churn → Recovery

3. Are the critical moments correctly weighted?

Ranked: Setup (#1) → Persistence Proof (#2) → Phone Proof (#3) → Scale Proof (#4) → Value Justification (#5)

4. Which journey gap is the highest risk?

Four gaps identified. Which needs resolution first?

Answer all 4 questions above, then compile your validated decisions.

4 questions remaining
Copied!

Next Steps

Pick one: