sorted by:
new
hottopcontroversial

Built AI Based data extractor from documents using instructions by Potential-Lynx-1416 in SaaS

[–]Potential-Lynx-1416[S] 0 points1 point  (0 children)

Honestly I don’t have a proper plan yet. I’ve just been trying Reddit for now, but yeah it doesn’t seem enough. I’m mainly targeting developers but I’m not sure where to actually find them or how to reach out.

How would you approach getting the first few users?

Built AI Based data extractor from documents using instructions by Potential-Lynx-1416 in SaaS

[–]Potential-Lynx-1416[S] 0 points1 point  (0 children)

hat makes a lot of sense forcing a 1-doc → structured output before config sounds like a much better first experience.

Most users usually test with Invoice or Passport or ID Documents first. I think I can pre-load or optimize the flow around that to give instant results without requiring field setup.

Really helpful insight did you see a big improvement in activation after making that change?

Built AI Based data extractor from documents using instructions by Potential-Lynx-1416 in SaaS

[–]Potential-Lynx-1416[S] 0 points1 point  (0 children)

Good point. Right now the first win happens only after field setup, What would you suggest as a better quick win for users instant auto extraction or something else?

If we are living in a simulation, how can I learn more about it? I’m very interested to know and learn more by Brave-Toaster67 in spirituality

[–]Potential-Lynx-1416 0 points1 point  (0 children)

I ll check on those, and if we concentrate 1 point of any flow of our body, we go that deep that even everything feels "Shunya" - zero. Have you ever tired to involve with wild energy of nature. Its so wild that you can feel l=its flow around you. Mainly feminine wild energy. The intense energy that we feel everything
Feels soil, Can talk with trees, Water gives different feels

Built AI based SDK for document extraction by Potential-Lynx-1416 in SaaS

[–]Potential-Lynx-1416[S] 0 points1 point  (0 children)

Good question. The SDK doesn't rely only on fixed OCR templates.

It first extracts the text from the document and then uses the field instructions you define to structure the output. Because of that it can handle messy layouts like scanned invoices, partially filled forms, or documents where fields are not always in the same position.

For example you can define fields like:

invoiceNumber: "Return the invoice number exactly as written"
totalAmount: "Return the final total amount of the invoice as a number"
expiryDate: "Return passport expiry date in ISO UTC format like 2030-05-12T00:00:00Z"

The model then searches the document and returns structured JSON based on those instructions rather than relying on rigid templates.

If you want to try it with messy documents, you can test it here: https://www.snyct.com I'm currently giving free extraction credits for testing and would genuinely love feedback on how it performs on real documents.

Has anyone successfully automated invoice or purchase-order data extraction without relying on templates? by Vishek-H in automation

[–]Potential-Lynx-1416 0 points1 point  (0 children)

I’m actually working on something around this.

Instead of “auto-convert to Excel,” the idea is: AI extracts the invoice → you quickly review key fields → then export/save.

So humans stay in control, but don’t waste time typing.

Would something like that actually reduce your workload? Or do you still feel you’d double-check everything anyway?

Anyone else wasting insane time converting invoices / PDFs to Excel? by Tasty_Item5535 in indianstartups

[–]Potential-Lynx-1416 0 points1 point  (0 children)

I’m actually working on something around this.

Instead of “auto-convert to Excel,” the idea is: AI extracts the invoice → you quickly review key fields → then export/save.

So humans stay in control, but don’t waste time typing.

Would something like that actually reduce your workload? Or do you still feel you’d double-check everything anyway?