Solutions — pick by product category

Solutions are product-category answers — IDP, document parser, AI invoice processing, OCR. Useful when you're evaluating tools by category (e.g., "we need an IDP platform"). Use cases are workflow-specific — they describe a real workflow with documents-in and data-out (e.g., parse invoices to QuickBooks). If you know the category, start here. If you know the workflow, start at /document-types.

The document-type pages (/document-types/invoices, /document-types/pdfs, /email-parser, …) and /ocr-software are head-term category pages — they capture buyers searching the head term. Solutions go one layer deeper: they target a named product category a buyer might be evaluating against alternatives (e.g., "intelligent document processing software", "document parsing API"). Each solution page has a unique buyer angle the core pages don't cover.

Solution first if you're still scoping the product category. Integration first if you already know which destination tool the data needs to land in (Google Sheets, QuickBooks, Zapier, etc.). The two are complementary — every solution supports every integration.

No — each solution page targets a distinct product-category keyword and a distinct buyer mental model. For example, /solutions/document-parsing-api targets developers building integrations, while /solutions/document-parser targets ops teams who don't write code. Overlapping intents are consolidated to the canonical page (per framework §5.4 cannibalization rule).

Solutions are product-category pages — what we sell (e.g., /blog/best-bank-statement-analyzer, /solutions/intelligent-document-processing). Use-cases are workflow pages describing specific end-to-end tasks (e.g., /integrations/quickbooks, /use-cases/bill-of-lading-parsing). Each solution page lists the workflows it powers; each use-case links back up to its parent solution.