Here's my contribution: I looked at the landing page for 5-10 seconds and I couldn't quite figure out what the product does. What is a "template" in your product's context? I understand "HTML to PDF" or maybe even "JSON to PDF", but what is "template" to PDF?
EDIT: Okay I see on your site a template is a "LibreOffice/OpenOffice document." I have no idea what that is. Maybe I'm just not your target audience?
If you know JSON, you probably are somehow my target audience.
Imagine you could take your normal Word document and just put in some placeholders. Then send some JSON and this Word document (as a template) to my service. You would get a PDF in return.
Instead of MS-Word documents I use OpenOffice documents as templates.
OpenOffice is a word processor like MS-Word. Also a nice user interface etc. it is just build with different goals in mind.
That's a good point though. Could you handle .docx files? I bet a lot of your potential users (the managers more than the developers) would be in the same boat: use MS Word every day, but never heard of LibreOffice. Even though they could obviously install it and convert their template doc from Word, that adds a lot of friction.
Comments
Here's my contribution: I looked at the landing page for 5-10 seconds and I couldn't quite figure out what the product does. What is a "template" in your product's context? I understand "HTML to PDF" or maybe even "JSON to PDF", but what is "template" to PDF?
EDIT: Okay I see on your site a template is a "LibreOffice/OpenOffice document." I have no idea what that is. Maybe I'm just not your target audience?
If you know JSON, you probably are somehow my target audience.
Imagine you could take your normal Word document and just put in some placeholders. Then send some JSON and this Word document (as a template) to my service. You would get a PDF in return.
Instead of MS-Word documents I use OpenOffice documents as templates.
OpenOffice is a word processor like MS-Word. Also a nice user interface etc. it is just build with different goals in mind.
That's a good point though. Could you handle .docx files? I bet a lot of your potential users (the managers more than the developers) would be in the same boat: use MS Word every day, but never heard of LibreOffice. Even though they could obviously install it and convert their template doc from Word, that adds a lot of friction.