How the assessment works
The tool chooses one 30-day experiment from your buyer, existing signal, economics, permission and ability to follow through.
1. Describe the job
Choose the buyer and the business outcome. Rough bands are enough; the assessment does not need customer names, contact lists or account access.
2. Verify the signal
Relevant social or website questions, a defined B2B account sample, measured landing-page traffic, an opt-in list, inbound calls or an active content program each lead to different checks. Unknown answers remain unknown rather than being guessed.
3. Apply hard exclusions
A path with missing permission, unsupported trigger or no follow-up owner cannot win even if other answers look strong. Software is shown only after the path reaches the site's internal 70-point review threshold.
4. Run one bounded test
The result shows why it was chosen, why other paths wait, three preparation gaps, weekly actions, a spend ceiling, a metric, a stop rule and a manual alternative.
A practical example
Suppose a small service team receives repeated website questions but has few social inquiries. If it can name the question, staff a handoff and review visitor privacy, a website response test may be more useful than social messaging automation. The result points to a small first experiment; it does not claim that any chat product will create demand.
If the same team has no reliable inquiry count or no person to answer, the assessment can choose foundation work instead: clarify the offer, place an obvious contact route and log real questions for a month. That is an actionable result, not a failed score.
How to use your result
Save or print the result, name the owner and write down the baseline before week one. Revisit the stop condition each week rather than waiting for the end of the month. When a prerequisite is unknown, treat it as a question to investigate; do not guess a favorable answer to unlock a tool recommendation.
The assessment is a planning aid. It does not verify contact permissions, platform rules, product availability or expected revenue. The methodology page explains the rules and limits in more detail.