I got my first customer for my PDF generation API. Here’s what I learned
I got my first customer for Pritset.
For some people this may sound small, but for me it feels like a very important milestone.
Pritset is an API for generating PDFs from DOCX templates. The idea is simple: instead of building custom PDF layouts in code, developers can use Microsoft Word templates, pass JSON data through an API, and get a generated PDF back.
When I started building it, the biggest question was not technical.
The real question was:
Does anyone actually need this?
As developers, we can spend a lot of time building something that feels useful to us. But until someone outside your own head tries to use it, you do not really know.
My first customer is a travel startup. Their case is very close to what I had in mind when building Pritset: document generation from business data, where templates may change and the company does not want to spend developer time rebuilding PDF layouts again and again.
What I learned from this first customer experience:
The first customer is not only about money
Of course, revenue matters. But the bigger value is learning.
A first customer shows you where your onboarding is confusing, what your documentation is missing, what is obvious to you but not obvious to others, and what parts of the product actually matter.
The product needs to be explained much simpler
I used to think mostly in terms of API, DOCX templates, JSON, webhooks, conversion, and infrastructure.
But customers usually think in terms of:
“I need to generate an invoice.”
“I need to create a report.”
“I need to send a document to my client.”
“I do not want to manually edit this every time.”
That is a big difference.
Founder-led sales is uncomfortable but necessary
Before this, I spent most of my time building. Writing code is comfortable. Talking to customers is much less comfortable.
But after doing outreach and conversations, I understand that the product direction becomes much clearer only after real conversations.
Even replies like “not now” or “we do this another way” are useful signals.
Small startups are a good place to start
Big companies may have complex buying processes, security requirements, and long decision cycles.
A small startup can move faster, give direct feedback, and help you understand the real use case much earlier.
The first customer changes your mindset
Before the first customer, it feels like you are trying to prove that the product should exist.
After the first customer, the question changes.
Now it becomes:
Who else has the same problem?
How do I find them?
How do I make onboarding easier?
How do I turn this into repeatable sales?
I still have a lot to improve in Pritset: onboarding, examples, documentation, positioning, and probably many product details I have not discovered yet.
But now I have something real to build from.
The product is no longer just an idea or a technical project.
It has a real customer using it.
For me, that is a big step.
