Sharing a document looks simple.
Upload a PDF, create a link, send it to someone, and wait for a response.
That's how I used to think about document sharing too.
But things change when the document you're sending is actually important.
Maybe it's a pitch deck you're sending to an investor.
Maybe it's a sales proposal worth thousands of dollars.
Maybe it's a financial document, due diligence file, client presentation, or confidential company report.
Once you send that link, a completely different set of questions starts.
Did they open it?
Did they actually read it?
Which pages caught their attention?
Did they return later?
Did someone else open the link?
Can I control who gets access?
These questions eventually became one of the reasons we started building SendNow.
The Problem Started After Clicking Send
Google Drive and Dropbox already make file sharing incredibly easy.
The problem isn't getting a document from one person to another.
The interesting part is what happens after that.
Imagine you're raising money for your startup.
You spend days improving your pitch deck and finally send it to an investor.
Then you wait.
One day.
Two days.
Three days.
No response.
You don't know whether they haven't opened it yet or whether they read the entire deck and decided not to reply.
You also don't know whether they spent most of their time looking at your product, traction, team, or financial projections.
That missing context is what made document tracking interesting to us.
It's also why we started studying products in this space and looking closely at different DocSend alternatives for sharing and tracking business documents.
Eventually, instead of only researching the problem, we decided to build our own solution.
Why We Started Building SendNow
The original idea behind SendNow was pretty straightforward.
Upload a document.
Create a secure link.
Share it.
Understand what happens next.
The more we worked on it, the more we realized that a document could behave much more like a website.
When someone visits your website, you can understand their activity.
You know that someone visited.
You can understand which pages they explored.
You can measure engagement.
But we still send some of our most important business information through PDF links without knowing much about what happens afterward.
That felt strange.
So we started thinking about document analytics.
A View Doesn't Tell the Whole Story
Let's say you send a 15 page proposal to a potential customer.
They open it.
That's useful information.
But imagine knowing that they spent ten seconds on the introduction, skipped quickly through the company section, spent two minutes reading your solution and another three minutes looking at pricing.
That gives you much more context.
This is why we started focusing on things such as:
◉ Document views
◉ Page level activity
◉ Time spent
◉ Viewing sessions
◉ Returning visitors
◉ Device information
◉ Browser information
◉ Geographic information
◉ Document interactions
The goal wasn't to create another dashboard filled with numbers.
We wanted the analytics to answer a useful question.
What happened after someone opened my document?
That question ended up influencing a lot of the product.
Then Security Became Just as Important
Tracking documents is useful.
But tracking means very little if the wrong person can access the document.
A lot of business documents contain information that shouldn't be completely public.
For example:
◉ Investor pitch decks
◉ Financial reports
◉ Client proposals
◉ Legal documents
◉ Due diligence files
◉ Internal company information
◉ M&A documents
◉ Product roadmaps
This meant we also had to think seriously about document security.
We started working on password protection, email verification, viewer restrictions, NDA gates, dynamic watermarks and other access controls.
The interesting challenge wasn't simply adding more security.
It was keeping the document easy to open for the intended recipient.
Every additional security step creates friction.
If someone needs to complete five different actions before reading a proposal, there's a good chance you've made the experience worse.
Finding the balance between security and usability became an important part of the product.
We ended up writing a separate guide about secure document sharing and protecting sensitive business files because there was much more to the problem than we initially expected.
The PDF Viewer Was Actually the Easy Part
When we first started, I thought displaying documents would be one of the difficult parts.
It wasn't.
The difficult questions appeared after we started tracking real viewing behaviour.
What exactly counts as a view?
When does a viewing session end?
What happens if someone leaves the document open in another browser tab?
How should returning visitors be counted?
What happens when someone opens the same document from a laptop and later from a phone?
How should time spent on a page be calculated?
What happens when someone repeatedly moves between the same two pages?
These are tiny details when you look at the finished product.
When you're building the product, each one becomes its own decision.
That's one thing I really enjoy about building SaaS products.
Features that look incredibly simple from the outside can have a surprising amount of complexity underneath them.
One Document Quickly Became Ten Documents
Another thing we learned was that people don't always share individual documents.
A founder speaking with investors might need to share:
◉ Pitch deck
◉ Financial projections
◉ Cap table
◉ Product information
◉ Legal documents
◉ Investor updates
◉ Company information
A sales team might need to share proposals, pricing, case studies, presentations and contracts.
At that point, sending separate links for every document starts getting messy.
That pushed us to think beyond individual document links.
Why We Started Thinking About Deal Rooms
Sometimes the better experience is having multiple documents organized in one place.
That's where deal rooms and microsites became interesting for us.
Instead of sending several unrelated links, a company can create one controlled place where the recipient can access everything they need.
This can make sense for workflows such as:
◉ Fundraising
◉ Investor communication
◉ Sales
◉ M&A
◉ Due diligence
◉ Client onboarding
◉ Partnerships
While working on this part of SendNow, we spent time understanding how traditional virtual data rooms work and how newer document sharing products approach the same problem.
We documented some of that research in our guide to virtual data room and DocSend data room alternatives.
That research changed how I looked at the product.
We weren't only building a better PDF link anymore.
We were trying to improve the experience around sharing important business information.
The Biggest Thing I Learned
Before building SendNow, I thought file sharing and document sharing were basically the same thing.
Now I see them as slightly different problems.
File sharing asks:
How do I give someone this file?
Document sharing asks:
What happens after I give someone this file?
That second question changes everything.
Now you start thinking about the viewer.
You think about engagement.
You think about identity.
You think about security.
You think about access control.
You think about presentation.
And eventually you start thinking about the entire workflow surrounding that document.
That's probably the biggest thing building SendNow has taught me.
We're Still Figuring It Out
SendNow is still evolving.
Every new user seems to have a slightly different way of sharing documents.
Founders have one workflow.
Sales teams have another.
Agencies have another.
Teams doing due diligence have completely different requirements.
That makes the problem interesting because there isn't one perfect document sharing workflow for everyone.
We're continuing to improve SendNow around secure sharing, document analytics, microsites and deal room workflows.
If you're curious about what we're building, you can check out SendNow.
But I'm actually more interested in hearing from other builders here.
What's one feature you thought would be easy to build, but became surprisingly complicated once you started working on it?
I'd love to hear the story in the comments.
Top comments (0)