ICP Alignment

Primary ICP: Gamer Indie Builders

Solo devs and indie hackers who play RimWorld, Factorio, and Dwarf Fortress — and build software in evening/weekend sessions.

B2C Premium Indie Game Steam PLG $24.99–$29.99 EA 4 candidates scored
~32
Average Age
55%
Work Solo
84%
Use AI Coding Tools
34%
RimWorld-Factorio Overlap
Who We're Building For

User Profiles

☾
The Evening Builder
Primary — Solo dev with a day job, codes side projects in 1–3hr sessions
High technical sophistication. Comfortable with Git, CLI, TypeScript/Python. Uses VS Code or Cursor daily. Knows what good code looks like but can't always write it for side projects.
Goals
  • Feel genuine progress despite limited time
  • Ship something real, not just accumulate repos
  • Maintain quality without cognitive overhead
  • Experience emotional satisfaction of building
RimWorld Factorio Cursor Side Projects Evening Sessions
☼
The Weekend Tinkerer
Secondary — Codes recreationally, treats programming as a hobby alongside gaming
Moderate-to-high technical skill. May be junior at work but deeply engaged with programming as craft. Wants the act of coding to feel rewarding in itself.
Goals
  • Make coding feel like play, not work
  • Explore ideas without maintenance burden
  • See visible results quickly
Dwarf Fortress Slay the Spire Hobby Coder Weekends
What Hurts

Pain Map

