Email thread → readable message with honest truncation
| QC score | Tables | Figures | Code cells | Output size |
|---|---|---|---|---|
| 100% | 0 | 0 | 0 | 1,032 chars ≈ 258 tokens |
Fidelity warnings
- long quoted reply chain truncated (5 quoted lines) — token sink; the newest message is intact
- 1 attachment listed but not extracted — save them from your mail client if needed
Converted Markdown
# Re: Vendor consolidation — next steps
## Message
- **From:** Jordan Lee <jordan@example.com>
- **To:** Ops Team <ops@example.com>
- **Cc:** Sam Park <sam@example.com>
- **Date:** Thu, 02 Jul 2026 09:14:20 +0000
- **Subject:** Re: Vendor consolidation — next steps
## Body
Agreed on both counts — let's lock the shortlist Friday.
Two updates before then:
1. Contract review finished for the top two vendors.
2. The tooling audit found 3 duplicate subscriptions we can cut now.
Jordan
On Wed, 01 Jul 2026 at 17:02, Sam Park wrote:
> Thanks for the summary. My take:
> - Shortlist should be two vendors, not four.
> - Procurement wants the decision memo by the 10th.
> On Tue, 30 Jun 2026 at 11:40, Jordan Lee wrote:
> > Kicking this off. Current spend is spread over six vendors.
> > Draft criteria attached; comments welcome.
> > The long tail here is mostly legacy contracts nobody renewed
> > on purpose, so expect quick wins.
> … (5 more quoted lines truncated)
## Attachments
- `criteria.pdf` (~135 B, not extracted)
Run this conversion live — or drop your own file. Everything stays in your browser.
Open in the tool →