Live data from Hacker News

Launch HN: Extend (YC W23) – Turn your messiest documents into data

extend.ai

1–10 of 35 posts

Launch HN: Extend (YC W23) – Turn your messiest documents into data

#1
Hey HN! We’re Kushal and Eli, co-founders of Extend (https://www.extend.ai/). Extend is a toolkit for AI teams to ingest any kind of messy document (e.g. PDFs, images, excel files) and build incredible products.

We built Extend to handle the hardest documents that break most pipelines. You can see some examples here in our demo (no signup required): https://dashboard.extend.ai/demo

I know you're probably thinking “not another document API startup”. Unfortunately, the problem just isn’t solved yet!

I’ve personally spent months struggling to build reliable document pipelines at a previous job. The long tail of edge cases is endless — massive tables split across pages, 100pg+ files, messy handwriting, scribbled signatures, checkboxes represented in 10 different formats, multiple file types… the list just keeps going. After seeing countless other teams during our time in YC run into these same issues, we started building Extend.

We initially launched with a set of APIs for engineers to parse, classify, split, and extract documents. That started to take off, and soon we were deployed in production at companies building everything from medical agents, to real-time bank account onboarding, to mortgage automation. Over time, we’ve worked closely with these teams and seen first-hand how large the gap is between raw OCR/model outputs —> a production-ready pipeline (LLMs and VLMs aren’t magic).

Unlike other solutions in the space, we're specifically focused on three core areas: (1) the computer vision layer, (2) LLM context engineering, and (3) the surrounding product tooling. The combination of all three is what we think it takes to hit 99% accuracy and maintain it at scale.

For instance, to parse messy handwriting, we built an agentic OCR correction layer which uses a VLM to review and make edits to low confidence OCR errors. To tackle multi-page tabular data, we built a semantic chunking engine which can detect the optimal boundaries within a document so models can excel with smaller context inputs.

We also shipped a prompt optimization agent to automate the endless prompt engineering whack-a-mole teams spend time on. It’s built as a background agent to replicate the best prompter on your team, and runs in a loop with access to a set of tools (view files, run evals, analyze results, and update schemas).

The most surprising part of this whole experience has been seeing how many crazy PDF formats are out there! We've run into everything from supermarket inventory magazines, pesticide labels, construction blueprints, and satellite manufacturing plans.

Everything described above is live today. You can see it in action here (no signup): https://dashboard.extend.ai/demo. To upload your own files, you can log in and do so (we’re adding free usage credits to all accounts that sign up today).

We’re excited to be sharing with HN! We’d love to hear about your experiences building document pipelines. Please try it out, and share any and all feedback with us (e.g. hard documents that didn’t work, feature requests).

Launch HN: Extend (YC W23) – Turn your messiest documents into data
extend.ai

Re: Launch HN: Extend (YC W23) – Turn your messiest documents into data

#5
Congrats on the launch! It looks really cool.

> Unlike other solutions in the space, we're specifically focused on three core areas: (1) the computer vision layer, (2) LLM context engineering, and (3) the surrounding product tooling.

I assume the goal is to continue to serve this via an API? That would be immensely helpful to teams building other products around these capabilities.

Re: Launch HN: Extend (YC W23) – Turn your messiest documents into data

#6

Just how many IDP / document processing “AI” startups are out there?

There's definitely no shortage of options. OCR has been around for decades at this point, and legacy IDP solutions really proliferated in the last ~10 years.

The world today is quite different though. In the last 24 months, the "TAM" for document processing has expanded by multiple orders of magnitude. In the next 10 years, trillions of pages of documents will be ingested across all verticals.

Previous generations of tools were always limited to the same set of structured/semi-structured documents (e.g. tax forms). Today, engineering teams are ingesting truly the wild west of documents, from 500pg mortgage packages to extremely messy healthcare forms. All of those legacy providers fall apart when tackling these types of actual unstructured docs.

We work with hundreds of customers now, and I'd estimate 90% of the use cases we tackle weren't technically solvable until ~12 months ago. So it's nearly all greenfield work, and very rarely replacing an existing vendor or solution already in place.

All that to say, the market is absolutely huge. I do suspect we'll see a plateau in new entrants though (and probably some consolidation of current ones). With how fast the AI space moves, it's nearly impossible to compete if you enter a market just a few months too late.

Re: Launch HN: Extend (YC W23) – Turn your messiest documents into data

#7
post #6

Just how many IDP / document processing “AI” startups are out there?

There's definitely no shortage of options. OCR has been around for decades at this point, and legacy IDP solutions really proliferated in the last ~10 years. The world today is quite different though. In the last 24 months, the "TAM" for document processing has expanded by multiple orders of magnitude. In the next 10 years, trillions of pages of documents will be ingested across all verticals. Previous generations of…

fully aware that OcR and IDP has been around, but the “AI native” versions are pretty saturated too

Re: Launch HN: Extend (YC W23) – Turn your messiest documents into data

#8

Congrats on the launch! It looks really cool. > Unlike other solutions in the space, we're specifically focused on three core areas: (1) the computer vision layer, (2) LLM context engineering, and (3) the surrounding product tooling. I assume the goal is to continue to serve this via an API? That would be immensely helpful to teams building other products around these capabilities.

thanks! Yup that's correct, we offer a set of APIs for handling documents: parsing, classification, splitting, and extraction.

We've seen customers integrate these in a few interesting ways so far:

1. Agents (exposing these APIs as tools in certain cases, or into a vector DB for RAG)

2. Real-time experiences in their product (e.g. we power all of Brex's user-facing document upload flows)

3. Embedded in internal tooling for back-office automation

Our customers are already requesting new APIs and capabilities for all the other problems they run into with documents (e.g. fintech customers want fraud detection, healthcare users need form filling). Some of these we'll be rolling out soon!

Re: Launch HN: Extend (YC W23) – Turn your messiest documents into data

#10
post #6

Earlier quoted context omitted.

There's definitely no shortage of options. OCR has been around for decades at this point, and legacy IDP solutions really proliferated in the last ~10 years. The world today is quite different though. In the last 24 months, the "TAM" for document processing has expanded by multiple orders of magnitude. In the next 10 years, trillions of pages of documents will be ingested across all verticals. Previous generations of…

fully aware that OcR and IDP has been around, but the “AI native” versions are pretty saturated too

There's certainly a lot of tools that focus on individual parts of the problem (e.g. the OCR layer, or workflows on top). But very few that solve the problem end-to-end with enough flexibility for AI teams that want a lot of control over the experience.

For example, we expose options for AI teams to control how chunking works, whether to enable a bounding box citation model, and whether a VLM should correct handwriting errors.

Most customers we speak with, the evaluation is actually between Extend or building it in-house (and we have a pretty good win rate here).

Post reply on HN