Moore Positioning Hypothesis
Geoffrey Moore "Crossing the Chasm" positioning template for gblock-party
Sources: research/icp.md, research/competitive-analysis.md, research/positioning-jtbd.md, research/positioning-strategic-canvas.md
Step 3 of 4 in Positioning Framework Execution · Review state
Primary Positioning Hypothesis
For solo developers and technical founders running multiple AI coding agents on remote infrastructure
who need their agents to keep working when they step away from their desk and want to monitor and control them from any device
gblock-party is an always-on agent workstation
that provides persistent AI agents — sessions that survive across devices, a unified status dashboard, and smart approval routing
Unlike the DIY stack of tmux + SSH + VPS (the primary alternative) and vendor-locked cloud agents (Cursor, Codex)
our product combines managed infrastructure with BYO-client flexibility [BYO-client connectivity needs validation] — your agents never stop, you control them from any device, and you use your own tools.
Element Breakdown
| Element | Content | Evidence Source | Confidence |
|---|---|---|---|
| Target customers | Solo developers and technical founders running multiple AI coding agents on remote infrastructure | ICP primary persona: "The Agent Conductor" — solo developer or technical founder using 2–4 AI coding tools simultaneously. Ranked 18/20 combined score, #1 of 4 ICPs. Budget authority: single decision-maker, no procurement process. | High |
| Statement of need | Need agents to keep working when they step away; monitor and control from any device | ICP #1 stated desire: "Close the laptop, pick up where I left off." #2 value driver: "See all my agents in one view." #3: "Approve from my phone." JTBD primary job statement validated. Journey Map aha moment: "closed laptop, checked from phone, 3 PRs ready." | High |
| Market category | Always-on agent workstation | Strategic Canvas category analysis: "Not an IDE/ADE, not a CDE, not an agent framework, not a mobile companion app." Competitive Analysis gap validated. Search term research resolved label: "always-on" maps to user language ("running 24/7", "keep running"), "agent" avoids GPU infra confusion, "workstation" unclaimed and developer-native. Closest parallel: Coder (enterprise CDE control plane), but for solo developers. | Medium-High |
| Key benefit | Always-on infrastructure with session persistence, unified status dashboard, and smart approval routing | JTBD functional dimensions: session persistence (Unique), unified multi-agent visibility (Unique), smart approval routing (Unique). Strategic Canvas Create factors: Session Persistence as a Standard, Cross-Device Session Continuity, Smart Approval Routing. These are the three dimensions where gblock-party diverges most sharply from all competitors. | High |
| Competitive alternative | DIY tmux + SSH + VPS stack, and vendor-locked cloud agents (Cursor, Codex) | ICP Current Alternatives: "tmux + SSH + VPS — the dominant DIY solution. Works but has no GUI, no mobile, no agent-aware features. Universally used, universally complained about." JTBD positioning: "DIY (VPS + tmux) is the primary alternative, not other tools." Cursor and Codex cited as the only persistence alternatives, but both vendor-locked. | High |
| Primary differentiation | Managed infrastructure + BYO-client flexibility — agents never stop, control from any device, use your own tools | Strategic Canvas: "The 'Managed BYO-Client' gap — DIY gives BYO-client but not managed. Cursor gives managed but not BYO-client. Nobody gives both." Competitive Analysis: "No product combines BYO-client + managed infrastructure + multi-agent + mobile + zero-inbound." JTBD positioning formula: "Your agents never stop. Monitor from any device. Approve from any device. Use your own tools." | High |
Gate: Positioning Hypothesis Approval
Does this positioning hypothesis accurately capture gblock-party's target customer, need, category, benefit, competitive frame, and differentiation?
Decision: Positioning Hypothesis
Answer: Approved
Date: 2026-06-04
Hypothesis accepted as-is. All six elements (target customer, need, category, benefit, competitive frame, differentiation) are accurate and ready for artifact.
Evidence Mapping
Each element of the positioning hypothesis classified by evidence status. Evidenced = directly supported by research data. Hypothesized = reasonable inference from evidence, not directly observed. Unvalidated = assumed, needs testing.
| Element | Status | Evidence Summary | Key Citations |
|---|---|---|---|
| Target: Solo devs / technical founders | Evidenced | ICP research identified 4 candidate ICPs and scored Power Users / Solo Founders at 18/20 (highest). Profile validated against VPS tutorial ecosystem, community behavior patterns, and budget authority analysis. The developer who evaluates = buys = uses daily. | research/icp.md § Customer Profile, Prioritization Matrix (9/10 value, 9/10 accessibility) |
| Need: Agents keep working when away; control from any device | Evidenced | "Close the laptop, pick up where I left off" cited unprompted across multiple VPS+agent articles and ICP interviews. Aha moment quote validated in journey map. Mobile access is #3 value driver. Trigger events #1 (scaling agents) and #2 (first mobile need) directly map. | research/icp.md § Stated Value Drivers; research/positioning-jtbd.md § Primary Job Statement; research/journey-map.md Critical Moments #2, #3 |
| Category: Always-on agent workstation | Research-backed | Resolved through search term research: "always-on" maps to user language ("running 24/7", "keep running", "while you sleep"), "agent" is more precise than "AI" (avoids GPU infra market confusion), "workstation" is unclaimed, developer-native, and carries always-on connotation. Strategic Canvas confirmed no existing category fits. Category-creation move (Play Bigger). | research/positioning-strategic-canvas.md § Category Impact; research/competitive-analysis.md § Gap 1; search term research (2026-06-04) |
| Benefit: Always-on + persistence + dashboard + smart approvals | Evidenced | Each benefit maps to a JTBD functional dimension rated "Unique" (no competitor on managed infra with BYO-client). Session persistence = #1 desire. Unified visibility = #2 value driver. Smart approvals = validated by Copilot Remote GA (62% approve from banners). Strategic Canvas Create factors confirm these as new value dimensions. | research/positioning-jtbd.md § Functional Dimensions; research/positioning-strategic-canvas.md § Create; research/competitive-analysis.md § Copilot Remote |
| Alternative: DIY tmux + vendor-locked cloud | Evidenced | tmux+SSH+VPS is "the dominant DIY solution" per ICP research. "Universally used, universally complained about." 10+ tutorials exist for this workflow (QuantVPS, Hostinger, Medium, GitHub). Cursor cloud agents and Codex cloud are the only persistence alternatives, both vendor-locked and single-agent. JTBD explicitly recommends positioning against DIY, not other tools. | research/icp.md § Current Alternatives; research/competitive-analysis.md § Gap 2; research/positioning-jtbd.md § Positioning Around Job Outcome |
| Differentiation: Managed infra + BYO-client | Evidenced / Hypothesized | The competitive gap is evidenced: feature matrix of 27 competitors confirms no product combines all 5 dimensions (BYO-client, managed infra, multi-agent, mobile, zero-inbound). Front-end commoditization is observed (5+ OSS tools). BYO-client integration paths analyzed (3 of 5 priority targets support config-driven backend replacement). Hypothesized: whether "managed + BYO-client" as a combined phrase resonates with users and drives purchase decisions is untested. | research/competitive-analysis.md § Market Gaps, Feature Matrix, Pluggable Frontend Model; research/positioning-strategic-canvas.md § Managed BYO-Client gap |
Gate: Evidence Sufficiency
Is the evidence base sufficient to support this positioning hypothesis, or are there critical gaps that should be filled before committing?
Decision: Evidence Sufficiency
Answer: Sufficient
Date: 2026-06-04
Evidence base adequately supports the positioning hypothesis. Market category label remains the known gap, deferred to Step 4.
Weakest Link Analysis
Resolved: Market Category
"Always-on agent workstation"
Why This Was the Weakest Link
Every other element of the positioning hypothesis was grounded in direct evidence: users describe the target customer (themselves), articulate the need ("close the laptop, pick up where I left off"), name the competitive alternatives (tmux, Cursor), and validate the differentiation gap (no product combines managed infra + BYO-client). The market category was a synthesis — an analytical conclusion that no existing category fits. Search term research (2026-06-04) resolved this by validating each word choice against user language and competitive landscape.
- Resolved: "Always-on" maps to user search language. Users search for "running 24/7", "keep running", "while you sleep" — "always-on" captures this intent directly. The old term "managed" was architecture jargon users never search for.
- Resolved: "Agent" avoids GPU infrastructure confusion. "AI" pulls the category toward the $142B GPU infra market (CoreWeave, Lambda, AWS). "Agent" is more precise and maps to how users describe their coding assistants.
- Resolved: "Workstation" is unclaimed and developer-native. No competitor claims this term. It carries connotations of personal, always-on, professional tooling. Category-creation move (Play Bigger) with lower education cost than "control plane."
- Remaining risk: user language testing outstanding. The label is research-backed but not yet validated through direct user testing. Confidence upgraded from Medium to Medium-High, not High.
What Changes If This Element Is Wrong
| If the category is wrong... | Impact on positioning |
|---|---|
| Users think of gblock-party as a "remote development tool" or "agent dashboard" | Positioning gets pulled into existing categories where competitors are entrenched (Codespaces, Replit, T3 Code). Differentiation message weakens. |
| The term "control plane" doesn't resonate with solo developers | Marketing language needs to be benefit-led ("your agents never stop") rather than category-led. The category becomes implicit, not the headline. This may actually be the safer default. |
| A competitor claims the category first with a different name | gblock-party must either adopt that name or invest in category creation. First-mover advantage on naming is real but fragile. |
What Evidence Would Strengthen It
- User language testing: Present 3–5 category labels to target users and measure which one they immediately understand and associate with gblock-party's value. Options might include: "agent control plane," "agent infrastructure," "agent runtime," "remote agent platform," "always-on agent manager."
- Search behavior analysis: (Done — 2026-06-04.) Search term research analyzed user language, competitor labels, and term viability. Resolved "always-on agent workstation" as the category label. Each word choice validated against search patterns and competitive landscape.
- Analyst / journalist framing: How do third parties describe this space? If they use a consistent term, adopting it is lower-risk than creating a new one.
- Competitive category claims: Monitor how Emdash, Multica, and Grass self-describe. If one gains traction with a category label, evaluate whether to adopt or differentiate.
Gate: Market Category Choice
The market category "managed AI agent orchestration control plane" is the weakest element. How should we handle it?
Decision: Market Category
Answer: Resolved — always-on agent workstation
Date: 2026-06-04
Search term research validated each word choice: "always-on" maps to user language ("running 24/7", "keep running", "while you sleep"); "agent" avoids GPU infra market confusion ($142B, CoreWeave/Lambda/AWS); "workstation" is unclaimed, developer-native, and carries always-on connotation. Category-creation move. Confidence: Medium-High (research-backed, pending direct user language testing).
Alternative Hypotheses
Two alternative positioning hypotheses that use different target customers, market categories, or competitive frames. The primary hypothesis is preferred for reasons explained below each alternative.
Alternative A: "Mobile-First Agent Dashboard" Positioning
For developers running AI coding agents who are frustrated by being chained to their desk
who want to check on their agents and approve risky actions from their phone
gblock-party is a mobile agent dashboard
that gives you push notifications, one-tap approvals, and a unified status view for all your agents from any device
Unlike Copilot Remote Control and Claude Code Remote (single-agent, single-provider mobile tools)
our product works with every AI coding agent and provides always-on visibility without requiring your laptop to stay on.
What This Gets Right
- User-facing pain is the headline. "Check from your phone" is how users describe the desire, not "managed control plane." Leads with the experience, not the architecture.
- Clean competitive frame. Copilot Remote and Claude Code Remote are known entities. Positioning against them is concrete and testable.
- Narrower, sharper. A "mobile agent dashboard" is immediately understandable. No category creation required.
Why Primary Is Preferred
- Reduces the product to one feature. Mobile is the conversion trigger (vs. free DIY), but the product's durable value is the managed infrastructure underneath. Positioning as a "mobile dashboard" invites feature-parity competition from first-party mobile tools (Claude Channels, Codex Mobile) that could ship multi-agent support.
- Misses the BYO-client story. The mobile dashboard framing implies gblock-party IS the UI. The primary hypothesis positions gblock-party as infrastructure that any UI can connect to. BYO-client is a must-have per ICP research and a strategic moat (front-end commoditization).
- Undervalues the infrastructure moat. Strategic Canvas shows front-end UI is commoditizing. Durable value = managed infrastructure. A mobile dashboard is a client for the infrastructure, not the product itself.
- Smaller addressable framing. "Mobile dashboard" positions against mobile tools only. "Control plane" positions against the entire DIY workflow, capturing infrastructure + monitoring + mobile + security.
Alternative B: "Turnkey Agent Infrastructure" Positioning
For solo developers and small teams who run AI coding agents on VPS infrastructure
who are tired of the 10-step DIY setup process and ongoing sysadmin overhead
gblock-party is a managed agent infrastructure platform
that replaces your VPS + tmux + Tailscale stack with turnkey, always-on infrastructure you connect your existing tools to
Unlike DIY VPS setups (manual, fragile) and Coder (enterprise-only, complex)
our product gives solo developers enterprise-grade agent infrastructure without the enterprise complexity or price.
What This Gets Right
- Infrastructure-first, which matches the strategic thesis. Strategic Canvas, competitive analysis, and JTBD all conclude the durable moat is infrastructure, not UI. This positioning leads with that insight.
- BYO-client is explicit. "Connect your existing tools" is front and center. Matches the ICP must-have and the front-end commoditization thesis.
- Clear competitive frame against DIY. Positions against the actual primary alternative (VPS + tmux), not against other tools. Aligns with JTBD recommendation.
Why Primary Is Preferred
- Leads with mechanism, not outcome. "Managed infrastructure" is what we build; "your agents never stop" is what users buy. The primary hypothesis includes managed infrastructure as a differentiation point, not the headline benefit. Users search for "how to keep agents running," not "managed infrastructure."
- Misses the emotional hook. JTBD emotional dimensions show relief from desk-tethering and delight at the aha moment ("closed laptop, checked from phone, 3 PRs ready"). Infrastructure positioning is rational, not emotional. The primary hypothesis captures both.
- "Enterprise-grade for solo devs" is a risky frame. It can read as either aspirational (good) or overkill (bad). Solo developers may hear "enterprise" and think "complex, expensive, not for me" — the opposite of the intended message.
Gate: Competitive Frame
The primary hypothesis positions against both DIY (tmux+VPS) and vendor-locked cloud (Cursor, Codex). Is this dual competitive frame correct?
Decision: Competitive Frame
Answer: Dual frame correct
Date: 2026-06-04
Both DIY (tmux+VPS) and vendor-locked cloud (Cursor, Codex) are real alternatives users consider. Research findings added:
Search Term & Category Research
"AI Cloud Infrastructure" is not viable — the term is claimed by the GPU/training infrastructure market ($142B, dominated by AWS/Azure/CoreWeave). Using it would cause category confusion.
User search language is problem-oriented, not category-oriented:
| Search Pattern | Signal | Viability for gblock-party |
|---|---|---|
| "Run Claude Code in the cloud 24/7" | Problem-oriented, persistence need | High |
| "Keep Claude Code running 24/7" | Always-on desire, matches benefit headline | High |
| "Claude Code VPS setup" / "best VPS for persistent sessions" | DIY infrastructure search | High |
| "Keep agents running after SSH disconnects (tmux guide)" | Pain-point search, DIY workaround | High |
| "Monitor Claude Code from your phone" | Mobile access desire | High |
| "Background agents for developers" | Emerging term (Cursor uses it) | Medium |
| "AI cloud infrastructure" | Claimed by GPU/training market | Not viable |
Analogous product positioning patterns (Vercel, Railway, Fly.io, Render, Coder):
- All frame against DIY complexity, not specific competitors
- Formula: "The [adjective] cloud for [audience verb]"
- Power word is "without" — what disappears when you use the product
- Coder is closest structural analog (control plane for dev environments, recently pivoted to "AI Workflow Infrastructure")
Strongest unclaimed positioning angles for Step 4:
- "Always-on AI agents" — mirrors user language, no product owns it
- "Managed infrastructure for AI coding agents" — follows Vercel/Railway pattern
- "The cloud for AI agent sessions" — clean, descriptive
Evidence Matrix
| Claim | Source | Evidence Type | Confidence |
|---|---|---|---|
| Solo devs / technical founders are the right launch ICP | research/icp.md — 4-ICP evaluation, prioritization matrix | Observed + Scored | High |
| "Close the laptop, pick up where I left off" is the #1 stated desire | research/icp.md, research/positioning-jtbd.md | Observed (user language) | High |
| No competitor combines BYO-client + managed infra + multi-agent + mobile + zero-inbound | research/competitive-analysis.md — 27-competitor feature matrix | Observed | High |
| tmux + SSH + VPS is the dominant alternative, universally complained about | research/icp.md § Current Alternatives | Observed (user language) | High |
| Front-end agent UI is commoditizing (5+ OSS tools, all free) | research/competitive-analysis.md § Frontend Commoditization | Observed (market analysis) | High |
| BYO-client is a must-have; vendor lock-in is a deal-breaker | research/icp.md § Deal-breakers | Observed (user language) | High |
| "Always-on agent workstation" is the right category label | research/positioning-strategic-canvas.md § Category Impact; search term research (2026-06-04) | Research-backed | Medium-High |
| The dual competitive frame (DIY + vendor-locked) is correct | research/positioning-jtbd.md § Positioning Around Job Outcome; research/competitive-analysis.md § Gaps 1–2 | Inferred (synthesis) | High |
| Users will pay $9–29/mo for managed orchestration vs. free DIY | research/icp.md § Budget authority | Hypothesized | Low |
| The combination of dimensions (not any single one) is the positioning | research/positioning-jtbd.md § Positioning Implication; research/positioning-strategic-canvas.md § Divergence Points | Inferred (cross-validated) | High |
| "Your agents never stop" is the right benefit headline | research/positioning-jtbd.md § Positioning formula; ICP aha moment | Inferred (user language synthesis) | Medium |
| BYO-client integration paths exist for 3 of 5 priority targets | research/competitive-analysis.md § Pluggable Frontend Model | Observed (code/architecture analysis) | High |
Confidence & Assumption Register
| Assumption | Status | Confidence | What Would Change It |
|---|---|---|---|
| The Moore template captures gblock-party's positioning accurately | Evidence-backed | High | User testing showing the positioning statement doesn't resonate or is confusing |
| Target customer is correctly scoped (solo devs, not teams/enterprise) | Evidence-backed | High | Early adopters turning out to be small teams, not solo devs; or solo dev market too small to sustain |
| The need statement captures the primary hiring reason | Evidence-backed | High | User interviews showing a different primary need (e.g., cost savings, agent quality, not mobility) |
| "Always-on agent workstation" is the right category | Research-backed | Medium-High | User language testing showing "workstation" confuses or doesn't resonate; a competitor claiming the category with a different name that sticks |
| DIY tmux is the primary competitive alternative, not other tools | Evidence-backed | High | A direct competitor (Emdash, Multica, Nimbalyst) gaining significant traction and becoming the reference point |
| The managed + BYO-client combination is the durable differentiator | Evidence-backed | High | A competitor shipping managed infrastructure with BYO-client flexibility; or BYO-client proving unnecessary (users preferring an integrated UI) |
| Benefit-led messaging ("your agents never stop") is better than category-led | Hypothesized | Medium | A/B testing showing category-led messaging drives more signups; or the category label becoming well-known enough to lead with |
| Willingness to pay $9–29/mo for managed orchestration | Unvalidated | Low | Price-point testing with real users; conversion data from free tier to paid |
Gate: Artifact Destination
If approved, this analysis will be written to research/positioning-moore.md. Confirm the destination.
Decision: Artifact Destination
Answer: Confirmed
Date: 2026-06-04
Write to research/positioning-moore.md.
Compile Review
Use Compile Feedback to send concerns or clarification requests before answering every gate, or Compile Answers for final approval once all required gate questions are answered. The compiled YAML always includes any optional section feedback you set.