soloop product manual
Start with what you have.
An idea, URL, repo, deck, or half-built product. soloop turns that context into one next move, shows you the card, and waits for approval.
Quickstart
Get to the first approved task.
The shortest useful setup is one project, enough context to judge it, and one outcome you want next.
- 01
Create your workspace
Tell CEO who you are, what you are building, what works today, and what gives you an edge.
- 02
Add product context
Paste an idea or URL. Connect a GitHub repo, upload a ZIP, or attach the deck, brief, screenshot, or research you already have.
- 03
Describe the outcome you need
State the outcome you want. CEO reads the project, checks active work, and decides whether to answer, ask, or route the job.
- 04
Review the card
Read the objective, exact action, target, and credit cost. Coding cards also include acceptance criteria. Approve it, request changes, or cancel it.
- 05
Read what came back
Execution output appears in Tasks. Uploaded context and the Product Doc stay under Documents. Monitored replies appear in Inbox.
- Idea
- URL
- GitHub
- ZIP
- DOCX
- Image
Result locations
Where results are stored.
Tasks hold execution output. Documents hold uploaded context and the Product Doc. Inbox holds monitored replies.
Tasks
Task status, execution output, progress logs, failures, and credit use.
Documents
The Product Doc, uploaded files, extraction state, and indexing state.
Inbox
Monitored replies and external signals that may need a response.
Confirm the exact action, target, credit cost, and stop condition. Coding cards should also include acceptance criteria.
CEO and specialists
Choose a workspace.
CEO keeps the project together. Specialists take the work that needs a narrower judgment or an execution path.
CEO
Main conversationHolds the project view, chooses the next move, and routes work. CEO explains the decision and does not run external actions.
CMO
Mixed executionPlans acquisition across X, Reddit, cold email, and ads. X can publish approved work, Reddit stays manual, cold email requires Gmail and approved send tasks, and ads are plan-only.
CTO
Execution availableOwns product and code work. Approved jobs run in an isolated sandbox and can return a checked change or Vercel deployment.
Analyst
Execution availableRuns approved competitor, market, and target-user research. The report stays on the task and includes source links when the run collected them.
CFO
Conversation todayWorks through pricing, cost, and finance questions. It does not move money or run a separate finance worker.
Approvals
Read the card before the work starts.
Research runs, public posts, emails, code changes, and deployments need an approval path.
Approve
For an action card, start the exact work shown. For a handoff card, open the named specialist workspace.
Request changes
Close the current proposal with your correction. CEO or the specialist prepares a revised card for approval.
Cancel
Close the proposal. No research, post, send, code change, or deploy starts.
A handoff card is different from an action card.
A handoff opens CMO, CTO, Analyst, or CFO. Approval does not run external work. The specialist creates a separate action card when the work is concrete.
Documents and memory
Project context is kept in four records.
Chat is one view. The Product Doc, uploaded files, Tasks, and Inbox hold the durable record.
Product Doc
The editable brief for the product, target user, problem, advantage, and current focus.
Uploaded documents
Files stay with the project. Supported text documents are indexed when indexing is available, and the file status shows whether indexing succeeded.
Tasks
The source of truth for pending approvals, running work, failures, results, and execution notes.
Inbox
External replies and monitored signals that may deserve a response or change in direction.
When asking about prior work, name the file, task ID, reply, or Doc field so CEO can load the right record.
Current channels
What runs today.
Each channel below says whether soloop executes it, assists with it, or only plans it.
Analyst
LiveApproved competitor, market, and prospect research. Reports stay on the task; source links appear when collected.
X / Twitter
Live with OAuthDraft posts and replies, publish approved work, then collect comment signals from the connected account.
Cold email
Beta, Gmail requiredAfter Gmail is connected, CMO can prepare an operating plan and single-recipient send or reply cards. Sending follows the approval mode shown on the task.
Coding
LiveWork from a new project, GitHub repo, or ZIP. Approved jobs run in a sandbox and may deploy through Vercel.
Prepare a reviewable post or reply and open a prefilled Reddit flow. Public posting stays in your hands.
Ads
Plan onlyCMO can discuss the channel and put it in a plan. soloop does not buy or manage ads today.
Useful first requests
Give CEO a result to aim at.
- Compare these five competitors. Show the evidence before you call the gap.
- Find ten recent X posts where solo founders complain about getting their first users.
- Inspect this repo and prepare a task to fix the signup drop-off. Include the acceptance checks I should review before approval.
- Read this deck and update the Product Doc where the target user or offer changed.
Files and limits
File types and upload limits.
These are product limits from the current upload and project flows.
- Documents
- TXT, Markdown, PDF, and DOCX. Up to 10 MB per file.
- Images
- PNG, JPEG, WebP, and GIF. Up to 3 MB per image.
- Attachments
- Up to 5 files in one message or landing-page start.
- Existing code
- Connect a GitHub repository or upload a ZIP up to 50 MB.
- Long text
- Text attached to one chat message is capped at 50,000 extracted characters per file. The original file remains stored; indexed retrieval depends on its file status.
Troubleshooting
Check the task status first.
The latest task record shows whether the work is waiting, running, complete, or failed.
The card was approved, but the task did not start.
Open the task and read its latest state. Common holds are a missing account connection, exhausted credits, provider quota, or another coding job already using the project sandbox.
Approval opened another conversation instead of running work.
That was a specialist handoff card. It opens CMO, CTO, Analyst, or CFO. Approval does not run external work; the specialist must propose a separate action card.
The answer ignored an uploaded file.
Check that the file appears under project Documents, then name the file in your next message and ask CEO to read it before making the call.
The result is missing from chat.
Check Tasks for execution output, Documents for stored project context, and Inbox for replies or monitored signals. Background results do not always return to the open chat first.
Still blocked
Send the task ID and exact error.
Include the project name, the page you were on, and the last action you took.