**Module:** Discuss

Threaded discussions on tasks, sales orders, and invoices keep context attached to the work so collaboration happens naturally.

## Copy

Collaboration becomes difficult when context gets lost. A decision made in a meeting isn't connected to the project it concerns. Feedback on a deliverable doesn't travel with the file. A question about an invoice sits in an email thread that nobody can find later. This context loss forces collaborators to reconstruct what happened instead of building on it. The work of collaboration becomes the work of reconstruction.

This module keeps context attached to work. Threaded discussions on tasks, orders, and invoices travel with the records they concern. Feedback and decisions stay in context. New team members can follow the full history of any item. Collaboration happens naturally because context is preserved where work lives, not lost in separate communication channels.

For copywriters: Focus on the context loss problem—how collaboration suffers when the history of decisions and feedback disappears. Position threaded discussions as the mechanism that preserves context. The audience should recognize the reconstruction work their teams do daily because context wasn't preserved.

## Ideas

- **Angle:** Preserve collaboration context—threaded discussions that keep decisions and feedback attached to work
- **Audience:** Team leads, project managers, operations directors, cross-functional teams
- **Pain points:** Lost context, reconstruction overhead, scattered feedback, history gaps, collaboration friction
- **Outcomes:** Preserved context, searchable history, natural collaboration, new member onboarding, reduced rework
- **Vertical spins:** Creative agencies (creative feedback), software teams (feature discussions), professional services (engagement history), legal (case collaboration)