Sales operations
Lead qualification & outreach drafting
Research pilot — simulated example, not a live deployment
Assess inbound leads against your customer criteria and prepare an outreach draft with the reasons behind the match.
See an input and its handoff
Compare the expected behavior in a routine case and an exception.
Agreed rule
Qualify only when the required customer criteria have evidence.
Matching lead
A fit assessment with reasons a salesperson can inspect.
Example input
- Company
- Example Studio · 12-person agency
- Request
- We need owned agent backends for three client workflows.
- Sample criteria
- Agency team · client backend need · source ownership required
Illustrative output
- Fit score
- 3 of 3 sample criteria matched
- Evidence
- Agency team, client workflows, and source ownership are stated in the request
- Outreach draft
- Which client workflow would you like to start with? We can use its requirements to outline the backend spec and handoff.
The human handoff
A salesperson verifies the fit and edits the draft before sending. No outreach is sent by this example.
Missing context
An incomplete lead stays open for clarification.
Example input
- Company
- Not provided
- Request
- Interested in agents. Can you send more information?
- Sample criteria
- Agency team · client backend need · source ownership required
Illustrative output
- Fit score
- Not scored · insufficient evidence
- Missing details
- Team type, intended workflow, and ownership needs
- Outreach draft
- What kind of work would you like an agent to handle, and is it for your team or a client?
The human handoff
A salesperson reviews the clarification draft. Keep the lead unqualified until the missing details are checked.
How this agent would work
Check the evidence
Read the submitted company details and compare them with the agreed customer criteria.
Explain the fit
Score the available evidence and call out missing information that could change the assessment.
Draft the first touch
Prepare a relevant outreach message for a salesperson to check, edit, and send.
Where human judgment stays
- The score reflects the criteria in the spec, not a prediction that a lead will buy.
- Missing company information stays unknown until someone verifies it.
- A salesperson approves outreach. This example does not send messages or enroll leads in campaigns.
When you build your version
A backend you can inspect and own
- Approved spec
- Define your ideal customer profile, scoring criteria, required evidence, and when a salesperson must review a lead.
- Backend/API
- A generated FastAPI backend, packaged as a versioned artifact. Review its configuration, integrations and deployment requirements for your environment.
- Source code
- Download the project code to inspect, change and run in your own environment.
- Validation results
- Evidence tied to the artifact version and the checks actually run. Include clear matches, missing company details, conflicting evidence, and outreach drafts that must stay unsent in the test plan.
No validation report is provided for this pilot. The scenarios above illustrate expected behavior, not passed tests.
Read what Axtra validates