Pain Point Severity Frequency Current Workaround
Context loss between sessions Critical Every session Git log, TODO comments, personal notes (all fragile)
Project abandonment cycle Critical Monthly Start new projects instead of finishing (makes it worse)
AI tools increase cognitive load High Daily Accept lower quality or do it manually
Side projects feel like work, not play High Every session Gamify with habit trackers (doesn't work)
No visible progress or reward High Weekly GitHub contribution graph (weak signal)
No emotional connection to building High Chronic Play actual games instead of coding
Tool fragmentation Medium Weekly Consolidate to one tool, lose capabilities
Code review is lonely Medium Every commit Skip review or rubber-duck with AI chat
Without Bismarck

Current State Journey

1
Session Start
5–15 min
Open VS Code/Cursor. Try to remember where they left off. Read git log, scan TODO comments. Context is fragmented across tools.
2
Planning
5–10 min
Decide what to work on. Often pick something easy instead of what matters, because planning overhead is too high for a short session.
3
Coding
30–90 min
Write code with AI autocomplete. For complex tasks, spend more time evaluating AI suggestions than writing from scratch. Alt-tab between docs, Stack Overflow, AI chat.
4
Review & Testing
10–20 min
Run tests if they exist. Manual QA. No structured review — they're the only reviewer. Quality depends on how tired they are.
5
Commit & Context Dump
5 min
Commit with a message that will make no sense in a week. Close laptop. Context is lost.
6
Between Sessions
Days to weeks
Project sits untouched. Motivation decays. The longer the gap, the harder it is to return.
7
Abandonment
Eventual
After 2–3 failed re-entry attempts, the project joins the graveyard. Developer feels guilt and diminished motivation for the next idea.
What Brings Them In

Trigger Events

1
New AI coding tool launch / hype cycle
HIGH frequency · MEDIUM urgency
Every major AI tool release triggers devs trying new workflow approaches. Bismarck enters as "what if the AI interface was a game?"
2
Side project abandonment moment
HIGH frequency · HIGH urgency
The moment a dev opens a project untouched for 2 weeks and feels the dread of lost context. Actively searching for something to make coding rewarding.
3
Colony sim game discovery
MEDIUM frequency · LOW urgency
Player finishes a RimWorld/Factorio session and browses Steam for something new. Bismarck appears in the colony sim tag with a novel twist.
4
Developer burnout from day job
MEDIUM frequency · HIGH urgency
After a draining sprint, dev seeks something that makes coding feel meaningful. Colony sim frame makes side projects feel like play.
5
Steam Next Fest / seasonal sale
LOW frequency · HIGH conversion
Concentrated discovery events. Demo availability is critical.
6
Dev streamer recommendation
LOW frequency · HIGH trust
Trusted dev YouTuber/streamer plays Bismarck. High conversion because audience self-selects for developer-gamers.
Why We Win

Value Proposition

“Build your software as a living colony — command AI agents, watch real code take shape, and ship from a world that remembers every decision.”
Every AI coding tool asks “how can we help you write code faster?” Bismarck asks “how can we make building software feel like commanding a frontier colony?” The wedge is emotional, not functional.
Step 1
Player issues a Work Order to build a new feature
Step 2
Named colonist (AI agent) walks to worksite and begins coding
Step 3
Agent produces a real pull request; player reviews it in-game
Step 4
Player approves — colony map changes to reflect shipped code
⚔
Command
Guilt → "I want to play my colony"
▶
Momentum
Colony grows with every shipped feature
⚙
Craft
Review is a game mechanic, not a chore
The Gap

Market Landscape

No product combines real AI-agent-driven software development with the emotional loop of a colony sim. Every AI coding tool is productivity-framed. Every coding game uses fake development.

Cursor $20/mo
Dominant AI IDE, $500M+ ARR. Best inline completions but no emotional layer.
No game layer
GitHub Copilot $19/mo
Widest adoption but falling behind on complex tasks. GPT-4o backend.
No game layer
Game Dev Tycoon $9.99
94% positive, 22K reviews. Simulates game studio but uses fake development.
No real code
Screeps $14.99
MMO with real JavaScript coding. Competitive multiplayer, not colony sim loop.
No colony sim
COMPARABLE GAMES (emotional/mechanical reference)
RimWorld
$34.99
97% · 232K reviews
Reference
Factorio
$35.00
98% · 115K reviews
Reference
Against the Storm
$29.99
95% · 18K reviews
Reference
Timberborn
$24.99
95% · 37K reviews
Reference
How Big

Market Sizing

TAM
~$108M
3.6M players × $29.99
SAM
$15–30M
500K–1M active seekers
SOM
$150K–600K
5K–20K units Y1
Confidence: Rough extrapolation. Colony sim genre size and pricing well-evidenced. Developer-gamer intersection is novel with no direct precedent.
Top-down check: Timberborn ~1M+ sales at 1.0. Against the Storm ~450K+ sales. A novel colony sim capturing 1% of genre = 80–120K sales = $2.4–3.6M.
How They Buy

Acquisition & Conversion Funnel

Awareness
Steam Discovery Queue, Next Fest, Reddit, streamer video
Risk: AI-coding angle confuses colony sim fans
Interest
Store page, trailer, reviews — 1–5 minutes
Risk: "Is this a game or a dev tool?"
Evaluation
Plays Steam demo — 15–30 minutes
Risk: Demo fails to deliver aha moment within 5 min
Decision & Purchase
Wishlist or buy at $24.99–$29.99 EA — seconds to days
Onboarding
Demo mode with sample project — 30–60 minutes
Risk: Mechanics confusing, colony sim expectations not met
Activation
Connect GitHub repo, issue first real Work Order — 1–2 hours
Risk: GitHub OAuth friction, AI agent output disappointing
Motion: PLG via Steam. Self-serve. No sales team. Cycle: Days. Comparable titles (RimWorld, Factorio, Against the Storm) all use this exact motion.
All 4 Candidates

ICP Prioritization Matrix

ICP Value Accessibility Combined Rationale
A: Gamer Indie Builders 9/10
8/10
17 Game framing IS the value. Steam proven. Short cycle.
B: Vibe Coders 7/10
4/10
11 Large market but game framing is friction. Different GTM needed.
C: AI-Curious Solo Founders 6/10
5/10
11 Overlaps A but game frame risks feeling frivolous.
D: Dev Content Creators 4/10
6/10
10 Tiny segment. Better as amplification channel for A.
Cross-ICP

Shared Pain Points

⚠
Loss of meaning in coding work
Affects: A (abandoned projects) · B (can't evaluate quality) · C (tool fragmentation) · D (boring streams)
Bismarck's emotional loop (command, momentum, craft) addresses this across all segments.
🔒
AI trust gap
Affects: A, B, C, D — 84% adopt AI tools but lack confidence in output
Colony sim review mechanic (ship / send back / revise scope) provides oversight through play, not process.
🕑
Context loss between sessions
Affects: A, C, D — solo developers and creators struggle with re-entry
Colony state provides visual context that text-based tools can't match.

Conflicts & Trade-offs

A vs B: Game depth vs. simplicity
Gamer Indie Builders want RimWorld-level systems depth. Vibe Coders want simple interfaces without game literacy. Serving both dilutes the core.
Resolution: Build for A. Simplified mode for B can come later.
A vs C: Game-first vs. productivity-first
Gamers love the colony sim framing. Founders may see it as a toy that adds overhead. The game must be fun AND produce real output.
Resolution: If it does both, C converts naturally. If it's only fun, C bounces.
Steam vs. web distribution
A lives on Steam. B and C live on the web. Building both channels simultaneously splits focus and engineering resources.
Resolution: Steam first. Web later, if at all.
Execution Order

Recommended Build Sequence

1
NOW
ICP A: Gamer Indie Builders
Ship the colony sim prototype. Validate the core loop is fun with real players. Steam Early Access is the launch vehicle. No infra until the game is fun.
ICP D: Dev Content Creators
Once prototype is playable, get it in front of dev streamers. Colony sim gameplay is inherently watchable. Emergent stories from real coding create viral content.
3
LATER
ICP C: AI-Curious Solo Founders
Only if A validates that game framing delivers emotional ROI. These founders discover Bismarck through word-of-mouth from A and D.
4
MUCH LATER / NEVER
ICP B: Vibe Coders
Would require a fundamentally different product: web-based, simplified UI, no game literacy required. Only if core tech proves valuable enough for a non-game wrapper.

GTM Comparison

ICP Motion Channel Cycle GTM Muscle
A: Gamer Indie Builders PLG via Steam Steam, Reddit, Discord, streamers Days Community + capsule art + demo
B: Vibe Coders PLG via web Product Hunt, TikTok Weeks Content marketing + free tier
C: AI-Curious Founders Mixed Indie Hackers, Twitter/X Days–weeks Community + word of mouth
D: Content Creators Direct outreach Email, Twitter DM N/A Press/influencer relations
Verdict: Build one GTM muscle at a time. Steam PLG first.