Track quality as well as inquiry volume
Track the inquiries that follow a paid skill purchase, then assess their fit, preparation, and eventual outcome. Keep the buyer's prior relationship and reported reason for contacting you alongside any recorded product activity. This gives you evidence about the role your product plays without assuming it caused every later consulting engagement.
A companion can have several commercial jobs. It may earn revenue independently, help readers prepare for consulting, or simply introduce your method to people who will never need personal advice. Choose which question you are evaluating before you build a dashboard.
For an author who wants more suitable consulting work, the useful question is: “Are the inquiries associated with this product the kind of engagements I want, and what do I know about how they arrived?”
Define a qualified inquiry in ordinary language
An inquiry is a person asking about your services. A qualified inquiry meets your stated criteria for a possible engagement. An accepted engagement is work you have agreed to undertake. A product purchase is none of those things automatically.
Write a short qualification rule before classifying records. For a fictional author who advises small cultural organizations, the rule might be:
The requested work is within my audience-research expertise; the organization has a responsible contact, a specific question, a plausible project timeframe, and a budget conversation it is willing to have.
This is an illustrative business definition, not an industry standard. Add criteria that genuinely determine whether you would consider the work. Avoid awarding points for superficial enthusiasm or for purchasing your product alone.
Record “unknown” when you have not established an answer. Do not silently label every unanswered inquiry unsuitable.
Copy the inquiry ledger
Use one row per distinct consulting opportunity, with a stable identifier. If the same person emails and then books a call about the same project, update the row instead of counting two leads.
| Field | What to record | Why it matters |
|---|---|---|
| Inquiry date and ID | When this opportunity first appeared | Defines the cohort you are reviewing |
| Prior relationship | New contact, reader, former client, existing prospect, or unknown | Separates new relationships from people already likely to inquire |
| Product connection | Purchased, used, mentioned, gifted, or unknown | Avoids treating access as use or payment |
| Recorded path | Relevant link or campaign information you actually captured | Documents observed touchpoints |
| Reported path | The person's own account of discovering you and deciding to inquire | Adds context your records may miss |
| Preparation | Specific materials or completed work they brought | Makes “better prepared” observable |
| Fit | Qualified, unsuitable, or not yet assessed, with reason | Keeps quality separate from volume |
| Current outcome | Conversation, proposal, accepted, declined, pending, or closed without decision | Prevents a booking from becoming a claimed sale |
| Follow-up date | When the record was last checked | Shows whether the outcome is mature enough to interpret |
Keep private identifiers out of public reports. You can use pseudonymous IDs in analysis and retain contact details separately where needed for your normal business process.
Ask two different source questions
“How did you first come across my work?” and “What prompted you to contact me about this project?” are different questions. Someone may have read your book years ago, purchased the companion last month, and contacted you after a colleague's referral.
A marketing consultant described seeing clients “struggle with attribution and measuring the true value that channels bring”. That public account is a useful reminder that a tidy source field does not necessarily capture the whole buying path. Original post by u/LeadingWall.
Preserve the answer instead of forcing it into the source category you hope to prove. If the reader says the companion clarified their question but a referral prompted the inquiry, record both roles. Neither observation establishes what would have happened without the product.
Read a fictional cohort without exaggerating it
Suppose the cultural-organization author receives twelve distinct consulting inquiries during a quarter. The following numbers are invented to demonstrate the ledger, not results from an author or Skillfully.
| Group | Inquiries | Assessed for fit | Qualified | Accepted engagements | Still pending |
|---|---|---|---|---|---|
| Mentioned using the paid companion | 5 | 4 | 3 | 1 | 2 |
| No known companion use | 7 | 6 | 3 | 1 | 1 |
| Total | 12 | 10 | 6 | 2 | 3 |
Here, “pending” includes two qualified opportunities still under discussion and one unassessed inquiry. It is not a mutually exclusive qualification category. The ledger should retain both fit status and commercial outcome.
Among assessed inquiries, the companion group has three qualified out of four; the other group has three out of six. Report those counts before the corresponding 75% and 50%. The groups are too small and different to justify a claim that the companion improved qualification by a particular amount.
One of the five companion users was already a consulting prospect before purchasing. Another was a former client. Those relationships matter. The one accepted engagement associated with the companion is not automatically an incremental customer created by it.
Also inspect preparation directly. Did the person bring a usable research question or an evidence brief? A receipt alone tells you nothing about that.
Keep pending outcomes visible
A marketer working with long sales cycles wrote that it was “still difficult to tell which campaigns have the biggest influence on an opportunity.” Their context involved several decision-makers and months-long buying processes. It should not be converted into a benchmark for an author business, but it explains why a review date matters. Original post by u/xxmmccnnvvb.
Review the same inquiry cohort again later rather than comparing an old, fully resolved group with this month's unfinished conversations. State the cutoff date. Keep declined projects and unanswered inquiries visible alongside accepted work.
If you calculate revenue, distinguish quoted project value, contracted value, and collected revenue. Do not add the same engagement to several channel totals and then describe their sum as additional revenue.
Use the ledger to choose a specific change
If product users arrive well prepared but ask for work you do not offer, revise the consulting transition and scope description. If suitable buyers cannot complete the preparation, examine the product itself. If former clients account for most activity, investigate how new readers encounter the offer before claiming a new acquisition channel.
You may also discover that the product is useful on its own and rarely leads to consulting. That can still fit your business. Decide whether consulting inquiries were the primary goal or an optional benefit.
For quality issues in the companion, use the separate guide to testing an agent skill. Business attribution cannot establish that the method was applied correctly.
If you want to explore a paid application of your book that can also prepare appropriate consulting prospects, visit Skillfully and choose Book onboarding. Bring the reader task and your definition of a qualified inquiry. The product and its commercial role should be clear before you start counting leads.