SALES OPPORTUNITY REVIEW · Workflow idea

Use company research to inform a pipeline, without letting a signal make the sales decision.

Prepare a proposed sales record when public company technology observations may relate to a team’s offerings. Keep the source, evidence, and qualification rationale visible, ask a salesperson to verify that the organization is a suitable prospect, and require approval before adding shared records, contacting anyone, making a quote, or committing money.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A possible company opportunity needs qualification
Produces
A proposed sales record with company context, technology evidence, source links, qualification notes, owner, and approval status.
Category
Sales

01 / The starting point

A clear request.
A useful direction.

A verified company research record and an approved description of the offering or business need

“Prepare a proposed lead record from company technology evidence and require human review before pipeline entry, outreach, or any commercial commitment.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps sales teams turn relevant company research into opportunities for a person to assess, rather than treating a data point as a qualified lead.

  1. Confirm the company and business purpose

    Check that the organization is within the approved market and that the proposed use of its information is appropriate.

  2. Review technology evidence and sources

    Verify relevant observations, their age, and their connection to the company before treating them as a potential business signal.

  3. Prepare a proposed lead record

    Summarize the evidence and reason for consideration without adding unsupported needs, budgets, or buying intent.

  4. Qualify the prospect and check contact permissions

    Have a salesperson review fit, verify any business contact, and check source restrictions, consent requirements, and opt-outs.

  5. Approve pipeline entry and commercial actions

    Require the responsible owner to approve the record and exact recipient before outreach, and separately approve any quote, purchase, contract, or financial commitment.

03 / The result

Something useful.
Something to build on.

A proposed sales record with company context, technology evidence, source links, qualification notes, owner, and approval status.

AmbactiWorkflow folio · 5 steps

Review technology-based sales leads

Sales · Example outcome

The handoff

A proposed sales record with company context, technology evidence, source links, qualification notes, owner, and approval status.

Keep in mind

Technology observations may be wrong or unrelated to a company’s needs, and business contacts may have privacy and contact preferences. Verify each source and prospect record, honor consent requirements and opt-outs, and require an authorized owner to approve the exact lead and any recipient before outreach. Pricing, discounts, purchases, contracts, and other financial commitments always need separate human approval.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Define a suitable prospect and lead evidence

Document which markets, offerings, company signals, and evidence are relevant enough for a person to review.

Set record and contact safeguards

Keep sources and dates visible, minimize personal data, honor restrictions, and define how duplicate or weak prospects are handled.

Establish pipeline and outreach approvals

Specify who may accept a proposed record, approve a recipient and message, and authorize changes to a shared sales record.

Set financial approval boundaries

Keep prices, discounts, purchases, contracts, budgets, and other commitments with authorized commercial or finance approvers.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