Qualify the job before the account
A promising social media management lead needs more than a company in the right sector. Confirm the job: client approval arrives after the scheduled publishing time. Identify writers, designers, and account owners reviewing posts as the possible user group, then find who can authorize a pilot; the working buyer hypothesis is a social lead managing several brands or client accounts.
Ask about the current workaround, a content calendar spreadsheet with approvals spread across messages, and what would make changing it worthwhile. Do not assign a budget or procurement timeline from company size, funding, or job title alone.
Use a category-specific qualification rubric
Use the calculator below to organize your judgment after reading the source. Unknown evidence should remain unknown. Its weights are a transparent prioritization convention, not a prediction of purchase probability.
| Dimension | Evidence to seek | Reason to pause |
|---|---|---|
| Problem | Who must approve text, visual assets, and timing for each account? | The person cannot describe a recent instance of the problem. |
| Product fit | Can you prepare one week's draft posts for a single brand and rehearse an approval change? | buyers expecting guaranteed reach, follower purchases, or unsupported social-network automation |
| Timing | the team takes on additional clients with different approvers | The proposed change has no confirmed date or relevance. |
| Implementation | Which channels need direct publishing versus an export for manual posting? | channel support and permissions vary; verify the exact supported publishing action |
| Value | the current approved version and responsible publisher are unambiguous before its scheduled time | The buyer and user disagree on what success looks like. |
Work through an illustrative assessment
Suppose the source says: “Three clients approve copy in different chat threads and we keep missing changes. Looking for a calendar with clear approval status.” That supports investigating the problem, but it does not yet settle purchasing authority or technical compatibility. A reviewer should ask the two discovery questions above and preserve the answers beside the source.
Compare that with: A creator asks how to buy followers. This weaker example should not receive the same pain or timing score. A relevant public topic is not evidence of a current evaluation.
Even a strong problem signal should be rejected when the need belongs to buyers expecting guaranteed reach, follower purchases, or unsupported social-network automation. Qualifying out prevents a misleading promise and preserves time for a prospect the product can help.
Create a reviewable handoff
A qualified opportunity should contain the original evidence, a summary of the job, confirmed and unknown constraints, the buyer/user distinction, and an agreed next step. Keep a score attached to those facts so another teammate can challenge the conclusion.
Propose a pilot only when the critical gap is addressed: channel support and permissions vary; verify the exact supported publishing action. Evaluate the pilot through a real observation that the current approved version and responsible publisher are unambiguous before its scheduled time, and keep that observation separate from the initial qualification score.
About these playbooks and examples
Prepared by DemandBolt with AI assistance as practical planning resources for people building and selling software. The category scenarios and message examples are illustrative, not quotations from real prospects or claims of customer results. Adapt the hypotheses to your product, verify original sources, and review capabilities before making an offer.
The workflow follows our first-customer guide and buying-signal review method. Our PyInvesting and Rae records distinguish actual internal work from targets. Published .