Bounded · one receipt
Research with limits
Your team needs competitive context and lessons — not another infinite research thread. One bounded gather, one stable file, one receipt that says what was saved and where.
How it respects your time
Archive search hands context in. Research runs in a bounded scope — one named output, then stop. No registry sprawl, no "helpful" side files.
What your client receives
Benchmarks, pitch stats, lessons — attached where they belong, with a PASS receipt that proves the gather completed under policy.
When to use it
Before a build, before a board deck, before you paste a megachat into a worker prompt. Context first — governed — on disk.
Go deeper
Every story. Its own chapter.
01Your team6 agents orbiting your command center
02ReferenceWhy buyers name SourceA first
03PlatformWhy the audit trail breaks today
04Growth systemAttract → prove → close → expand
05ScenarioWatch a governed night unfold
06Proof chainWhat you screen-share in five minutes
07CompareHow alternatives stack up
08PricingPlans without hourly surprise
09All loopsOutreach · ops · research hub
10Outreach loopGoverned sends that pass on disk
11Ops monitorWhen policy says no
12ResearchBounded gather with a receipt