Blog · Tag
shipped.
8 posts in this archive.
Shipped: auto-generated post-mortem themes
After 200 debriefs the themes cluster predictably. The clustering is now automatic — here's what ships, what it does, and what it refuses to do.
Shipped: the win-loss dashboard with debrief capture
We shipped the win-loss dashboard last week. It's the feature behind this month's series. Debrief capture, theme clustering, and KB write-back, all wired to the schema.
In preview: the post-mortem pipeline at submit close
The moment a proposal marks won or lost, PursuitAgent opens a structured post-mortem against the captured pair. In preview while the post-mortem template, reflection, and write-back loop mature toward general availability.
Shipped: bulk edit for answer blocks, with undo
A real-world request we dragged our feet on for nine months. Bulk edit is now in the product, with version-aware undo and a confirmation flow that prevents the silent overwrite that made us nervous in the first place.
In preview: question router v2 with confidence scores
DDQ questions now route with a confidence score in preview. High-confidence routes auto-draft from the KB; low-confidence routes to human review with a typed reason for the routing call.
Shipped: answer-block inheritance across projects
When you edit an approved KB block, in-flight proposals inherit the change without overwriting their local edits. Here's how the merge resolves and what we did about the conflict cases.
Shipped: win/loss pair capture at submit time
When a proposal hits submit, PursuitAgent now captures the response, the disposition, and the structured post-mortem inputs into a single record. The first piece of the win/loss intelligence loop is in production.
Stop announcing features, announce what changed for the reader
An announcement that names a feature is a press release. An announcement that names what changed in the reader's day is a useful one. A short field note on what we'll publish under 'shipped' from now on.
See the proposal workflow
Take the 5-minute tour, then start a trial workspace when you're ready to run a real pursuit against your own source material.