Diagnosis pain
Bottleneck Map
Ranked painpoints, recommended harness, risk notes, and the next agent action.
Agent system
Solodot uses agents as harnessed workflows, not silent employees.
The intake result is the routing layer. It becomes the handoff into the right harness, where specialist agents prepare one action or execution asset and wait for founder approval.
Harness path
01
Founder intake
02
Painpoint router
03
Harness planner
04
Action planner
05
Risk evaluator
06
Founder approval
07
Copy or export
Roadmap boundary
Solodot now carries the result into a stored, approval-gated action loop when persistence is configured.
The product can record runs, actions, approvals, previews, and export/delete controls. It still does not publish, send email, write to a CRM, invoice, or automate compliance.
Execution-pack harnesses
Six ways a routed painpoint can become agent work.
Each harness uses the same control pattern: structured context, role-scoped agents, evaluator review, and founder approval before any external action.
Distribution pain
First-Customer Pipeline
ICP, buyer trigger, channel choice, weekly outreach sprint, and approval-ready outreach direction.
Workflow pain
Founder Function Map
Founder-owned work, agent-assisted work, paused work, batched work, and weekly operating rhythm.
Retention pain
Customer Learning Loop
Feedback synthesis, retention hypothesis, risk notes, and next customer learning action.
Trust pain
Trust Packet
B2B FAQ, support expectations, proof gaps, and unsupported claims marked for founder approval.
Orchestration pain
Agent Workflow Plan
Agent roles, required inputs, approval gates, final artifact, and review checklist.
Current diagram
The homepage packs still show the first execution surface.
The intake harness is the router. These execution packs are the first agent actions Solodot can prepare for founder approval.
The first paid-beta test is one intake plus one execution pack. The router can still select any of the six workflows when the founder's evidence points somewhere else.
Founder approval
Painpoint router
Bottleneck Map
Primary validation wedge
First-Customer Pipeline
Available route
Founder Function Map
Available route
Customer Learning Loop
Available route
Trust Packet
Available route
Agent Workflow Plan
Painpoint router
Bottleneck Map
Ranks the active founder painpoints and names the harness that should run next.
Use when
Several urgent problems compete and the real constraint is unclear.
Resulting asset
A ranked bottleneck map with one next move and a not-this-week list.
- Primary bottleneck
- What not to do this week
- One next action
Primary validation wedge
First-Customer Pipeline
Turns offer, ICP, channel, and constraints into one testable weekly customer sprint.
Use when
A product exists, but ICP, buyer trigger, replies, or weekly customer motion are weak.
Resulting asset
An ICP hypothesis, outreach direction, and a weekly first-customer sprint.
- ICP and buyer trigger
- Outreach angle
- Weekly prospecting plan
Available route
Founder Function Map
Separates founder-only work, agent-assisted work, paused work, and batched recurring work.
Use when
Delivery, sales, support, and admin compete for the same founder hour.
Resulting asset
A founder-function map and a realistic weekly operating rhythm.
- Founder-owned work
- Agent-assisted work
- Weekly operating rhythm
Available route
Customer Learning Loop
Turns customer feedback, churn risk, or activation confusion into one learning experiment.
Use when
Feedback exists, but the next customer or product lesson is unclear.
Resulting asset
A learning question, risk hypothesis, and next experiment.
- Feedback synthesis
- Retention risk
- Next experiment
Available route
Trust Packet
Drafts credibility material for solo founders selling into cautious or enterprise-like buyers.
Use when
An active buyer needs proof, process, support, security, or continuity answers.
Resulting asset
An approval-ready buyer packet that marks proof gaps and unsupported claims.
- Security and process FAQ
- Support expectations
- Unsupported claims marked
Available route
Agent Workflow Plan
Coordinates AI tool roles, required inputs, approval gates, and the final agent action.
Use when
Several AI tools or roles exist, but their handoffs and approvals are unclear.
Resulting asset
A role map, handoff artifacts, review checklist, and one final action.
- Agent roles
- Handoff artifacts
- Review checklist