Workflows
BAD — Brief A Day
Client-ready briefs from raw inputs in one POM.
A voice memo, a transcript, a PDF, a one-liner — turn into a structured Project Card, sector classification, technical architecture doc, and proposal pack. Daily, on demand.
- Voice → structured Project Card
- Sector classification + framing options
- Proposal pack auto-drafted
Why
Discovery calls produce gold and lose it the moment they end. BAD captures the gold the same day — a Project Card, a sector framing, and a draft proposal pack — so the client momentum doesn't.
How
- Ingest the raw input (voice / transcript / PDF / bullets)
- Run /abc-intake → /abc-sector → /abc-architect → /abc-proposal
- Output: markdown master + HTML + JSX prototype + PDF + email
Proof
- Time from call to draft
- <1 POM-day
- Artefacts per BAD
- 5
- Sector packs available
- 8+
BAD — brief a day, intake to proposal
Raw input → 4 agents → 5 artefacts
Hover or tap a node to see details.
FAQ
- What format does the raw input need to be in?
- Anything with speech or text — voice memo (Whisper), PDF (OCR), email thread (raw), one-liner pitch (raw). The Intake agent handles modality routing internally.
- How long from input to draft proposal?
- Under one POM-day on most engagements. The bottleneck is the architect step, which is opinionated and won't rush a bad architecture call — by design.
- Can a non-technical sales person run BAD?
- Yes — it's designed to. The output is human-readable and the agent never asks for a configuration choice it can't infer from the input. One command, five artefacts back.
In production
- Voice memo → proposal pack
Discovery voice memo to draft proposal in under one POM-day via /abc-intake → sector → architect → proposal.
- Five output artefacts
Each BAD produces Markdown master + HTML proposal site + JSX prototype + PDF + outbound email.
- Sector-aware framings
Eight sector packs (charity, care, property, recruitment, services, franchise, excursions, other) — three framings per project.