Keep the context attached to the work
The assumption behind a section, the question for the client, the note for the developer, all of it lives against the exact section it affects, and none of it reaches the client.
No card needed. 2 clients and 5 quotes free forever. Unlimited teammates.
Context where it belongs
Notes on the section they affect
Add notes, dev notes, comments and open questions to any section. When a scoper flags a risk or a developer leaves a note, it sits against the work, not in a separate doc that nobody opens.
- Notes, dev notes, comments and open questions
- One level of replies to keep threads tidy
- Filtered summaries you can copy out
Custom functionality
Trade pricing needs a per-group cache. Flag before estimate is locked.
Does Acme need guest checkout at launch?
Internal by design
Never in the client PDF
Everything here is internal. Notes and questions travel with the Scope into the spec and delivery hand-off, but they are always kept out of the document the client sees.
## Ecommerce Requirements
The store supports trade and
retail customers with…
Hartley & Co, Ecommerce rebuild
…matches “trade pricing”
Trade Pricing Module
…matches “tiered discounts”
Platform comparison: Shopify vs Magento
…matches “B2B pricing”
Why it matters
Why scattered context costs you
Nothing lost
The reasoning behind a scope decision stays with the scope, so it survives into delivery.
Fewer misreads
Developers see the dev notes and assumptions in place, not in a separate thread they never find.
Safely internal
Internal context can never leak into a client PDF, so people write freely.
Questions, answered
Write your next quote in ScopeDeck
One Scope, from first quote to delivery-ready spec. Start free, no card needed.