Setup
CSV upload
Lost-deals format, target-accounts format, and the most common parse errors.
CSV upload
Thawly accepts two CSV shapes. Both are processed by the same parser — the difference is just which columns you provide.
Lost-deals CSV (recommended)
The richest input. Each row is a deal you didn't win.
| Column | Required | Notes |
|---|---|---|
name | yes | The company name as you knew it. |
deal_value | no | GBP, no currency symbol (e.g. 12500). |
lost_date | no | YYYY-MM-DD preferred. |
lost_reason | no | Free text — fed into Claude when drafting your message. A present reason can sharpen the re-engagement message; leaving it blank carries no penalty. |
Target-accounts CSV
If you want to monitor prospects you haven't pitched yet, upload a list of target accounts. Just name is required; everything else can be added later.
| Column | Required | Notes |
|---|---|---|
name | yes | The company name. |
notes | no | Optional context about why you're watching this account. |
Target accounts are for first-touch outreach — Thawly's drafted message will never reference a prior relationship, because for target accounts there isn't one.
Common parse errors
- "No header row found" — the first line of the file must contain column names. Save from Excel as CSV UTF-8 rather than legacy CSV.
- "Unrecognised column" — column names are case-insensitive, but typos like
lost_value(instead ofdeal_value) are skipped silently. Check the column header line. - Duplicate companies — Thawly de-duplicates on lower-cased name within your account. Re-uploading the same list is safe.
Don't include
We only store company names — no contact names, no email addresses. If your CSV has personal data columns, they'll be ignored and the file is dropped after parsing.