Skip to main content
Human guide: work with your agent → Build a candidate map for one account. Verify role evidence before treating someone as a buyer or decision maker.

Before you start

Use an authorized workspace and a small file with stable source IDs. Have source access and your team’s acceptance policy available. This guide describes customer-authored logic, not an automatically enabled product policy.

1. Understand the decision

A title suggests responsibility. It does not establish budget authority or support for a purchase. Test this fictional sample before calling providers:

2. Inspect supported operations

Inspect a returned ID with deepline describe <returned-id> --json. Compare required identifiers, outputs, access mode, and price. A similar title does not establish that a contract fits.

3. Implement the bounded workflow

Ask your agent to author buying-committee-mapping.play.ts using Write Plays. Have it declare the CSV input and preserve source IDs. Reuse existing contracts when they fit the transformation. Implement these rules explicitly:
  1. Define the account and the buying roles you need to understand.
  2. Resolve people and current company relationships from inspected contracts.
  3. Retain role evidence. Mark inferred authority as unconfirmed.
  4. Identify missing roles and the next introduction or question without inventing contacts.
Keep external changes disabled for the first pilot. That control belongs in the authored logic, not a universal Play dry-run flag.

4. Check and pilot

Prepare pilot.csv using CSV-safe selection. Then check the source:
Resolve authoring errors first. After reviewing source and price, run only the pilot:
Use the ID returned by the pilot. Select a returned dataset path when several exist. Provider-backed execution can incur usage.

5. Verify the outcome

Check current employment and evidence for each buying role. A useful map can still have an unknown budget owner.
Every source ID has a result or explicit exception. The fictional cases follow the stated policy, and actual results retain their evidence.
Ask your agent why a record was accepted, held, or rejected. Correct the rule before expanding input or enabling external writes.

Continue

Contact discovery covers candidates. Account planning turns gaps into actions.