# Lead Intake Sprint Kit

Use this kit to decide whether one lead workflow is ready for a USD 100 automation sprint.

Do not paste regulated, medical, legal, financial, or sensitive customer data into public forms or chats. Use synthetic or anonymized examples until scope and permissions are clear.

## 1. Workflow Snapshot

Lead source:

Current destination:

Current follow-up owner:

Average leads per week:

Current response time:

Most common failure:

- lead not logged,
- duplicate record,
- delayed follow-up,
- missing context,
- no next action,
- no audit trail,
- other:

## 2. Example Lead

Use fake or anonymized data.

```text
Name:
Email or identifier:
Company:
Source:
Message:
Requested service:
Urgency:
Known context:
```

## 3. Desired Output

What should exist after the workflow runs?

```text
CRM or spreadsheet row:
Internal summary:
Suggested next action:
Follow-up draft:
Owner notification:
Audit row:
```

## 4. Minimum Field Map

```text
lead_id
source
received_at
contact_name
email_or_identifier
company
request_summary
urgency
missing_info
next_action
owner
status
audit_timestamp
```

## 5. AI Summary Schema

```json
{
  "qualified": true,
  "reason": "One sentence based only on supplied data.",
  "urgency": "low | medium | high",
  "internal_summary": "Max 60 words.",
  "missing_info": ["field or question"],
  "suggested_next_action": "One clear action.",
  "follow_up_draft": "Human-review draft with no invented claims."
}
```

## 6. Duplicate Rule

Choose the first safe duplicate check:

- email exact match,
- phone exact match,
- company + contact name,
- source lead ID,
- manual review when confidence is low.

## 7. Review-Before-Send Rule

Early AI follow-up should produce drafts, not automatic customer messages.

Automatic sending should only be enabled after:

- the prompt has been tested on real examples,
- the buyer approves allowed and forbidden claims,
- failure handling is visible,
- the workflow has a clear owner,
- sensitive or regulated data risks have been reviewed.

## 8. Starter Sprint Acceptance Criteria

A USD 100 starter sprint is complete when it delivers:

- one current-state workflow map,
- one field map,
- one AI summary/follow-up schema,
- one proof-of-flow, implementation spec, or executable SOP,
- handoff notes with limits and next recommended improvement.

Production implementation, paid tools, complex API access, or automatic outbound messaging should be scoped as a separate implementation sprint.