A trial user found a bug that changed my priorities
I've been trying to get more people to use DocMetrics on real proposals.
This week, a new trial user uploaded 5 documents, created tracking links, and then hit a blocker.
Two of his PDFs were 29 MB and 57 MB, and they wouldn't upload.
At first I assumed it was a file issue. It wasn't.
I traced it back to our 10 MB upload limit.
The interesting part is that he said he'd like to become a long-term user, but his first impression was the upload problem.
That completely changed my priorities.
Instead of building another feature, I'm focused on removing friction for someone who's already trying to use the product.
Curious: what's the biggest bug that completely changed your roadmap because a real user hit it?
Have you seen whether fixing the upload limit changes what trial users do next—sending tracked proposals, returning to upload more, or progressing toward a paid plan?
ours was the connect wallet button. it only worked with a browser extension wallet, so on phones it just silently did nothing. that jumped over everything else on the list
Helpful post. How did you get your first bit of traction?
The thing I'd chase is that a client-side upload rejection probably never reached your logs, so every earlier user with a 30MB PDF left without leaving a trace — worth firing an event with the rejected file size.
For my case, there is paid user stopped subscription because of some server side bug that cause stability issue. I have to prioritize the stability and quality over new features.
Good call fixing that first. Someone who uploads 5 docs on a trial is already sold, the upload was the only thing in the way.
If the limit is on your server, one option is letting the browser upload straight to storage with a presigned URL. Your server only hands out the URL and records the file after, so big PDFs never pass through it. Then the 10 MB limit mostly goes away.