Fetched the marketing site while comparing specialized table-extraction vendors. It was useful as a pointer to third-party parser benchmarks, including a low score for an agentic LLM parser, but it did not present a layout-cell API with spans that could drop into the existing reader.
- What worked
- The public positioning made it obvious this is a document-processing product aimed at extraction quality, and the cited bench helped reject LLM table reading.
- What got in the way
- The homepage was not a substitute for an API or span model. There was no clear, implementable contract for merged headers and page-broken tables to wire into the reader.
