ICP — gblock-party SaaS Control Plane

Primary ICP selected from 4 candidates. See Additional ICPs and Cross-ICP Analysis below.
Search log: research/icp-search-log.md

Who they are: Solo software developers, indie hackers, and technical solo founders who run multiple AI coding agents (Claude Code, Codex, OpenCode) on remote infrastructure. They typically have 2-10+ years of development experience and are experienced developers who want to focus on shipping, not infrastructure. Many are building SaaS products, open-source projects, or freelance client work using AI agents as force multipliers.

Budget authority: Single decision-maker. No procurement process. They control their own tooling budget and make purchasing decisions in minutes, not weeks. Typical developer tool spend: $50-200/month across all tools. Sweet spot for a single new tool: $9-29/month.

Discovery channels: Hacker News, Reddit (r/programming, r/SideProject, r/IndieTechnology), X/Twitter dev community, Indie Hackers forum, Dev.to, Medium technical blogs. Word-of-mouth in Discord servers and Slack communities. GitHub trending repos.

Company profile: Solo or 1-3 person company. Pre-revenue to early revenue ($0-50K MRR). Bootstrapped or lightly funded. Often running multiple projects simultaneously.

Business Model & Go-to-Market Motion

Model type: B2B SaaS (PLG) with optional managed IaaS upsell. Evidence: Cursor reached $2B ARR without hiring enterprise sales until $200M+. Developer tools in 2026 overwhelmingly start with PLG — 67% of hybrid PLG+SLG companies hit NRR targets vs. 58% pure-PLG.

Primary motion: Product-led growth. Self-serve signup, free tier or trial, upgrade when value is proven. The buyer and the user are the same person.

Buyer-user relationship: Same person. The developer who evaluates is the developer who buys is the developer who uses daily.

Primary persona: "The Agent Conductor"

What causes someone to start looking NOW — ranked by frequency and urgency:

1. Scaling past 3-5 parallel agents (HIGH frequency, HIGH urgency) — Laptop CPU/RAM caps out. They need remote compute. gblock-party provides it so they never manage it. This is the most common entry point.
2. First mobile need (HIGH frequency, MEDIUM urgency) — They're away from desk and an agent needs approval, or they want to check if a long-running task finished. SSH on phone is intolerable.
3. Session loss from closed laptop (MEDIUM frequency, HIGH urgency) — They lose hours of agent work because their laptop went to sleep or SSH disconnected. They want persistence.
4. Rate limit management (MEDIUM frequency, MEDIUM urgency) — Running 5 agents uses quota 5x faster. They need visibility into which agents are active vs. idle.
5. Reading about the "Agent Conductor" role (MEDIUM frequency, LOW urgency) — Blog posts and trend pieces about developers managing agent teams spark interest in better tooling.
6. T3 Code or Termdock discovery (LOW frequency, MEDIUM urgency) — They find a partial solution but it lacks remote/headless mode or mobile access. They start looking for alternatives.

Current DIY workflow gblock-party eliminates

Step-by-step workflow without gblock-party:

What users say they currently use or have tried, in their own words:

• tmux + SSH + VPS — The dominant DIY solution. "tmux became the runtime for AI agent teams." Works but has no GUI, no mobile, no agent-aware features. Universally used, universally complained about.
• T3 Code — Free, open-source desktop GUI for managing AI coding agents. Session management, git integration, diff viewer. But: no remote/headless mode, no mobile access, desktop-only, Codex primary integration, Claude Code pending.
• Termdock — Electron-based desktop app with GUI-native AI agent monitoring, drag-resize panes. But: desktop-only, no remote, no mobile, $20-200/mo.
• Claude Code Remote Control — Built-in feature (Feb 2026) to control a session from phone. But: requires local machine to stay on, no true persistence, single session only.
• Cursor Agent View — Dashboard for sessions. But: tied to Cursor IDE, not agent-agnostic, no remote/mobile.
• code-server / OpenVSCode Server — VS Code in browser. But: not agent orchestration, just an editor. Users say: "The product is not competing on 'I can open a terminal in a browser.'"
• Ona (formerly Gitpod) — Pivoted to "mission control for agent teams" in Sep 2025. Enterprise-focused, cloud-only, AWS VPC. But: enterprise pricing, no BYO-client, no self-hosted option for individuals.
• Coder — Enterprise CDE platform, self-hosted, Terraform-based. But: enterprise complexity, not designed for AI agent orchestration, requires significant setup.

