Use case · Sales prospecting

Build the next prospecting list before a territory or campaign opens

When a team cannot explain why an account entered the list, reps spend the launch week checking firms, finding the right roles and removing CRM accounts by hand. Revenue, account and data owners can review one boundary, account reason, role gap, relationship route and hand-off before the list reaches the sales system.

Read the Sample Brief

Buyer-owned target-market brief · TM-14

Review organisation-led software accounts for one regional service operations campaign

Local sample · Reviewed 14 August 2026

Account unit: Organisation – not a site, asset, programme or customer
Exact Search fields: Country: United Kingdom or Germany · Industry contains Software · Employee count: 50–500
Buyer-owned judged tests: Does available text support a current move to regional service operations? Can the team review an operating owner and a technical reviewer?
Exclusions: Existing accounts and active opportunities from the buyer’s CRM. Relationship strength, inferred intent and contact permission never count as account fit.
Source scope: Graph One’s available organisation and person fields, plus buyer-owned CRM exclusions and any approved account source agreed for the work
Owner and reviewer: Maya Chen · Revenue Operations · Samir Khan · Account Executive
Output: One reviewed account Table with reasons, buying-group gaps, route context, reviewer, owner and a sales-system hand-off plan

Buyer labels define this brief. The revenue team checks account fit, buyer authority, buying intent, interest and contact permission before any sales action.

01 · Exact boundary

Let hard fields narrow the market, not decide the account

Use only supported fields for the first set. TM-14 uses Country, Industry and Employee count. Existing-account and active-opportunity exclusions still come from the buyer’s CRM.

Atlas Systems · Local sample

The sample fields meet these exact rules. The revenue team checks account need, CRM state and the buying-group case next.

02 · Buyer-owned judgement

Show why the account stayed in, stayed uncertain or stayed out

Search can place the buyer’s questions beside each account and keep a reason for review. A human decides whether the evidence is enough.

03 · Evidence at the point of use

Make the account reason open to challenge

Carry the value, source class, checked date, open gap and reviewer together. Do not turn missing coverage into a positive signal.

TM-14 · Traceable account record

Atlas Systems stays in review

The exact sample fields meet the Search boundary. The judged case remains partial, and the buyer’s CRM exclusion is still open.

Decision · Keep in review

FieldValue or review reasonSource classCheckedOpen gapReviewer

Field

Country

Value or review reason

United Kingdom

Source class

Local sample organisation field

Checked

14 August 2026

Open gap

Live source and account coverage must be agreed

Reviewer

Samir Khan

Field

Industry

Value or review reason

Software development

Source class

Local sample organisation field

Checked

14 August 2026

Open gap

Product need still needs buyer evidence

Reviewer

Samir Khan

Field

Employee count

Value or review reason

184

Source class

Local sample LinkedIn company field

Checked

14 August 2026

Open gap

Freshness and approved source still need review

Reviewer

Maya Chen

Field

Judged account reason

Value or review reason

Available sample text describes multi-site service workflows. It does not show a current change programme.

Source class

Local sample account description

Checked

14 August 2026

Open gap

Current operating change remains unproved

Reviewer

Samir Khan

Field

CRM exclusion

Value or review reason

Not supplied in this page sample

Source class

Buyer-owned CRM field

Checked

Open

Open gap

Existing-account and active-opportunity check required

Reviewer

Maya Chen

These are local sample values, source classes and dates. A live review uses only fields the account can access and sources the buyer has approved. Missing coverage stays visible; it does not become a positive fit signal.

04 · Joined account and people

Replace the lone contact with a useful role map

Open the same organisation profile, then label several relevant roles for this brief. Current titles are available profile fields; a role in the buying group is the buyer’s judgement.

A

Atlas Systems

Account under review · Local sample

TM-14 · Exact boundary met · Judged case remains partial

Organisation profile · Sample data

Likely operating owner: Alex Morgan · Buyer-labelled · Authority unknown
Likely technical reviewer: Priya Shah · Buyer-labelled · Authority unknown
Commercial approver: Open role · No reviewed person

Current Graph One organisation profile identity and tabs · Local sample fields checked 14 August 2026. Source coverage and available roles vary by account.Swipe the tab row or use its arrow keys to review each section.

Atlas Systems · Buyer-labelled role map

Two people to review, one role still open

Reviewer · Samir Khan

01

Likely operating owner

Alex Morgan

Current role: Operations Director · Local sample profile
Source and date: Available person role field · checked 14 August 2026
Open gap: Authority, need, interest and contact permission are unknown

02

Likely technical reviewer

Priya Shah

Current role: Director, Enterprise Systems · Local sample profile
Source and date: Available person role field · checked 14 August 2026
Open gap: Project role, authority and technical approval are unknown

03

Commercial approver

Open role

Current role: No person reviewed in the local sample
Source and date: Buyer-owned role requirement
Open gap: Named person, current role and authority are missing

Graph One shows available people and roles. The buyer labels their part in this brief and reviews each gap. The sample does not infer a complete buying group or prove authority.

05 · Relationship evidence after account and role review

A route can inform the next check, never establish fit

Inspect visible evidence on both legs only after the account and person remain worth research. The team still decides whether it may ask.

