Choose the tools around the work your team needs.

A staffing business wants to know when a former client starts hiring again. That job needs a current vacancy, the previous placement history, the right account owner and a reason to review the account. Finding a job advert alone does not complete it. Sending a message automatically adds another job with different approvals.

Write a short decision statement: “When an approved source shows relevant hiring at a former client, prepare an account brief for its owner to review.” Add what the owner will decide, where the brief should appear and what happens when the vacancy belongs to a different office. That statement lets you compare implementations on the same basis.

List what already works. Your CRM may hold a reliable ownership rule while the missing step is checking a source or resolving an uncertain match. Our seven-part system helps identify those connections without making the whole system compulsory. The workflow specification turns the trigger, decision and acceptance conditions into an implementation brief.

A CRM, ERP, applicant tracking system or shared sheet may hold part of the answer. Name the account identifier, owner and accepted place for the next action. If the same business appears in two systems, establish how those records are matched before adding another connection.

Keep ownership at field level. Finance may own billing details, the account team may own the relationship and an external source may supply a dated observation. A newer website result should not silently replace an approved customer record. The shared customer data guide explains how to separate identity, source priority and changes across tools.

In a demonstration, change the account owner, run the same input twice and interrupt a connection. Ask to see the resulting records. A useful demonstration shows where the work lands and what remains unresolved, as well as the successful first run.

An enrichment waterfall tries approved sources in sequence until it finds a usable result or reaches a stopping point. That sequence needs a definition of usable: the correct company or person, the needed field, a source and a date. An available email address does not establish a reason or permission to contact its owner.

Use a mixed sample of known accounts, difficult matches and records with missing details. Count correct results, wrong matches, unresolved cases and the cost of accepted information. Keep missing and wrong separate: an empty field can ask for review; a confident result for the wrong company can send the rest of the workflow in the wrong direction.

The CRM enrichment evaluation turns that sample into a repeatable comparison. Include the human time needed to verify a match, not only the price per lookup.

Use a fixed workflow when you can describe the steps and branching rules in advance. An agent can choose intermediate steps within a task. Anthropic explains this distinction between predefined workflows and agent-directed work. Choose the freedom the particular task needs.

“AI sales agent” is too broad to approve. Separate research, brief preparation, CRM updates, scheduling and sending. A research assistant may need to choose which approved page to inspect next, while an ownership update can follow a fixed rule. Neither requires authority to change prices or make commitments to a customer.

Use an agent where that bounded choice is useful and testable. Write its operating contract before giving it tools. If the output cannot be checked, adding more freedom makes the operating problem harder to contain.

Give each connection only the records and operations required for the agreed task. Reading an account, preparing a draft, editing an owner and sending a message are separate permissions. A review button is useful only if the underlying system also prevents an unapproved write or send.

OWASP’s excessive-agency guidance calls for constrained capabilities and permissions, with authorisation enforced outside the model. In this brief, the research component may read approved sources and save a draft; it cannot send outreach or alter commercial terms.

Check the reviewer’s access too. A brief should not expose a customer document to someone who could not otherwise read it. Keep credentials out of prompts, briefs and logs, and identify who can revoke the connection if its owner leaves.

Before enabling outreach, name the audience, source of contact details, relevant markets, exclusions, suppression process and person responsible for replies and stop decisions. A positive account signal is an input to that review, not an instruction to send.

Authentication and delivery monitoring also need an owner. Google’s sender guidelines concern delivery to personal Gmail accounts; they do not establish permission to contact someone or guarantee an inbox placement. Use the sending-readiness record to keep technical checks and recipient decisions visible.

Test a correct account, a duplicate observation, stale information, a missing owner and conflicting company identities. Agree the expected result for each case before the demonstration. An unresolved item that reaches the right review queue can be a correct result; an invented answer cannot.

Also try a forbidden action. A source page telling the agent to send a message should not expand its authority. Confirm that rejected operations leave the protected fields unchanged. If a connection fails after a write may have occurred, the result must stay uncertain until the operator checks the destination; a failed response is not proof that nothing changed. Give the operator the request reference and a clear recovery step.

Keep the inputs, observed outputs, reviewer and decision with the handover. A supplier’s general feature list cannot show whether your particular records and exceptions have passed.

Compare the full cost of implementation and operation: licences, data, usage, human review and maintenance. Identify who pays each subscription, controls credentials, can export records and handles provider changes. Include the time needed to investigate held cases.

Name the person responsible for the complete handover, even when several tools are involved. They need to know how to pause the workflow, find exceptions and recognise a change that needs testing. Give them the operating record with the configuration and handover.

Choose the commercial scope separately from the tool. A Build campaign combines the agreed research, setup, outreach operation and improvement. A standalone connection or custom working tool receives its own scope and quote; AI Workflows covers bounded AI tasks. If an inherited setup needs investigation before its scope is reliable, agree a paid Plan assessment first. The starting prices for Build and AI Workflows apply to their defined offers; bespoke software is quoted for its own scope.

Choose delivery responsibilities separately. We can hand research and account evidence to your team, operate agreed outreach or share the work. A tool choice should support that arrangement. The working agreements explain scope, ownership and handover.