What users say matters, in their own language:

• "Close the laptop, agents keep running" — Session persistence is the #1 stated value. VPS articles open with this promise.
• "See all my agents in one view" — Unified status dashboard. Every tmux complaint circles back to "I can't see what's happening across sessions."
• "Approve from my phone" — Mobile permission approval. Blog posts describe fire-and-forget workflows where you start agents and check from phone.
• "Like having a co-founder who never sleeps" — AI agents as force multipliers. The value is in parallel throughput, not individual agent quality.
• "Zero setup, just connect" — BYO-client with turnkey managed infrastructure. Users want the workflow without the sysadmin. [BYO-client connectivity needs validation — tools may have hardcoded endpoints or locked inference layers]
• "I need to review diffs before anything gets pushed" — Safety through visibility. T3 Code's diff viewer is specifically mentioned as a key feature.

The "aha moment" as users describe it: "I started 5 agents, closed my laptop, had dinner, checked from my phone — 3 PRs were ready for review."

Post-purchase relationship: Buyer = user = admin. No provisioning complexity. The solo founder connects their existing front-end tool to gblock-party's managed infrastructure, or opens the Agent Board, and starts using it immediately. No onboarding flow needed beyond initial setup.

Self-service everything: Account creation, tool connection, configuration, billing changes, cancellation — all self-serve. Support via docs, Discord, and GitHub issues.

Expansion path: Solo founder hires first engineers → needs team features → upgrades to team tier. This is the natural PLG land-and-expand motion.

How They Find Solutions

• Community discovery: Hacker News "Show HN" posts, Reddit threads about VPS+AI agent setups, X/Twitter threads from developer influencers.
• Blog/tutorial trail: They search "how to run Claude Code on VPS" or "tmux AI agent workflow" and find tutorial posts. Multiple such posts exist (Medium, Dev.to, personal blogs). A product that appears in this search trail captures high-intent users.
• Peer recommendation: Discord servers (AI coding communities), Indie Hackers forum, developer Slack groups.
• GitHub discovery: Trending repos, awesome-lists (awesome-terminals-ai exists), "stars" from followed developers.

How They Evaluate

• Free tier or trial first: Will not pay before trying. Need to see value in under 60 seconds (2026 PLG bar). "Can a user get value in under 60 seconds?"
• Compare against DIY: Is this better than my tmux setup? If not significantly better, they'll stick with free.
• GitHub stars + open-source signal: T3 Code's MIT license and open-source nature is explicitly cited as a strength. Users trust what they can inspect.
• Solo evaluation: No committee. One person decides in minutes to hours, not weeks.

How They Choose

• Mobile access is the tipping point: This is the one thing tmux+SSH cannot provide well. If the product nails mobile, it wins against DIY.
• BYO-client is a must-have: They already use a front-end tool they like. The product must work with their existing tools, not force a new UI. [Connectivity validation needed — see journey-map.md § BYO-Client Integration Landscape]
• Deal-breakers: Vendor lock-in, required public inbound ports, inability to use their own API keys, no CLI/headless mode.
• Price sensitivity: High for individual tool spend. Must be under $30/mo to compete with "free tmux." Value must be obvious.

ICP 2: Small Engineering Teams (2-15 developers) Priority #2

Customer Profile

Who: Early-stage startups and small SaaS companies with 2-15 developers. Engineering-led organizations where the CTO or engineering lead makes tooling decisions. Series A/B stage or bootstrapped with revenue.

Budget authority: Engineering lead or CTO. $1K-5K/month developer tools budget. Decision process: engineer champions the tool, lead approves after seeing usage data.

Business Model & Go-to-Market Motion

PLG land-and-expand. Individual developer signs up free, team adopts when 2+ devs are using it, lead approves team billing. Expansion from $29/seat/mo.

User Profile(s)

Individual developers on the team use it for their own agent workflows, plus the engineering lead wants visibility into team-wide agent activity: who's running what, which repos are being modified, aggregate resource usage.

Trigger Events

1. Team scales past 3-5 developers — Can no longer casually coordinate who's running agents on what repos
2. Agent conflict incident — Two developers' agents modify the same files, causing merge conflicts or regressions
3. New developer onboarding — Need to give new hire access to shared dev infrastructure without giving root SSH access

Current State Journey