AM

Alex Morgan

Operations Director · Atlas Systems · Local sample

Person profile · Sample data

SummaryNotesInteractionsMutual Connections

Whom could you ask?

Check the evidence on both legs before making the ask.

You Via Target

ViaMe – ViaVia – TargetPath contextAvailable contact context

MC

Via

Maya Chen

Me – Via

Strong

Via – Target

Medium

Path context

Direct on both legs · Team-shared record

Available contact context

Meeting metadata · 6 Aug 2026

OR

Via

Owen Reed

Me – Via

Medium

Via – Target

Weak

Path context

Second-degree path · Team-shared record

Available contact context

Email metadata · 18 May 2026

Shown relationship strength is evidence; Graph One does not choose whom to ask.Swipe the profile tab row to see every section. Compare both routes, then choose whom to ask

06 · Reviewed Table output

Give the account one owner before it enters sales work

Keep the reason, people, route, gap, reviewer, owner and next work on one account row. Views and comments help the team return to the same decision record.

The joined gain

Keep the reason with the account after Search ends

An export can start a list, and the CRM stays the buyer’s formal sales record. The gain shown here is one joined research record: exact bounds, judged reason, people, relationship route, source date, evidence gap, reviewer, comments, owner and next step remain with the account.

Graph One complements approved account data and CRM. It does not replace either one or claim a ready sync.

Compact account record

Phone proof

Brief: TM-14 · Organisation-led software account review
Account: Atlas Systems
Boundary: UK · Software development · 184 employees · Local sample
Review reason: Multi-site service workflow text is available; current operating change is not proved
Decision: Keep in review – not sales-ready
Buying group: Alex Morgan · Priya Shah · Commercial approver open
Route: Via Maya Chen · Hold for her review
Source and checked date: Local sample fields and metadata · 14 August 2026
Open gap: CRM exclusion, authority and contact permission
Reviewer: Samir Khan
Owner and next work: Maya Chen · Check buyer CRM and route context
Sales system: Target and hand-off method to agree

Reviewed account Table · Local sample

07 · Owned hand-off

End the research record where the buyer’s sales process begins

State who supplies each field, what Graph One keeps joined and which formal system owns sales action. Any movement between systems needs an agreed method.

Graph One holds

The reviewed account set, exact Search document, reasons, people, route context, sources, dates, gaps, reviewer, owner, comments, next work and Views.

Buyer and approved sources supply

CRM exclusions and status, approved account fields, source rights, role requirements, contact rules and any sector-specific facts used in the brief.

The buyer’s sales system owns

The approved account and contact record, permission, campaign or sequence, outreach, response, opportunity and formal sales outcome.

Any agreed hand-off keeps account ID and name, review reason, person and role, route context, source and checked date, open gap, reviewer, owner and next step. The target system and method form part of the scoped sale. This page does not claim a ready connector, sync, export, write-back, sequence or automated workflow.

Graph One Agreed hand-off Sales system

Local sample access: Maya can edit and comment; the account research team can view and comment; public link is off.

The buyer sets real viewers, source rights, identity, retention, offboarding, deletion and contact controls in the agreed scope.

Change the brief, not the proof rule

Five settings, five honest adaptations

The main sample covers an organisation-led software campaign. Other settings need a different account unit, buyer fields, role map and formal boundary.

01

Technology and software

Brief unit · Organisation

Buyer or approved source: Product, customer, usage, security, revenue, stage and intent
Role map: Commercial owner · Technical reviewer · Approver
Sales boundary: CRM owns contact, campaign and opportunity state

02

Manufacturing

Brief unit · Plant or site plus organisation

Buyer or approved source: Plant, line, process, equipment and supplier status
Role map: Plant owner · Engineering · Procurement
Sales boundary: CRM or plant process owns approved sales work

03

Healthcare

Brief unit · Approved care setting plus organisation

Buyer or approved source: Provider scope, procurement and contact controls
Role map: Service owner · Technical reviewer · Procurement
Sales boundary: No patient, clinical, outcome or permission claim

04

Banking and capital markets

Brief unit · Approved client or market entity

Buyer or approved source: Restricted-source, conflict, risk and contact checks
Role map: Coverage owner · Operations · Controlled approver
Sales boundary: Authorised bank process owns every contact decision

05

Energy and utilities

Brief unit · Asset or programme plus organisations

Buyer or approved source: Programme, grid, market and performance facts
Role map: Programme owner · Technical buyer · Commercial approver
Sales boundary: Buyer system owns stakeholder action and formal outcome

Exact first meeting test

Define the territory, fields and hand-off before prospecting starts

Bring the revenue owner, daily account reviewer and the data or CRM owner. Name the account unit, required fields, exclusions, role gaps, approved source scope and the sales system that owns the next action.

We will test: Exact supported fields, buyer-owned judged questions, exclusions, source and date coverage, buying-group gaps, route evidence, access, reviewer, owner and the target sales-system boundary.
The meeting returns: One target-market brief and a field-level plan for a reviewable account Table and owned sales-system hand-off – not a qualified account, complete buying group, contact permission, ready sync, pipeline result or sales outcome.