Practical guide

Project or opportunity: separate delivery from selling

Last materially reviewed 2026-09-20

Quick answerUse the commercial record for the buying decision and the delivery record for the accepted commitment.
What to know

Different records answer different questions

An opportunity asks whether a particular purchase will happen and what decision is needed next. A project asks how an accepted piece of work will be carried out. Keeping those meanings separate helps the team avoid forecasting delivered work or treating a possible sale as an active delivery commitment. Capsule documents both concepts, but a product label alone cannot enforce your operating distinction. Write the rule before deciding where every task should live.

What to know

Use the acceptance boundary

Before agreement, actions may clarify requirements, scope or commercial approval. After acceptance, actions fulfill the promise and manage changes. A customer can have both kinds of work at the same time, so keep the relationship context shared while separating the commitments. A new discussion does not require overwriting the existing project, and a delivery issue does not automatically mean the commercial opportunity should be reopened. Record the actual business decision rather than using status changes as shorthand for everything.

What to know

Check closure effects

Closing a record can change how related tasks appear or behave. Review the current Capsule documentation and test the intended path before relying on it. A task that seems missing may still exist in a different context or inactive state. Do not immediately create a replacement. Preserve the original identifiers and inspect the linked record’s status. This is especially important when an automated handoff or a covering colleague depends on the visibility of the next action.

What to know

Keep the handoff small and clear

Move only the information needed to start delivery responsibly, while retaining access to the original agreement. Name the delivery owner and first action, then keep later changes tied to the accepted scope. If the project requires capabilities beyond the CRM’s supported workflow, maintain a clear boundary with the delivery system rather than claiming the CRM replaces it. Continue to sales handoff and change control for the practical details that make the distinction useful in daily work.

Continue when useful

Next: Move a won deal into delivery without losing the promise

Carry the agreed scope, owner and first delivery action into the project; won does not mean delivered.

Open Move a won deal into delivery without losing the promise →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Capsule projects — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20
  2. Capsule opportunity stages — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20