The fastest way to fail with a placement workbench is to switch everything on for every team at once. The way that works is smaller: one team, one renewal cycle, agents at draft, and the product’s own record telling you what to switch on next.
The plan in one paragraph
- Days 1–30: one team’s renewals inside 120 days; readiness, the data-gap chaser and the controls only.
- Days 31–60: submissions and market selection on the same book; the appetite table maintained by the team.
- Days 61–90: comparison, proposal and compliance; review the record; decide on the second team.
Days 1–30: see the book
Load the team’s renewals inside 120 days with their exposures, SOVs, loss runs and expiring programs. Turn on the readiness agent, the data-gap chaser and the ten controls as shipped. The first value is visibility: the renewals page sorted by days to inception, readiness on every placement, and the controls’ warnings on Home. Leave every agent at L1.
Days 31–60: build and market
Turn on the submission builder and the market selector. The appetite table is the team’s knowledge — have the placement brokers own it, carrier by carrier. Keep outreach on the dry-run provider until the team trusts the drafts; log approaches and responses on the market rows either way.
Days 61–90: compare, propose, review
Turn on the comparison, the proposal writer and the compliance agent. At day 90, read the record:
| Question | Where the answer is |
|---|---|
| Are placements on the calendar earlier? | Readiness at the 90- and 60-day marks; placements behind the calendar |
| Are the agents right? | Agreement and overrides per agent and action on the autonomy page |
| Which controls do real work? | 30-day hits per rule in the Studio; how often a refer changed the outcome |
| Where do brokers disagree with the recommendation? | Selections that differ from the recommended quote, with reasons |
| What does it cost? | Model calls, tokens and cost per agent run |
Governance from day one
- Model risk reviews the grounding contract (engines compute, models explain, ungrounded numbers rejected), the per-run traces and the versioned prompts.
- E&O review reads the decision record: controls, prepared decisions, signed answers, the client’s sign-off.
- Compliance owns the security-floor and surplus lines thresholds in the Studio.
- IT confirms identity, tenancy, where documents are stored and which model account the agents use — see security & deployment.
What we will not promise
We do not publish customer results, because we will not invent them. The ninety days are for you to measure your own: the product records everything you need to do it.

