You spent hours on that proposal. They never replied. You have no idea if they even opened it. I built the solution. Launching today.
The idea
It started with a simple frustration.
I was sending documents — proposals, CVs, decks — and once I hit send, I was completely blind. Did they open it? Which part did they read? Did they share it with someone else? Did they even care?
That black hole after sending a document is one of the most frustrating experiences in business. You put hours into a proposal and then you wait. And wait. And guess.
I started researching the space and found platforms like DocSend and PandaDoc had built businesses around this exact problem. But two things stood out to me immediately — they were expensive, and none of them solved the understanding gap.
Knowing someone spent 4 minutes on page 3 is useful. But you still don't know why. Did they love it? Were they confused? Did they have a question they never asked?
That insight became DocMetrics.
What I built differently
DocMetrics does everything you would expect from a document intelligence platform — share tracking, per-page analytics, time spent, viewer identity, download controls, NDA signing, e-signatures, watermarking, and real-time notifications.
But the feature that nobody else has is video walkthroughs.
As the sender, you can record up to 60 seconds of video per page. When your prospect opens page 3 and spends time there, your face appears — explaining exactly what that page means, anticipating their questions, guiding them through your thinking.
It turns a static document into a conversation. Without a call. Without scheduling. Without hoping they read the caption you buried at the bottom.
For sales teams, founders sending pitch decks, recruiters, consultants — anyone who sends documents and waits — this changes the dynamic completely.
Building it solo in 5 months
I am a full stack developer, about a year and a half into my career. I built this entirely alone, bootstrapped, no co-founder, no funding, no team.
It was not easy.
The authentication architecture alone — making sure every user has a completely isolated dashboard and data environment — took me a week to get right. PDF rendering at scale, real-time analytics pipelines, the signing infrastructure, the video recording and storage system — every layer had its own surprises.
I watched more documentation videos than I can count. I rewrote backend logic multiple times. I broke things and fixed them and broke them again.
But five months later, DocMetrics is live.
What DocMetrics includes today
Document sharing with full per-page analytics
Time-on-page tracking per viewer
Video walkthrough recording per page
E-signatures and NDA flows
Watermarking and access controls
Password protection and email gating
Real-time viewer notifications
Portal spaces for sharing multiple documents
Team collaboration
Compliance and audit trails
Pricing is simple and built for individuals and small teams — not enterprise contracts.
Where I am today
Launching today. Zero paid users as of this morning. One developer. One product. Global ambitions.
DocMetrics is live at docmetrics.io.
If you send documents as part of your work and you are tired of the silence after hitting send — this was built for you.
What I want from this community
Honest feedback. Brutal if necessary. If you try it and something does not work, tell me. If the positioning is off, tell me. If there is a feature you would pay for that I have not built, tell me.
I am building in public from today. Follow along if you want to see what happens when a solo developer attempts to compete with well-funded tools on nothing but code and conviction.
Let's go.
The proposal black hole is painfully real. I run a marketing agency and we send proposals constantly. Before we started tracking opens we had no idea if the silence meant they hated the pricing, never opened it, or if it just got buried in their inbox.
Once we added open tracking to our proposals (we use a different tool for it now) we realized that about 40% of our lost deals never even opened the document. They were not rejecting us. They just forgot or got distracted. That single insight changed our entire follow up strategy because now we know the difference between someone who read the whole thing and went silent versus someone who literally never looked at it.
The per page analytics angle is interesting too. We noticed that prospects who spent time on our case studies page almost always converted. The ones who only looked at pricing and bounced rarely did. That data completely changed how we structured our proposals and what content we put where.
For what it is worth the biggest challenge with tools like this is not getting people to try it. It is getting them to change their existing workflow. Most people are still sending PDFs as email attachments out of habit. The friction is not price, it is behavior change. Curious how you are thinking about that.
This is exactly the kind of insight that validates why per-page data matters more than just open tracking. The case studies versus pricing pattern you noticed is deal intelligence in action — not just what they did but what it means about where they are in the decision.
The 40% who never opened is something we see consistently too. It completely changes the follow-up conversation. Instead of chasing someone who already said no with their behaviour, you are simply re-engaging someone who got distracted. Completely different tone, completely different outcome.
On the behaviour change problem — you are right and it is the real friction. Our approach is to meet people where they already are. Most people already send PDFs. We do not ask them to change that habit — we just add a layer on top of it. Generate a link instead of attaching the file and everything else stays the same. The workflow does not change, the insight just appears.
The harder part is getting people to act on the data once they have it. Seeing that a prospect spent 8 minutes on page 4 is interesting. Knowing that page 4 is your pricing section and that they have not replied in 3 days is the signal that should trigger a specific follow-up. We are building toward surfacing that automatically so the user does not have to interpret the dashboard — they just get told what to do next.
How are you currently handling the gap between the data you see and the action you take on it?
The uncertainty after sending something is often worse than a clear rejection.
There are a few tools that track opens, but they usually stop at “it was viewed.”
Curious how you’re thinking about going beyond that.
Are you trying to capture deeper signals of interest, or help people act on that information in a more meaningful way?
Both, honestly — but in a specific order. First capture the right signals (not just opens — re-reads, back navigation, dropping engagement across visits). Then tell the sender what it means and exactly when to follow up. Most tools give you a dashboard to check. We push the insight to you before the deal goes cold.
The strongest part here isn’t document tracking.
It’s turning silent intent into visible buying signal.
Open data is useful.
But “where they slowed down, where they hesitated, what needed explanation” is the real sales layer.
That’s the wedge.
Most tools stop at analytics.
The more valuable product is: “tell me where the deal got uncertain before the prospect disappears.”
That’s where this gets much harder to replace.
I like this framing a lot. I’ve been thinking along similar lines — especially around identifying hesitation patterns (re-reading sections, repeated returns, drop-offs). Curious what signals you think are most reliable for “uncertainty” beyond time-on-page?
Time-on-page is noisy.
The stronger signals are usually:
re-reading the same section
jumping back to pricing
hovering on proof
opening a doc multiple times without forwarding
stalling right after a specific objection point
That’s usually where it stops being engagement data and starts becoming deal uncertainty.
The useful layer is not “they spent 4 minutes.”
It’s “they got stuck here and needed this to feel safer.”
That’s the part worth naming clearly if you want this to become harder to replace.