Job win-loss-interview-notes-coded-to-reasons · revised 12 October 2026
Code your own win-loss interviews into reasons, with the quotes behind each
Interview notes you collected yourself are coded to reasons you approve, with the verbatim quote behind each code. We never contact your buyers.
You might be seeing
- Different readers draw different conclusions from the same notes
- Quotes get paraphrased until they say something else
No passwords, keys, card details or admin invites needed to start.
What usually happened
Buyer interviews often show more than rep notes about why deals are won or lost, but coding them by hand is slow and varies by reader. A tool that summarises can bend a quote or read a cause into a hedge. The interviews themselves are yours to run.
Who it’s for: Sales or product leader who runs buyer interviews and wants them coded consistently.
Usually starts when: A stack of interview notes sits unread, and the summary depends on who reads it.
The result: Notes or transcripts of interviews you ran are coded to reasons you approve. Each code carries the verbatim quote behind it, counts reconcile, and "unclear" is allowed. We never contact your buyers.
Check whether this job fits
Answer these without sending files or logins. Nothing is submitted unless you choose to contact us.
What you get
- The coded interviews with quotes
- The counts by reason
- The coding guide
- The quote-check results
Included
- At least 12 interviews you ran yourself, with notes or transcripts
- A reason list you approve, with "unclear" allowed
- A verbatim quote per code, checked against the notes or transcripts
- Counts by reason as counts, not percentages, for a small set
- A coding guide you can reuse
Not included
- Contacting, scheduling or interviewing buyers
- Names or contact details in the output
- A claim about causes beyond what interviewees said
- Recording calls
- Percentages on fewer than 30 interviews
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
An automated check finds 100% of quotes appear word for word in the notes or transcripts. A quote that does not appear word for word fails the whole test.
Evidence: The quote check output.
You code 6 of the interviews yourself, without seeing our codes; at least 5 get the same main reason as ours, and the disagreements are listed. With so few interviews this is a smoke test: it shows nothing about the interviews you did not code (5 of 6 bounds the true rate at about 41%).
Evidence: Your codes and ours side by side.
Counts by reason add up to the number of coded interviews, and "unclear" is counted separately.
Evidence: The count table.
No name or contact detail appears in the output. A name in the output fails the whole test.
Evidence: A name and email scan of the output.
Sign-off. You re-run the test yourself, check the list of severe errors and sign off in writing. Payment follows sign-off.
If it fails. If the agreed pass mark is not met, we say so, hand over the results and the failures, and do not call the output working. You do not pay for this scope; we agree whether to stop or re-quote.
When it fits, and when we stop
It fits when
- You ran the interviews and hold consent to use the notes this way
- Notes are redacted of names and company identifiers before sharing
- A named person approves the reason list
We stop and tell you if
- You want us to contact buyers or run interviews
- Consent for this use was not obtained
- Fewer than 12 interviews
What could go wrong
The job reads notes and writes a report, so there is nothing to undo. Our copies are deleted at the end.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A quote is bent or invented | An automated check confirms each quote appears word for word in the notes or transcripts. |
| Identifiable notes are shared | Notes are redacted before sharing, and we delete our copies at the end. |
| A small set looks like a pattern | The report gives counts, not percentages, and says how many interviews it covers. |
A separate automated reviewer checks every quote, the codes and the counts before hand-over, and no person on our side reviews unless your agreement names one. Your named person approves the reason list and reads the results. At launch the work is largely automated, and we say so.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the reason list, the quote rule and the pass marks in writing
- Receive the redacted notes by the agreed route
- Code each interview and attach a verbatim quote, or "unclear"
- Check every quote against the notes or transcripts
- Independent automated review of codes, quotes and counts
- Hand over the results and the coding guide
This is a one-off job, not a subscription or emergency cover. We confirm eligibility, price, a start window and a delivery date before you accept, and work starts only after agreed inputs and access are in place. Nothing is sent, merged, posted or changed in your live systems by us, and an enquiry creates no charge or booking.
Need to keep it working?
Discuss coding each new batch of interviews.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Two people on your team can code the same five interviews on a shared sheet and compare. That also builds your own coding guide.
Questions
Will you interview our buyers?
No. We never contact them.
Why not percentages?
With a dozen interviews, a percentage would suggest more certainty than the data has.
Is the coding done by AI?
A model may draft the codes. Every quote is checked against the notes or transcripts, and you approve the reason list.
Send an enquiry
Send us
- How many interviews, over what period
- The reasons you already look for
- How consent was obtained
Later, once you agree
- Redacted notes or transcripts
- The approved reason list
- A secure handoff route agreed before any notes are shared
You keep the interviews. We read redacted notes you hand over and return coded results. Which service reads your records is agreed in writing before any real record is shared; the entry test uses invented or redacted data, or your own provider account.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “win-loss-interview-notes-coded-to-reasons” as the subject.