CultivateOSbushel turns recommendations
into the nine artefacts a launch needs.
Blog announcement, customer email, support FAQ, sales one-pager, internal memo, demo script update, changelog entry, help-centre update, roll-out plan. Generated together, grouped by audience, every line carrying its provenance.
One recommendation in. Nine artefacts out.
Bushel takes a Winnow recommendation as its source, adds your launch context, and generates the nine artefacts in a single pass. Audience-grouped from the start; provenance attached to every line.
Pick a recommendation.
Anything from Winnow’s recommendation list. Bushel reads the recommendation, the user stories, and the foundations it cited.
> bushel new "cold-start"
✓ source: [r/2025-04/cold-start]
✓ 3 user stories attached
✓ 5 foundations consulted
Bushel writes nine.
One pass produces all nine artefacts, audience-grouped. Each one carries the same evidence trail back to the recommendation that birthed it.
bushel generate [l/2025-05-onb] ✓ Customers (3) — blog, email, changelog ✓ Support (2) — FAQ, help update ✓ Sales (2) — one-pager, demo notes ✓ Internal (2) — eng memo, roll-out state: draft
Ship the bundle.
Review, copy, hand off. Shipping freezes the bundle. Inputs change later? Bushel flags it; regenerate when ready.
> bushel ship [l/2025-05-onb] ✓ 9 artefacts frozen ✓ recommendation marked applied state: shipped
Nine artefacts. Four audiences. One source of truth.
Click any one in the unified app and the provenance panel shows you the recommendation it came from, the user stories that shaped it, the foundations consulted, and the model that wrote it.
Customers
Blog announcement
Long-form. Public. The thing your team will quote when asked what changed.
Customer email
First-person. Names the change in the subject line. Plain-text–safe.
Changelog entry
Engineering-grade summary. Two paragraphs, no marketing.
Help-centre update
Replaces the old page; preserves the deep link.
Support
Support FAQ
Five questions support is about to get. Answered before they're asked.
Macro template
Drop-in for Zendesk/Intercom. Variables interpolated from the launch.
Sales
Sales one-pager
For prospects in flight. Lifts the one line that closes the call.
Demo script update
Replaces the relevant slide narration. Timestamped from the previous version.
Internal
Roll-out plan
Phased dates, feature flag references, who owns each step.
Every line carries its provenance.
The single non-negotiable design principle of Bushel: a customer support person reading the FAQ can click any answer and see the call note it came from. A sales rep can trace the one-pager line back to the discovery moment. A product manager can see what changed in the foundations between launches.
Audience-grouped, not stack-ranked.
The launch detail surface groups artefacts by the audience that reads them, because that’s how launches actually ship.
Regenerate on input change.
If the user-story inputs change, the launch state moves to input-changed. You decide when to regenerate.
Shipped is frozen.
The friction of “unship” is intentional. Shipped bundles are quoted; they need to mean what they meant when they shipped.
One recommendation. Nine artefacts ready to ship.
Bushel is bundled with Cultivate OS. The Pro tier ships unlimited launches.