Drop in an ocean carrier service contract. Manifesto extracts every rate, arbitrary, and surcharge into your existing rate workbook — and links every row back to the exact line in the PDF it came from.
| Origin | Dest | 20GP | 40HC |
|---|---|---|---|
| CNSHA | USLAX | $1,450 | $1,850 |
| CNNGB | USLAX | $1,450 | $1,850 |
| CNSZX | USLGB | $1,500 | $1,900 |
| CNYTN | USLGB | $1,500 | $1,900 |
"Rates subject to GRI effective May 1. BAF included in base ocean freight."
What teams using Manifesto can expect on every contract.
A single carrier service contract is hundreds of pages of port-pair rates, arbitraries, and surcharges. Amendments arrive every few weeks and reset the clock.
A pricing analyst spends 4–8 hours keying a single ocean service contract into the team's rate workbook.
Manual transcription produces typos that show up as customer disputes weeks later, and there is no audit trail to chase them back to the source.
When a number is questioned, the answer lives in someone's spreadsheet history — not in the contract itself.
Deterministic-first. AI is a fallback for ambiguous cases, never the engine. Every row is verified against the source PDF.
Identify document kind, family, layout type, and amendment status before any extraction logic commits to a strategy.
Block-based parsing of rate tables, arbitraries, commodities, and surcharges with explicit page-and-text provenance per row.
Cities, commodities, and surcharges are matched to managed lookup tables. Unknowns are flagged, not guessed.
Each row is scored as verified, needs-review, or weak based on actual PDF text support — no template required.
Reviewers work the queue with side-by-side PDF highlighting. Click a row, the origin, destination, and rate tokens light up on the page.
Reviewer-ready .xlsm that drops into your existing rate workbook — VBA macros preserved. No workflow change.
When a customer disputes a rate, you don't dig through someone's spreadsheet history. You click the row and see the PDF token.
From ingestion and extraction to review and export — all in one place.
Manifesto understands the actual structure of freight contracts: rate blocks, note blocks, arbitraries, and surcharges.
Every extracted row is scored against the PDF text that supports it. Strong, ambiguous, and weak rows are surfaced explicitly.
Resolve flagged rows in a purpose-built UI. Compare extracted values against PDF evidence side by side.
Every pipeline run is a permanent artifact. Row history, amendments, and reviewer actions are auditable.
Documents are routed through deterministic layout profiles. Unknown layouts are flagged, not silently guessed.
Every field carries a strict audit trail back to the page, line, and tokens it was extracted from.
Amendments are first-class. Each one is processed against the base contract with full row-level diff and version history.
Export reviewer-ready .xlsm that matches your existing rate workbook — macros preserved. No workflow change.
Pricing teams ship more contracts. Operations leaders get audit trails. Reviewers stop scrolling spreadsheets.
Owns rate desk throughput and accuracy at quarter-end.
Lives and dies by amendment cycles.
Owns audit posture and customer disputes.
Tenant isolation, encryption, and audit logging are wired in — not bolted on.
Database-level row scoping per organization. No cross-tenant reads, ever.
TLS for all traffic; server-side encryption on object storage.
Row history captures actor, timestamp, and field-level diffs.
Invite-only, role-based access. Email + password, magic links, and OAuth via Supabase identity providers.
From discovery call to first export — it only takes a few steps to start using Manifesto.
30-minute call. We map your contract volume and existing Excel workbook.
We create your organization and seed your reference data in minutes.
Process contracts on real data. Reviewers get access to the secure workbench.
Review usage and convert to an annual plan. Your data is yours either way.
Bring us a sample contract on the discovery call. We'll show you the extraction, the evidence trail, and the .xlsm export — in your existing template.
Pilots typically launch within 1–2 weeks of the discovery call.