# The relationship after the sale

Almost everything continues. The same Person carries the research, the conversations, the deal and now the cases; the identities, the timeline, the memory and the open commitments all survive the sale untouched. What changes is the lifecycle stage, the deal's place on the pipeline, what Connect is being asked to do next, and how this person is treated by prospecting.

- **Status:** Available
- **Audience:** both
- **In the app:** #/relationships, #/timeline
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/support/post-sale/

## The continuity is the product

A business that runs sales in one system and service in another spends the first five minutes of every post-sale conversation reconstructing what the customer already told somebody. Connect avoids that by never creating the second record: the relationship that held the prospect research is the relationship that holds the case, and the timeline runs straight through the sale without a join in it.

That is why lifecycle stage exists as a field on a person rather than as a location. Moving from prospect to client is a fact recorded about somebody, not a migration of their history into a different place, and it is reversible in the way a fact is — you correct it — rather than in the way a migration is, which is usually not at all.

## What continues unchanged

| Thing | What survives | Where you see it |
|---|---|---|
| The Person and their identities | Every address on every channel still resolves to the same human | The relationship record |
| The timeline | Calls, messages, deals and events in one order, before and after the sale | The customer timeline |
| Memory | What Connect knows about this person and this business, at every tier | Memory, and every answer grounded in it |
| Open follow-ups | Commitments keep their reason and their due time; winning a deal cancels nothing | The follow-ups screen |
| Knowledge grounding | Answers are still bounded by what the workspace supplied | Every reply, on every channel |
| Autonomy | The per-channel rule for what Connect may do is unchanged by the sale | Connect Rules |

## What changes

1. **The lifecycle stage moves.** A stage change is its own action with its own record, and it is what the rest of the workspace reads to know who this is now.
2. **The deal closes.** The opportunity leaves the open pipeline as won, keeping its value and its history; the relationship keeps the deal.
3. **The next action changes shape.** Outreach was the work before; the work after is answering, onboarding and keeping the commitments already made.
4. **Prospecting must stop treating them as new.** A discovered organisation that is already a customer is an existing relationship, and telling those two apart is a job the research path does before it spends anything on them.

That fourth point is the one that embarrasses a business in public. Cold-approaching a customer you have had for a year is a specific, recognisable failure, and it is caused by prospect discovery and the relationship store not agreeing about identity rather than by anybody deciding to do it.

## What is deliberately not relaxed

**Commercial safety** — A price, an SLA or a warranty that Knowledge does not support is still refused and escalated. Being a customer does not make an improvised term safe — it makes it more expensive.
**Suppression and do-not-contact** — A client who unsubscribed is still unsubscribed. The relationship does not override the instruction they gave.
**Approval rules** — If the channel says a person decides, a person still decides. Familiarity is not authority.
**Isolation** — The relationship belongs to exactly one workspace, before and after the sale, enforced independently three times over.

## Reading the relationship afterwards

Two views answer most post-sale questions. [Customer 360](/docs/relationships/customer-360/) puts one person's whole history in a single place — every channel, the deals, the cases, the commitments — and the [relationship summary](/docs/relationships/relationship-story/) writes it as prose, with names scrubbed on the way out, for the times somebody needs the shape of an account rather than its rows.

Both read the same store, which is the point. There is no post-sale copy of the customer that could drift from the pre-sale one, because there was never a second copy to drift.

## Questions

### Do open follow-ups survive a deal being won?

Yes. A commitment has its own reason and due time and nothing about closing a deal cancels it. If a chase no longer makes sense after the sale, cancel it explicitly and record why.

### Will Connect prospect a company that is already a customer?

It should not, and separating a genuinely new prospect from an existing relationship is work the research path does deliberately. If it happens, treat it as an identity-resolution problem rather than a targeting one.

### Does becoming a client change what Connect may say about price?

No. Commercial terms are bounded by Knowledge for everybody. An ungrounded price is refused and escalated to a person whether the recipient is a stranger or a customer of ten years.

## Related

- [Support in Connect](https://connectbyjbrh.com/docs/support/)
- [Onboarding a new customer](https://connectbyjbrh.com/docs/support/onboarding/)
- [Lifecycle stages](https://connectbyjbrh.com/docs/relationships/lifecycle-stages/)
- [Customer 360](https://connectbyjbrh.com/docs/relationships/customer-360/)
- [Closing a deal: won and lost](https://connectbyjbrh.com/docs/sales/won-and-lost/)
- [Telling a new prospect from an existing customer](https://connectbyjbrh.com/research/prospect-identity-resolution/)

## What this page is based on

- `docs-source/sources/CHANNELS.md` §5 — one Person, lifecycle stages and the relationship console
- `docs-source/sources/CHANNELS.md` §6 — `safe_sales.py` and closing a deal
- `docs-source/sources/GENERAL.md` §10 — isolation and suppression rules that do not relax
- Connect capability registry (docs-source/facts.py) — `lifecycle_stage`, `customer_360`, `suppression_dnc`