Practical guide

Contact, company or opportunity: model the right thing

Last materially reviewed 2026-09-20

Quick answerA person, an organization and a possible purchase are different records with different lifetimes.
What to know

Give each record one job

A person is someone you communicate with. An organization supplies shared business context. An opportunity describes a particular possible purchase. These records may be connected, but they should not be interchangeable. Capsule documents contacts and opportunities; this guide adds an editorial rule for using them coherently. Start with the meaning of the information and then map it to supported product fields. Do not let an import file’s existing shape dictate the whole operating model.

What to know

Work through a repeat-customer example

North Pier has two contacts and is discussing a second project. Keep the organization context shared, retain the two people as distinct contacts and create a separate opportunity for the new decision. The previous project’s outcome should not be overwritten by the new sales stage. A colleague should be able to distinguish “we know this company” from “this particular purchase is likely.” This example is fictional and intended to expose modeling choices, not prescribe every team’s exact configuration.

What to know

Avoid duplicated responsibility

If the same next action appears on several records, decide which is authoritative. A note on the company can summarize context while the opportunity carries the specific sales task. Do not create several copies merely to make the action visible everywhere; they can later disagree. Instead, test the supported views and links colleagues use to find the relevant record. Where the product cannot show a needed relationship, document the limitation before relying on it.

What to know

Use the model as a migration rule

Write a short rule for incoming rows: what creates a person, what represents an organization and what deserves a separate opportunity. Include ambiguous cases and an exception owner. That rule becomes useful during imports, onboarding and cleanup. Revisit it when the business introduces a genuinely different process, not every time someone wants a new column. A stable model reduces the need for later merges and makes repeat-customer work easier to understand.

Continue when useful

Next: The minimum useful CRM field set

Start with fields that change an action or prevent a mistake; leave decorative data out.

Open The minimum useful CRM field set →

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 contact management — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20
  2. Capsule opportunity stages — Merchant documentation · capsulecrm.com · Merchant-controlled · checked 2026-09-20