Each developer manages their own agent sessions independently. No shared visibility. Coordination via Slack messages ("I'm running agents on the API repo, don't push to main"). No centralized audit of what agents are doing.

Pain Map

Current Alternatives (User Perspective)

Slack coordination ("don't touch the API repo"), individual tmux setups, Coder (too enterprise/complex), nothing purpose-built.

Market Sizing

~4.2M small teams worldwide (companies with 2-50 developers). SME developer tools segment growing at 28.2% CAGR. At $49/seat/mo average, 5 seats: ~$2.9K/yr per team.

Stated Value Drivers

"See what everyone's agents are doing." "Stop stepping on each other's toes." "Onboard new devs without giving SSH access."

Customer ↔ User Dynamics

Buyer (eng lead/CTO) and users (individual devs) are different. Lead cares about visibility and governance; devs care about UX and not losing their workflow.

Discovery & Evaluation Behavior

Individual developer discovers via same channels as ICP 1. Champions to team lead. Lead evaluates on: team visibility, security, pricing per seat. Trial period: 2-4 weeks of team usage before committing.

ICP 3: Freelancers / Agency Developers Priority #3

Customer Profile

Who: Freelance developers and small dev agencies (2-5 people) managing 3-8 client projects simultaneously. Technically skilled, budget-conscious, value efficiency over features.

Budget authority: Self (freelancer) or agency owner. $10-50/month typical tool spend per tool. Highly price-sensitive — every dollar must show ROI.

User Profile(s)

Freelancer running AI agents across multiple client repos. Needs strict project isolation (Client A's code must never leak into Client B's agent context). Mobile monitoring between client meetings.

Trigger Events

1. Taking on 4+ concurrent clients — Can't keep track of agents across projects
2. Client confidentiality concern — Needs to prove code isolation between clients
3. Between-meeting monitoring — Starts agents before a meeting, wants to check results on phone after

Pain Map

Current Alternatives (User Perspective)

Separate tmux sessions per client, manual directory switching, no isolation guarantees. Project management tools (ClickUp, Notion) for task tracking but not agent orchestration.

Market Sizing

~12M freelance developers globally. Of those using AI tools (~85% = 10.2M), subset running parallel agents across clients is smaller (~5-10% = 510K-1M). At $19/mo: $116M-$228M.

Stated Value Drivers

"Keep client projects completely separate." "Check on all my agents between meetings." "Handle 40% more clients without stress."

Discovery & Evaluation Behavior

Freelancer platforms (Upwork, Contra), freelancer communities, word-of-mouth. Evaluate on: price, setup speed, client isolation. Must have free tier.

ICP 4: Security-Conscious Developers Priority #4

Customer Profile

Who: Developers and small security teams at companies handling sensitive data (fintech, healthcare, govtech). Need governance around AI agent access to codebases.

Budget authority: CISO or engineering director. Longer procurement (1-3 months). Higher willingness to pay ($50-200/seat/mo) but requires compliance checkboxes.

User Profile(s)

Security-aware developers who want guardrails: no public ports, audit trails of agent actions, permission policies, secrets management. Enterprise DevSecOps practitioners.

Trigger Events

1. Security audit flags AI tool usage — "65% of enterprises worry about data leakage from AI tools"
2. Compliance requirement — SOC 2, HIPAA, or internal policy mandates governed AI tool access
3. Agent security incident — Agent accidentally exposes secrets, writes to production, or runs destructive commands

Pain Map

Current Alternatives (User Perspective)

Coder (enterprise, self-hosted, $$$), Ona (enterprise, cloud-only, AWS VPC), manual SSH lockdowns, "just don't use AI agents" (policy-level ban).

Market Sizing

~500K security-focused development teams globally. At enterprise ARPU ($100/seat/mo, 10 seats): $6B TAM for governed AI dev environments. But: highly competitive (Coder, Ona, cloud providers).

Stated Value Drivers

"Zero public inbound ports." "Audit trail for every agent action." "Permission policies per project." "Pass the SOC 2 audit."

Discovery & Evaluation Behavior

Analyst reports (Gartner), security conference talks, peer CISO recommendations, compliance vendor shortlists. Long evaluation with POC required. Security is the feature that gets you on the shortlist, not the feature that wins the deal.

Prioritization Matrix

Shared Pain Points

