Send a fixed codebook and a batch of short written exchanges — chat logs, interview snippets, survey verbatims. Every row comes back coded, with a one-line rationale you can audit. Turnaround inside a day.
No dashboard, no signup — just a codebook, a spreadsheet, and a coder who reads every row before assigning a code.
Your fixed category list and definitions, plus the exchanges to code — CSV, spreadsheet, or pasted text.
One code per exchange, chosen by the dominant content, with a short rationale so the call is auditable — not a black box.
Same structure you sent, plus code + rationale columns. Edge cases and ambiguous rows are flagged, not silently guessed.
This is a demonstration codebook and 20 synthetic exchanges — built to show the method, not a real client's data. A real job codes against your categories.
| Code | Label | Definition |
|---|---|---|
| IR | Informational Request | Asks for or supplies facts, clarification, or instructions. |
| PR | Problem Report | Describes a fault, obstacle, or discrepancy. |
| EE | Emotional Expression | Primary content is a feeling — frustration, gratitude, worry, relief. |
| SA | Solution / Action Proposal | A next step, fix, or decision is proposed or agreed. |
| SR | Social / Relational | Greetings, congratulations, small talk — no task content. |
| OU | Off-topic / Uncodable | Doesn't fit above, or too unclear to code. |
| Exchange | Code | Rationale |
|---|---|---|
| “Hi, does the app support two-factor authentication?” — “Yes, in Settings > Security.” | IR | Requests factual how-to information. |
| “I've been trying to reset my password for an hour and nothing works.” — “I'm sorry — let's get it sorted.” | PR | Describes a persistent, unresolved fault. |
| “Honestly, I'm really frustrated with how long this has taken.” — “That's completely understandable.” | EE | Frustration is the entire content of the message. |
| “Let's schedule a follow-up call for Thursday.” — “Sounds good, I'll send an invite.” | SA | Concrete next step proposed and agreed. |
| “Good morning! Hope you had a nice weekend.” — “I did, thanks — you too!” | SR | Pure greeting, no task content. |
| “lol anyway, did you catch the game last night?” — “Not this time, buried in emails.” | OU | Off-topic, unrelated to the research focus. |
Also open: coding rules used for this sample (tie-breaking, one-code-per-row, OU as last resort).
Flat-rate for a standard batch. Priced against what this category of job actually clears on Freelancer and Upwork today.
| 21–50 exchanges | $1.50 / item |
| 51–150 exchanges | $1.20 / item |
| 150+ / recurring codebook | Quote on request |
More than 6 categories or a codebook that needs double-coding for inter-rater reliability? Quoted separately — send the codebook and I'll turn a number around same day.
Pay however suits you. No card details are ever taken on this page.
Pay by ACH or card on Melio's own hosted page — no card details are ever entered here. After we agree scope you'll get an invoice reference (e.g. INV-0003); enter that reference in the memo/note field at checkout so the payment matches automatically.
USDC / USDT / ETH accepted on Ethereum, Base, Arbitrum, or Polygon to this address:
0x927Ca2c4d6e6b0236691b525dB916299F20e9F0D