[somberi]

Useful service and a large problem space. Congrats and all the best. As someone who is a target customer, my 2 cents:

a. If this is a strategic value for my pipeline (and it is), we are going to code it ourselves, only because we can host it inside our fences. Critical customer data and hence.

b. The pricing is way off and is not reflective of the cost or value (for us). Even if it was 1/10th of the prices you charge, it will still be a no-go. At the volumes we have, it makes sense to build this ourselves.

c. SOC2 / ISO27001 - You might want to obtain them asap if you are looking to sell to outsourcing companies or FSG.

[AugusteLef]

certifications (SOC2 / ISO27001) and offer an on-premise solution! I see there's already a discussion about pricing, so I'll leave that be. However, would an unlimited volume at a fixed cost (and self-host) be an attractive solution? It could be interesting for very high volumes.

[somberi]

I can tell you that the world I operate in will want something like what you are proposing (fixed rate + OnPrem) and the pricing is going to have a ceiling because building this in-house is a real and viable alternative. Our problem is not so much lack of talent but other product-roadmap priorities. What is the ceiling? I do not know, but can hazard a guess. 1/4th of the yearly cost of a good developer.

[AugusteLef]

Thank you for taking the time. It really helps us define our value proposition and outline the next steps in product development. As you mentioned, the challenge isn't the inability to produce something in-house but rather other product-roadmap priorities. Our goal is to ensure that companies needing to produce many documents —where documents are necessary but not core to their business— can use our solution at a fair price and limiting the pain of creating such solution in house. OnPrem + fixed rate seems to be the best option for high volume. We'll explore this and see what future solutions we can offer to meet these needs!

[HatchedLake721]

Curious, with ~$0.005 per document, what volumes do you do that pricing becomes a no-go for you?

[somberi]

In the long term, ~$0.005 per page (as opposed to document, which I assume hatchedlake meant) say on a mortgage document (~300 pages per) it adds up. The other alternative, which is to build this in-house (say 3 months and custom build, edge cases, such goodies), is more desirable (for us).

[HatchedLake721]

I was looking at https://www.onedoclabs.com/pricing which says $0.005 per document, not page.

[Titou325]

We indeed price starting at $0.005 per document, but have slightly updated the pricing following the good input we received yesterday from the community - hence the slight discrepancy in comments.

[ffpip]

FYI there is a typo on the pricing page under the pro plan.

"Generate up to 1'500 documents per month without watermark"

1,500 instead of 1'500

[AugusteLef]

Got it, thanks!

[nktrnk]

Unrelated, out of curiosity. In a 300 page mortgage document, there’s probably >90% of boilerplate with a few pages of custom content. Hypothetically, you could generate those <10% and then stitch it together with the rest onsite.

[AugusteLef]

Street smart! But yes, programmatic merging does get complex, especially with large document sizes. It's a balancing act between functionality and handling those technical challenges!