Review the designed inputs in the fit finder, then adapt them to your own team.
Open this example in the fit finderThe first practical move
Assign a person and define the minimum record: source, context, status and next action. Run five items manually, including a stop request and an exception.
Why the category boundary matters
The fit finder returns process first when the reply owner is missing. It does not recommend buying a provider. Create the operating routine before comparing categories.
What the pilot should measure
Owned records, missed handoffs and the ability to recover an exception.
This is a designed example, not a report of customer use, provider testing or measured performance. Replace the assumptions with your actual conditions before making a purchase.
The assumptions used in this example
These are designed inputs, not a measured customer case. Every assessment answer is listed below. Review the assumptions in the fit finder and change them before applying the plan to your team.
Scroll horizontally to read all columns.
| Assessment input | Illustrative answer |
|---|---|
| What job needs to improve? | Qualify new enquiries |
| Who is on the other side? | Consumers |
| Where does the work start? | Social comment or direct message |
| How many relevant items per month? | 101–500 |
| How long does a decision usually take? | Under 14 days |
| Where is the current record? | There is no shared record |
| Is the contact basis documented for this task? | Documented and reviewed for this task |
| What information is missing? | Conversation context |
| How can records move between tools? | Manual entry |
| Who owns replies and exceptions? | Nobody is assigned |
| What is the monthly software budget? | $100–$300 |
| Capabilities already available | None selected |
| Separate production tasks | None selected |
Trace one item through the workflow
A team wants social qualification automation, but no person owns replies and there is no shared record. The fit finder returns process first. The designed example deliberately produces no provider candidate; choosing an automation product is not the current acceptance condition.
A practical setup sequence
- Assign an operator who can handle normal responses, exceptions and stop decisions.
- Create the minimum shared record for source, context, status, owner and next action.
- Agree coverage and a visible queue for unattended items.
- Handle a small varied sample manually, including a duplicate and an uncertain request.
- Return to the assessment only after the operating gaps have a demonstrated solution.
The working record
Scroll horizontally to read all columns.
| Part of the record | What must remain visible |
|---|---|
| Reply owner | The named person responsible for the actual response |
| Shared record | A location the next operator can access and maintain |
| Exception route | What happens when nobody can decide immediately |
| Review evidence | A completed manual sample with failures and recoveries recorded |
What would stop the pilot
Keep new campaigns and integrations off while items can become unowned. A form naming a team is insufficient unless someone actually covers the responsibility and can recover missed work.
Count assigned records, missed handoffs and recovered exceptions. Buying no new software is a useful result while those foundations are being established.
Working files
Blank templates for your own planning. These contain no customer records and are not submitted to Sales Fit Lab.
Use the blank fields for your own task, owner, exception and acceptance conditions.