• No unified multi-agent visibility — All 4 ICPs. This is the universal pain.
• Session fragility / no persistence — ICPs 1, 2, 3. Close the laptop, lose the work.
• No mobile access — ICPs 1, 2, 3. SSH on phone is universally painful.
• Permission approval requires desk presence — ICPs 1, 3, 4. Agents stuck waiting for human who isn't there.

Conflicts & Trade-offs

• Simplicity vs. governance: Solo founders want minimal config, zero ceremony. Security-conscious users want RBAC, audit trails, policies. Building for both simultaneously risks satisfying neither.
• BYO-client vs. Agent Board only: Solo founders already use a front-end tool and want to connect it. Security users may prefer the managed Agent Board for compliance. Different onboarding flows.
• Single-tenant vs. multi-tenant on host: Freelancers need per-client isolation on a single host. Solo founders want multi-repo on one host. Similar but different isolation models.
• Pricing tension: Solo founders are price-sensitive ($9-29/mo). Enterprise buyers expect $50-200/seat/mo. Team tier needs to bridge the gap.

Product Line Recommendations

Recommended Build Sequence

1. Power Users / Solo Founders (NOW) — You are this ICP. Dogfood validates everything. Build the core: Agent Board + Terminal + BYO-client + managed infrastructure + mobile access. PLG self-serve. [BYO-client connectivity validation is prerequisite — experimentation needed]
2. Small Engineering Teams (NEXT, +3-6 months) — Add shared visibility, basic RBAC, team billing. Natural expansion from solo → team via PLG land-and-expand.
3. Freelancers / Agency Devs (THEN, +6-9 months) — Add per-client workspace isolation, project-scoped sessions. Marketing pivot, not major product pivot.
4. Security-Conscious / Enterprise (LATER, +12-18 months) — Add audit trails, SSO, compliance. Aligns with Phase 5-6 from concept brief.

Discovery & Evaluation Comparison

Pick one:

• /competitive-analysis — Research competitors (T3 Code, Ona, Termdock, Coder, Cursor Agent View) and map market gaps for this ICP
• /spec-interview — Design the solution for this ICP's pain points (no specs directory exists yet)

Raw signals captured during research. These are unvalidated observations — use the linked skill to verify, validate, and explore alternatives.

→ /competitive-analysis

• Direct competitors mentioned by users: T3 Code, Termdock, Ona (Gitpod), Coder, Claude Code Remote Control, Cursor Agent View
• Tools users compare: tmux vs. Termdock vs. T3 Code; Coder vs. Codespaces vs. Gitpod/Ona
• Stated alternatives: "tmux works," "I just SSH in," "code-server covers the IDE part"
• Category validation: Gitpod pivoted to Ona (agent orchestration) in Sep 2025 — validates category

→ /positioning

• Value language users use: "Close the laptop, agents keep running," "see all my agents in one view," "approve from my phone"
• Differentiation claim: "Not competing on 'I can open a terminal in a browser.' Competing on 'I can run 10 coding agents safely, monitor from phone, approve risky actions.'"
• Problem description: "tmux became the runtime for AI agent teams" — accidental infrastructure, not purpose-built

→ /monetization

• Budget signals: $9-29/mo sweet spot for individual dev tools. Cursor at $20/mo, $2B ARR
• Pricing sensitivity: "Must be under $30/mo to compete with free tmux." High individual price sensitivity.
• Cost of alternatives: tmux is free. T3 Code is free (open source). Termdock $20-200/mo. Codespaces $0.36/hr.
• Usage-based shift: Vendors shifting from seat-based to usage-based pricing for agentic workflows

→ /gtm

• Where users search: "how to run Claude Code on VPS," "tmux AI agent workflow," "AI coding agent mobile access"
• Communities: HN, Reddit r/programming, Indie Hackers, Dev.to, X dev community, Discord AI coding servers
• Peer recommendation patterns: Blog posts are the primary discovery channel. Show HN posts drive awareness. GitHub stars signal trust.
• PLG benchmark: Cursor didn't hire enterprise sales until $200M+ ARR. Developer tools are PLG-first.

One row per major ICP claim — each segment, each top pain, each value prop, and the prioritization call — with the source/repo evidence behind it, the inference made, confidence, assumption status, and what the claim drives.

Load-bearing conclusions and assumptions, with their evidence status, confidence, and what would change them. Folds in the key assumptions and research gaps surfaced during the analysis.