Indie
Ask for an outcome
Describe the work in plain language. Indie routes specialists. Direct @commands stay the power-user path.
Founder OS · docs
Documentation for the
Founder OS
Ask Indie for an outcome. Specialists on the roster remember the company, cite live pages, and wait at /approvals before anything leaves the terminal.
Cited work Shared memory Human approval
Find the wedge in AI app builders
Vera is scraping live competitor pages with your positioning and pricing history attached.
Context12 brain artifacts
Sources4 pages cited
Draft saved to company brainNext: approve →
Ask Indie
The operating layer
Indie is the AI operating partner at /command. Ask Indie for an outcome in plain language. Power users type @research, @post, or @build directly. Around every run: a named roster, a company brain with lineage, citations you can open, and a human decision at /approvals before any external action.
Company brain
Context with lineage
Research, decisions, and drafts persist as artifacts. Later runs read them instead of starting from a blank chat.
Connected work
Export through connectors
Agents can prepare Slack, Notion, X, HubSpot, and Airtable updates. The payload still waits at /approvals.
Approval queue
Nothing ships alone
Review at /approvals. Nothing posts, syncs, or ships until you approve — including scheduled @post drafts.
What problem does it solve?
Founders re-explain the company to a blank chat, or they let a mega-agent touch every tool with no owner. Indieterminal replaces that with Indie: describe the outcome, let Indie route a specialist, and approve at /approvals before anything ships.
Who this is for
- —Solo founders who want an operating partner, not another chat tab
- —Teams who need agents that remember the company
- —Operators who will not let tools post without sign-off
Your first session
Three actions — under five minutes:
Start here
1 · Ask IndieGo to the terminal and describe the outcome. Indie routes the work.
2 · Or @researchPower users type
@research on a niche. Cited indie comps, saved to the company brain.3 · ApproveExternal writes wait at /approvals. Nothing ships until you sign off.
Need the full map? Read next, or jump to for a guided walkthrough.
Founder OS
Founder OS is the operating layer for coordinating humans and agents. One terminal window — Indie, commands, brain, specialists, and approvals — instead of ten browser tabs and exported ChatGPT threads.
System map — five layers
Indie + TerminalAsk Indie for an outcome, or run /commands on the shared console
Company brainOrg memory with lineage — persists across every run
Specialists@team roster — Vera @research · Kai @launch · Nova @post · and the rest
ConnectorsSlack, Notion, X, GitHub, HubSpot — after you approve at /connectors
Approval queue@approvals — connector exports wait for your sign-off
North star workflow
Ask Indie→Morning brief→@research→@asset→@post→Approve on /approvals
Nothing ships to Slack, Notion, or X until you approve it at /approvals. Humans stay in charge — agents do the prep work.
What makes it different
Context compounds
- Session artifacts chain together
- @post reads your latest @research
- Company brain remembers your startup
Cited, not guessed
- @research pulls real indie comps
- Pricing audits use live pages
- Every claim links to a source row
Zero tab switching
- Tools open inline in Terminal
- Deep UIs still available from sidebar
- One keyboard shortcut: ⌘K to command bar
Governed exports
- Connector actions queue first
- Approval history in the terminal
- Nothing posts without you
Quick Start
A practical walkthrough of the resources most founders use on day one. Everything runs from the terminal unless noted.
Your first 5 minutes
Step 1
Ask Indie
Open /command and describe the outcome. Indie routes the work with your company brain.
› connect https://yoursite.com
✓ Company brain saved
Step 2
Run cited research
@research [niche] — indie comps with MRR, not generic summaries.
AI app builders
Cited scan for an indie founder checking whether the category still has a pricing wedge.
Market
AI app builders · public pages this run
Named comps
LovableBolt.newv0Replit Agent
Gap
No indie-focused tier under $29/mo on the pages scraped this run
Citations
- lovable.dev/pricing · scraped this run
- bolt.new · positioning + tiers
- v0.dev · public product page
- replit.com/ai · agent SKU
Step 3
Audit your pricing
@price inline — see where you sit vs real competitors.
› price
✓ Verdict: FAIR · $29/mo vs $27 median
Step 4
Connect exports (optional)
Add keys at /connectors. Nothing posts until you approve.
› export notion
⏳ Queued · awaiting approval
Ready? Open the terminal and ask Indie — or type @research.
@research
Cited competitor scans
Not a chat dump. The agent scrapes live competitor pages this run, attaches citations, and writes a brain artifact with lineage. @price and @post can read it. Notion and Slack still wait in the approval queue.
AI app builders
Cited scan for an indie founder checking whether the category still has a pricing wedge.
Market
AI app builders · public pages this run
Named comps
LovableBolt.newv0Replit Agent
Gap
No indie-focused tier under $29/mo on the pages scraped this run
Citations
- lovable.dev/pricing · scraped this run
- bolt.new · positioning + tiers
- v0.dev · public product page
- replit.com/ai · agent SKU
What you actually get
A command is the trigger. The product is the operating layer around it: memory, citations, and a human gate.
You stay in one console
Type @research in the shared left/right shell. Context sits on the left. The live report streams on the right. No /tools tab, no blank chat hero.
Every comp is a live page
Homepages and pricing pages scraped this run — not a mirrored directory. If a line has no source, treat it as a draft.
The report compounds
The artifact is persisted with derivedFrom lineage. Later hires and runs read it so you do not re-brief the company.
Export is a decision
Queue to Notion or Slack from the same console. A human reviews the payload. Nothing posts because an agent felt done.
After the scan
Company brainKeep the finding
The scan is an artifact, not a tab you will lose. Open it from the context rail or the brain.
@price · @mapPrice and position from the same comps
Those agents inherit the cited set instead of starting a new guess.
Hire VeraPut research on a schedule
A named hire runs @research weekly into the brain. You still approve anything that leaves the building.
FAQ
Generic chat has no owner, no company memory, and no citations you can open. @research scrapes live pages this run, stores the artifact in the brain, and still will not export until you approve.
Agent
@price
Comp-backed pricing bands in seconds. Know if you're underpriced, fair, or leaving money on the table.
Pricing verdict
›price dev-tools SaaS
Scraping live competitor pages…
Your price: $12/mo · Market median: $29/mo
Verdict: UNDERPRICED
Recommended band: $24–$32/mo
Fair premium zone identified · growth without churn risk
Before
- Guess from 3 competitor homepages
- No idea if $9 or $49 is right
- Pricing changes based on vibes
After
- Live competitor pricing pages
- UNDERPRICED / FAIR / OVERPRICED verdict
- Exact band with cited sources
Example
Input
My SaaS · $12/mo · dev-tools niche
Audit result
- Verdict
- UNDERPRICED
- Market median
- $29/mo
- Recommended
- $24–$32/mo
- Comps analyzed
- Live pricing pages
- Confidence
- High · 48 public tiers matched
How it works
01
Enter your price
One field. Your niche. Done.
02
Match comps
Public pricing pages scraped this run.
03
Get the verdict
Clear UNDERPRICED / FAIR / OVERPRICED with recommended band.
FAQ
Public pricing pages the agent scrapes this run — not a mirrored directory.
Commands
Ask Indie in plain language, or type @ plus an agent name at the terminal. Founder OS commands run inline with your startup context. Focused consoles stay on the same left/right shell.
Founder OS commands
| Command | Status | What it does |
|---|---|---|
@research | live | Cited competitor scan · live web + connected GitHub repo |
@launch | live | Launch war room · readiness · execution sequence · distribution |
@operate | live | Weekly operating brief · blockers → Linear / Jira / Asana on approve |
@post | live | Draft posts for X, LinkedIn, Threads, Reddit & more · publishes only to connected accounts after approval |
@cockpit | planned | Decision brief · live signals · risks · pending execution |
@intel | live | Category ledger from live competitor sites · cited comps · confirm to brain |
@price | live | Price agent · comp-backed bands · packaging experiments |
@scan | live | Scan agent · opportunity + GTM from live competitor sites |
@radar | live | Category movers and market gaps from live competitor sites |
@map | live | Competitor map · cited positioning · white space from live comps |
@value | live | Valuation agent · ARR / SDE / blended from cited comps |
@asset | live | Design studio for launch stills · not logos, not copy · then @post |
@build | live | Isolated code patch · bounded checks · GitHub writes on approve |
@doc | live | Create / edit / export — grounded in workspace + brain |
Live today: @research, @launch, @operate, @post, @intel, @price, @scan, @radar, @map, @value, @asset, @build, @doc. Planned: @cockpit.
Console agents
These run on the shared left/right console — no navigation away from the terminal.
@scanScan agentOpportunity + GTM from live competitor sites
@pricePrice agentComp-backed pricing bands and positioning
@mapCompetitor MapMap competitors and track positioning
@intelIntel agentCited category ledger from live competitor sites
@radarMarket RadarCategory movers and market gaps
@valueValuationARR, SDE, and blended valuation
@post — schedule and timezone
Drafts for X, LinkedIn, Threads, Reddit, and more. Publishing only happens to connected accounts after you approve at /approvals. Choose Schedule for later, pick a local time, and set the publishing timezone on the draft card or the post calendar. Editing the copy or time cancels a stale approval. Nothing auto-posts.
Tip Ask Indie in plain language, or type
@help for the live command list.Use Cases & Playbooks
Each playbook maps a founder situation to agents that are live today.
Command cheat sheet
- —Ask Indie for an outcome, then specialists as the power-user path
- —
@research·@launch·@operate·@post— core loop (live) - —
@intel·@price·@scan·@radar·@map·@value— shared consoles - —
@asset·@doc·@build— visuals, docs, isolated patches (live)
Playbook 1: 'I Have a Startup Idea'
The flow
- 01Run @scan [your idea] at /command — fast validation + GTM from live comps
- 02Run @research [niche] — deeper cited teardown with MRR and positioning
- 03Run @price — see what the market actually pays in your category
- 04Run @map at /command/map — find the empty quadrant on the 2D map
- 05Run @scan at /command/scan — generate a launch plan for your stage
OutcomeYou either find a real gap and build with confidence — or you discover the market is saturated and pivot before wasting 6 months.
Playbook 2: 'My Product Isn't Selling'
The flow
- 01Run @price on your product — get UNDERPRICED / FAIR / OVERPRICED vs 50+ comps
- 02Run @research on your top 3 competitors — cited MRR and tier breakdowns
- 03Run @map at /command/map — see if you're in the wrong quadrant
- 04Run @price at /command/price for full tier-by-tier comparison
- 05Reposition with @scan at /command/scan focused on messaging, not features
OutcomeYou identify whether it's a price problem, a positioning problem, or both — and you fix it with data, not guesses.
Playbook 3: 'I Want Startup Ideas'
The flow
- 01Run @scan on categories you care about
- 02Run @research on shortlisted niches — persist to the company brain
- 03Run @price in each shortlisted niche — confirm people pay
- 04Run @map per niche — spot crowded vs empty quadrants
- 05Validate top 2–3 with @scan before committing to build
OutcomeYou discover 2–3 real opportunities with paying users, existing demand, and room for a new player.
Playbook 4: 'I'm Building in Public'
The flow
- 01Run @research [niche] — pull 3 cited comps with MRR hooks
- 02Run @price — grab median tier pricing for a 'what the market pays' post
- 03Run @scan at /command/scan — one distribution insight to share in your voice
- 04Screenshot /command/map — strong visual for X/LinkedIn
- 05Post with your take — data-backed beats generic build logs
OutcomeData-backed content that gets way more engagement than generic 'day 1 of building' posts.
Playbook 5: 'I'm Pitching Investors'
The flow
- 01Run @research [niche] — export cited comps for your deck
- 02Run @price — anchor your revenue model to market medians
- 03Screenshot /command/map for a positioning slide
- 04Run @scan at /command/scan — pull distribution strategy bullets
- 05Run @operate for a weekly brief you can drop into the deck
OutcomeYou walk into your pitch knowing more about your market than your investors. That's how you earn trust.
Consoles
Shared command consoles
Ask Indie, or open a focused console. Research, launch, operate, post, intel, price, scan, build — same company brain, same approval queue.
Pick an agent
live
Scan agent
@scanOpportunity + GTM from live competitor sites
Learn morelive
Price agent
@priceComp-backed pricing bands and positioning
Learn morelive
Competitor Map
@mapMap competitors and track positioning
Learn morelive
Intel agent
@intelCited category ledger from live competitor sites
Learn morelive
Market Radar
@radarCategory movers and market gaps
Learn morelive
Valuation
@valueARR, SDE, and blended valuation
Learn moreSame console
These agents do not open a separate app. They use the shared left/right terminal, write to the brain, and still cannot post without you.
Agent
@scan
Validate any startup idea in 30 seconds. Full competitive analysis plus a GTM plan from live comps.
Before
- Weeks of manual competitor research
- No structured GTM output
- Guessing if the market is open
After
- Full comp map in 30 seconds
- GTM plan with cited comps
- Clear build or pivot signal
Example
Input
AI note-taking app for indie founders
Output
- Competitors
- 12 cited live pages
- Market gap
- No indie-focused tier under $19/mo
- GTM
- ICP + channels + 30-day sequence
- Verdict
- Build — gap confirmed
Terminal
›scan AI note-taking for founders
Scraping live competitor pages…
12 competitors mapped
GTM plan generated
Pricing band: $19–$39/mo
Opportunity score: 8.2/10
How it works
01
Describe your idea
One sentence is enough — niche and audience.
02
Match comps
Scanner pulls live competitor pages, not a directory.
03
Get GTM + verdict
ICP, channels, pricing band, and build/pivot signal.
Key benefits
Validate before code
Know if the market is saturated before you build.
Cited live pages
Every comp links to a site scraped this run.
Inline at /command
Run @scan without leaving the terminal.
Use cases
@scanPre-build validation
Test an idea before writing a landing page.
@scan → @researchDeep follow-up
Chain into @research for a full cited report.
@scanLong session
Full console for exploring multiple ideas.
FAQ
@scan is fast validation + GTM. @research is a deeper cited teardown.
Agent
@intel
Deep competitor profiles and pricing lookups from live pages — the research layer under @research.
Example
Input
Profile: Linear · category: dev-tools
Output
- MRR est.
- $42K/mo
- Growth
- +18% QoQ
- Pricing
- $8–$16/user/mo
- Peers
- 6 in same band
Terminal
›intel linear
Scraping competitor homepage…
MRR · growth · pricing tiers
6 category peers sampled
Profile ready · exportable
How it works
01
Query any startup
Name or URL — scrapes the public site.
02
Deep profile
MRR, growth, pricing, category context.
03
Export
Use in decks, Notion, or agent pipelines.
Key benefits
Verify citations
Open the live page behind any @research comp.
Live signals
Category movers from pages scraped this run.
Same console
Runs on the shared left/right agent console.
Use cases
@intelComp teardown
Full profile on one competitor.
@intelPricing lookup
Distribution for any niche.
@intelResearch session
Long-form intel gathering.
Agent
@map
2D positioning map — niche vs broad, budget vs premium. Find the empty quadrant.
Example
Input
Category: AI app builders
Output
- Players plotted
- 24 startups
- Empty quadrant
- Niche + premium
- Your position
- Broad + budget
- Opportunity
- Move up-market
Terminal
›map AI app builders
Plotting live comps…
24 bubbles on map
Empty quadrant: niche + premium
Positioning recommendation ready
How it works
01
Select category
Maps every major player in your market.
02
Read the map
X = niche→broad · Y = budget→premium.
03
Find whitespace
Empty quadrants = positioning opportunities.
Key benefits
Visual strategy
Screenshot for decks and build-in-public posts.
Whitespace detection
See where no one is playing.
Track moves
Re-run when competitors shift pricing.
Use cases
@mapPositioning
Find where to sit vs crowded players.
@mapPitch decks
Export map visual for investors.
@mapDeep map
Full console with filters and export.
Agent
@radar
Optional in-app panel for category movers. Indieterminal stays the Founder OS: ask Indie, run specialists, persist to the company brain, and approve before anything ships.
Example
Input
Watch: dev-tools · AI · creator economy
Output
- Signals
- 14 this week
- Top mover
- +42% MRR · AI docs
- Gap
- Compliance SaaS for indie
- Score
- 8.7 opportunity
Terminal
›radar dev-tools
Scanning signal feed…
14 signals · last 7 days
Top mover: AI docs +42% MRR
Gap flagged: compliance SaaS
How it works
01
Set categories
Radar watches niches you care about.
02
Detect signals
MRR spikes, launches, trend acceleration.
03
Act on gaps
Ranked opportunities with scores.
Key benefits
Always on
Signals refresh from pages scraped this run.
Find ideas
Discover markets you did not know to search.
Why now
Back pitch narratives with live signal data.
Use cases
@radarIdea discovery
Find underserved niches with demand.
@radarInvestor narrative
Support "why now" with signals.
@radarWeekly digest
Top 5 opportunities ranked.
Agent
@value
Four methods — ARR multiple, revenue multiple, SDE, and DCF — triangulated against live comps.
Example
Input
SaaS · $15K MRR · 40% growth · dev-tools
Output
- ARR multiple
- $540K
- Revenue multiple
- $495K
- SDE
- $420K
- DCF
- $580K
Terminal
›value my-saas $15K MRR
Running 4 methodologies…
ARR multiple: $540K
SDE: $420K · DCF: $580K
Cluster within 20% — solid range
How it works
01
Enter metrics
MRR, growth, category — minimal inputs.
02
Run four models
ARR, revenue, SDE, and 5-year DCF.
03
Triangulate
Cluster = confidence · divergence = investigate.
Key benefits
Raise or sell ready
Defensible range for investors or buyers.
Index benchmarks
Multiples calibrated to indie comps.
Four lenses
No single-method blind spots.
Use cases
@valueFundraising
Anchor your raise with comp-backed range.
@valueExit planning
Know what you built before listing.
@valueFull suite
Deep console with sensitivity tables.
Agents
Hire specialists
Ask Indie for an outcome, then hire a named specialist onto @team when you want a standing owner. Vera, Kai, Juno, Nova, and the rest bind to one live /command.
Example
Input
Hire a researcher for AI docs · bind to @research
Output
- Hire
- Vera · Research
- Bound command
- @research
- Schedule
- Mondays 8am
- Status
- Queued for approval
Terminal
›hire Vera to research AI docs for indie founders
Job → three briefing questions
Vera · Research · bound to @research
Schedule · Mondays 8am
Roster updated · exports wait at @approvals
How it works
01
Describe the job
Plain language. Three clarifying questions so you shape the brief.
02
Bind to a live command
One hire owns @research, @launch, @post, or another live command.
03
Approve exports
Nothing ships to Slack, Notion, or X without sign-off.
Key benefits
Named owner
A specialist on @team, not a blank chat thread.
Company brain
Each run persists with lineage for the next.
Governed
Queue at @approvals before Slack, Notion, or X.
Use cases
Vera · @researchCited market scan
Weekly research into the company brain.
Kai · @launchLaunch war room
Positioning, channels, dated checklist.
Nova · @postDrafts in your voice
Scheduled posts; every draft waits for approval.
Operate
@operate
Ask Indie for this week’s operating brief, or run @operate. Blockers, priorities, and ticket drafts from the company brain — exports still wait at @approvals.
Example
Input
This week’s operating brief
Output
- Blockers
- 3 with owners
- Priorities
- Ship pricing page · follow up 4 leads
- Tickets
- Queued for Linear / Jira on approve
- Status
- Brief saved to company brain
Terminal
›operate this week
Reading company brain…
3 blockers with owners
Priorities ranked for this week
Brief ready · tickets wait at @approvals
How it works
01
Ask Indie or run @operate
Plain language is enough — Juno owns the standing brief.
02
Pull from the brain
Recent runs, launch state, and connected tools.
03
Approve writes
Linear, Jira, Asana, and Slack still wait in the queue.
Key benefits
One weekly picture
Blockers and next moves without a new tab stack.
Company memory
The brief reads prior artifacts instead of starting blank.
Governed follow-through
Ticket drafts queue at @approvals — nothing auto-files.
Use cases
@operateMonday brief
Start the week from the company brain.
Ask IndieOutcome in plain language
“What should we ship this week?”
@radarGo deeper
Follow a market mover after the operating brief.
Workflows
A workflow is a chain of commands where each step reads context from the last. Artifacts accumulate in your session — visible in the context rail on the right of the command runner.
Default chain — research → asset → post
@researchCited competitor scan · saved to company brain
@assetLaunch visuals using research context
@postDraft from latest research — publishes wait for approval
ApproveReview in queue → export to Notion, Slack, or X
Session context rail
Every Founder OS run appends an artifact to your session. The rail shows lineage — click any prior artifact to re-read it, or chain a new command that inherits that context.
Example session
09:12@research linear competitors → Research report (4 citations)
09:18@scan dev tools → Scanner results (inline tool)
09:24@post thread about positioning → Draft queued · needs approval
When to chain vs. run standalone
- —Chain when outputs feed the next step — research before a post, audit before a pricing change
- —Run standalone for one-off questions — @intel, @price, @scan don't need prior context
- —Clear session when switching to a different startup or unrelated project
- —Save important artifacts to Workspace for long-term company brain storage
Roster
Hire named agents
Indie is the operating partner. Hire a specialist when you want a standing owner. Describe a job, brief the hire, bind them to a live /command on @team.
Agent pipeline
›hire a writer for X
Job → three briefing questions
Nova · Content Writer · bound to @post
Schedule · Mondays 8am
Skills · brain · company voice
Draft queued · needs approval
How it works
01
Describe
Plain-language job. Three clarifying questions so you shape the brief.
02
Bind
The hire joins the roster on exactly one live command, with a schedule and the company brain.
03
Approve
Nothing ships without human sign-off in the queue.
Agent types
Vera · @researchCited market scan
Weekly research into the company brain. Never repeats a finding.
Kai · @launchLaunch war room
Positioning, channels, dated checklist — from past launches in the brain.
Nova · @postDrafts in your voice
Schedule for later with the shared publishing timezone picker. Every draft still waits at @approvals.
FAQ
No. Every connector action queues for approval at @approvals first. Scheduled @post drafts use the same timezone picker as the post calendar and still need that sign-off.
Integrations
Browse integration setup guides →Connect the tools you already use at /connectors. Indieterminal never auto-posts — every connector action queues for your approval at /approvals.
Export flow — nothing ships alone
RunCommand or agent produces a deliverable with cited comps
QueueConnector action appears at @approvals
ReviewYou read the payload — Slack message, Notion page, CRM note
ApproveAction executes · logged with timestamp
Why approval-gated exports matter
Agents can draft overnight. You stay in control of what hits Slack, Notion, HubSpot, or X. Scheduled @post drafts use the same timezone picker as the post calendar. The queue is the governance layer between AI prep work and your live stack.
Supported connectors
Slack · Notifications
On approval — post pipeline updates, digests, and export prompts to your channels.
AvailableNotion · Export
On approval — cited deliverables export as Notion pages in your workspace.
AvailableZapier · Automation
On approval — completed runs trigger webhooks and the rest of your stack.
AvailableHubSpot · CRM
On approval — ICP insights, comps, and lead notes sync to deals and contacts.
AvailableAirtable · Export
On approval — comps, plans, and signal tables sync to your bases as rows.
AvailableX · Social
On approval — publish scheduled or immediate @post drafts to X.
AvailableGitHub · Dev
On approval — repo-grounded research, issues, and @build writes after you sign off.
AvailableCited live comps
@research, @intel, and @price scrape live competitor pages so founders are not stuck with generic chat summaries. That supporting evidence is not the product. Indieterminal is the operating layer: terminal, company brain, agents, and an approval queue.
API Reference
Public discovery is GET /api/v1. Agents run in the terminal. Connector credentials live at /connectors.
Public
Discovery — GET https://indieterminal.com/api/v1
No Bearer token. OpenAPI at /openapi.json. CLI: npx indie-terminal discover.
Endpoints
GET
/api/v1Public discovery catalog.
Parameters
Example
GET /api/v1
Changelog
What shipped
Roster, brain, citations, approval — and the public surfaces around them. What is live now, and what stays planned.
Release timeline
v0.13.0Latest
Weekly credits, paid builds, integration guides
One weekly credit wallet covers chat and builds. Company-grounded team assembly, paid build gates, and public connector setup guides.
- Paid plans share one weekly credit wallet, including builds (Oct 23)
- Company-grounded specialist assembly on setup (Oct 23–24)
- Paid @build gates, reviewed prompt workflows, and public integration guides (Oct 24–25)
Scheduler wake, timezone picker, faster nav
Due scheduled posts self-wake. @post drafts and the post calendar share a publishing timezone picker. Approvals return to the command you came from.
- Scheduler self-wake for due posts, plus post-safety guards
- Shared timezone picker on the @post draft card and post calendar
- Approvals back-navigation to the originating /command surface
- Faster workspace navigation: deferred panels, shared reads, hover prefetch
Scheduled posts, public shares, Pro at $29
Inline @post drafts can be scheduled. Public launch-report shares stay citation-safe. Pro’s public sticker is $29/mo.
- Homepage served at / (Oct 15); landing demos and public launch-report shares (Oct 20)
- Scheduled @post publishing with timezone-aware calendar times (Oct 19–20)
- Pro monthly sticker $29 (Oct 21) — checkout amounts stay on existing Dodo products
Approvals on /approvals
The review queue is a dedicated /approvals page again, with inline cards still on /command. Human chats persist and reopen.
- Dedicated /approvals review page; /command still shows inline approval cards
- Human chats persist and reopen without losing the thread
@build is live
Isolated sandbox patches, bounded checks, and GitHub writes only after approval. /command/cockpit stays planned.
- @build inspects the connected repo, produces a bounded patch, and stops the sandbox
- Push and draft PR are separate high-risk approvals — never merge or deploy
- /command/cockpit remains planned
Composio-only connectors
Connectors sign in through Composio. Paste-a-key Slack, Notion, HubSpot, Zapier, Airtable, and OpenAI BYOK cards are gone.
- /connectors is Composio OAuth only — no manual API keys
- Model keys stay in Settings → AI accounts
- Exports still wait in the approval queue
Docs on the operating layer
Public docs lead with roster, company brain, citations, and approval — not a command cheat sheet.
- Product hero with a live @research run on the shared console
- Copy page uses official ChatGPT, Claude, Perplexity, and Cursor marks
- Changelog is a timeline instead of a dense table
- Nav grouped by roster, brain, and consoles
One wordmark, Founder OS docs
Public pages share the Indieterminal wordmark. Docs explain the operating layer — roster, brain, citations, approval — not a command cheat sheet.
- BrandWordmark is the only public logo: mark + INDIE + TERMINAL
- Docs sit under MarketNav with a three-column Founder OS layout
- @research is documented as a cited brain artifact, not a GIF placeholder
- 404 uses the same wordmark as Home
Directory retired
The public startup directory is gone. Agents scrape live competitor pages. Connector secrets stay at /connectors.
- Removed directory pages and authenticated catalog search
- GET /api/v1 is a public discovery ping only
- Connectors (BYOK + Slack / Notion) stay at /connectors
- CLI discover and openapi wrap that ping and OpenAPI
Hire onto the roster
Named agents, company brain, and approval are the product. Crawlers get /agent.md and llms.txt — not workspace data.
- Hire: describe a job, brief, bind to one live agent, schedule, approve
- Live v1 agents: @research @launch @operate @post @intel @price @scan @radar @map @value @asset @doc
- llms.txt and /agent.md tell crawlers what to read
- Unknown HTML paths return a real HTTP 404
Machine-readable docs
llms.txt, per-section Markdown, and Copy page with production URLs so agents and humans read the same docs.
- llms.txt index and /docs.md for model context
- Copy page — ChatGPT, Claude, Perplexity, Cursor
- Founder OS rewrite: quick start, cited comps, gated connectors
Shared console
Every live agent runs on the left/right terminal. Context rail, brain persist, approval queue.
- /command is the default surface — not a stack of tool tabs
- @research live with cited competitor scans
- Lineage: research → asset → post on the context rail
Landing and agent.md
Public site positioned as the operating layer. Agent manifest at /agent.md.
- Agent manifest at /agent.md
- Landing: Founder OS, human/agent dock, pipeline visuals
Core platform
Command center, company brain, approval-gated connectors. Market tools as agents on the shared console.
- Terminal at /command — agents, brain, approval queue
- Live consoles: @scan @intel @map @radar @value
- Connectors — Slack, Notion, HubSpot, Zapier, Airtable (approval-gated)
Upcoming
- On deck
/command/cockpit stays planned — not a live console
- On deck
Richer roster schedules; overnight drafts still wait in the queue
- On deck
More connectors through the same approval gate — no silent posts
FAQ
Quick answers about Founder OS, hiring agents, and how Indieterminal works today.
What is Indieterminal?+
Who is Indie?+
What works today vs. what's planned?+
How do I hire an agent?+
Where do connectors live?+
Do Slack or Notion exports post automatically?+
Can I schedule a post?+
Where do I start?+
Is there a public REST API?+
Are competitor numbers accurate?+
What's free on Starter?+
What does the v1 API expose?+
Where are docs for AI agents?+
Founder OS · terminal
Open the terminal
Ask Indie for an outcome, run @research if you want the specialist, approve before anything ships.
Open terminal