| name | artifacts |
| description | Use when the founder needs a reusable business artifact from saved workspace context, especially investor/stakeholder updates or competitive snapshots. Combines recent context, tasks, research, closeouts, weekly plans, metrics supplied by the user, and competitor inputs into paste-ready drafts. |
| user-invocable | true |
Artifacts — Founder Outputs
Purpose
Turn the workspace into concrete founder outputs. This is the eighth operating workflow in SalesSidekick Lite.
Artifacts are not hidden intelligence. They are visible drafts the founder can inspect, edit, and send.
Supported Artifacts
Investor Or Stakeholder Update
Use when the user asks for:
- investor update
- stakeholder update
- board update
- monthly update
- weekly founder update
Read:
knowledge-bases/company-context.md
data/setup-status.md
views/weekly-plan.md
views/daily-briefing.md
data/tasks.md
- recent
data/research/
- recent
data/closeouts/
- metrics, asks, wins, risks, or notes supplied by the user
Output:
- headline
- wins
- learnings
- metrics or placeholders
- customer/pipeline/GTM progress
- blockers or risks
- asks
- next period focus
Save to:
exports/investor-update-{date}.md
Do not invent metrics, investor names, runway, revenue, customer names, or commitments.
Competitive Snapshot
Use when the user asks for:
- competitive snapshot
- competitor comparison
- category scan
- "who do we compete with?"
- "how should we position against X?"
Read:
knowledge-bases/company-context.md
- saved research
- supplied competitor names
- public sources if available
Output:
- competitor summary
- what each competitor leads with
- likely strengths
- likely weak spots
- our possible angle
- buyer questions
- sources
- open unknowns
Save to:
data/research/competitive-snapshot-{date}.md
Do not create full battlecards, win-probability models, landmine libraries, or displacement playbooks in Lite.
Usage Tracking
After saving an artifact:
- append one line to
data/ops.log
- update
data/setup-status.md workflow usage if the workflow tracker exists
- include a
FILES UPDATED block