DocSend is, in our view, one of the most quietly important pieces of fundraising infrastructure shipped in the last fifteen years. The per-slide dwell heatmap changed the way founders read investor interest, and the change was real — it pulled the deck out of the "hope they read it" category and into the "you can see them reading it" category.

We use DocSend ourselves at meetings outside our own workspace. We are not here to tell you it is bad. We are here to describe what changes when the heatmap is no longer a standalone artifact, but a panel inside the same workspace where your investor pipeline, your data room, and your CRM live.

What DocSend does, accurately.

DocSend is a deck-sharing tool with three core capabilities:

  • Per-slide dwell analytics. You can see, per recipient, how many seconds they spent on each slide.
  • Tracked links and version control. Re-share the same link after a deck update; nobody is reading v3 thinking it is v5.
  • NDA / email gates. Lightweight friction before a viewer can open the deck.

For pre-Series A companies that only need the deck to be tracked, DocSend is the obvious choice. It is sharp, focused, and the analytic is best-in-class.

What DocSend deliberately doesn't do.

DocSend does not know who the viewer is, in the larger sense. It knows their email, it does not know which fund they sit at, which partner you spoke to last Tuesday, which stage of your pipeline they are in, or which customer reference they were promised after the second call.

That is not a flaw. DocSend ships a focused tool. The cost is that the heatmap is, by design, a standalone signal — and standalone signals are weaker than the same signals viewed against context.

A 90-second second visit to your TAM slide is interesting. A 90-second second visit from a partner whose investment thesis sits one stage past where you currently are, on the day you sent a follow-up email, is a decision.

What Arx does differently.

Arx integrates the same deck heatmap directly into the investor record. When you open a partner's row in your pipeline, the deck section shows you their visit history — first view, return views, slide-by-slide dwell, and which slide they spent the most time on across sessions.

The behaviour change is small and important. You are not flipping between three browser tabs to assemble a picture of an investor. You are looking at one row, with all the context already joined.

Practically, that means:

  • Briefing for the second call is a one-screen view, not a search-DocSend-then-search-Notion exercise.
  • Heat triage during a round is a sortable list — every partner who spent more than 60 seconds on slide 7 in the last week, ordered by recency.
  • Updates can include a "investors who re-read your deck since the last update" cohort, not just everyone you have ever emailed.
  • Diligence questions the deck does not answer can be matched, in the same workspace, against the data room link you sent that same partner.

It is not that DocSend cannot be made to do these things. It is that they require manual stitching — copying viewer lists, exporting to Notion, joining against your CRM. The stitching takes hours every week. The hours are time you could have spent on the round.

The honest overlap.

Arx and DocSend overlap on three things:

  • Tracked links with per-recipient analytics.
  • Per-slide dwell heatmaps.
  • Version control for deck revisions.

We do not think we are better than DocSend at any of these in isolation. DocSend's analytics surface is more mature and has more polish on edge cases — large decks, complex PDFs, weird timezone handling. We are catching up on edge cases; we are not pretending to be ahead.

The case for Arx is not that we have a better heatmap. It is that the heatmap is more useful when it sits next to the rest of the round.

A worked example.

Imagine you sent your deck to a partner at a notable seed fund on Tuesday. By Thursday morning, three things have happened that you'd like to know about:

  1. The partner opened the deck for 90 seconds at 11pm Tuesday, mostly on slide 1.
  2. On Wednesday afternoon, the same partner opened the deck a second time, spent four minutes, and returned to slide 7 twice.
  3. On Thursday morning, an analyst at the same fund opened the deck for ninety seconds, on slide 1 only.

In DocSend, you have three line items in the viewer log. You can read them. You will probably stitch them together by hand into "I think the partner is interested, they came back for slide 7, the analyst is doing surface-level diligence."

In Arx, the same three events surface as a single annotated card on the partner's row in the pipeline — "Re-engaged Wednesday, returned twice to slide 7 (TAM), analyst-level diligence opened Thursday." The Slack channel or the digest you set up nudges you to follow up that afternoon. The next "intro requested" badge on the same row is on by Friday.

The difference is not the underlying data. It is the friction between the data and the decision.

Pricing and the small-print case.

DocSend pricing starts around $15/user/month for the basic tier, and rises to $65–$250/user/month depending on the level of analytics and the seat tier. For a two-founder team with one deck and one data room, you are looking at $30–$130/month, conservatively, depending on plan.

Arx is $99/month, flat, unlimited seats. That includes the deck heatmap, the data room, the CRM, the cap table, the forecast, and the updates pipeline. We are not undercutting DocSend on a per-seat basis; we are bundling.

For a single founder who only needs a deck-sharing tool, DocSend is cheaper than Arx. For a founder running a full seed round, Arx is cheaper than DocSend + Notion + Pulley + Mailchimp + Calendly, by a meaningful margin.

When DocSend is the right answer.

We think DocSend is the right answer for two distinct cases:

  • You already have a workspace and just want a heatmap. If your CRM lives in Affinity, your deck in Figma export, your updates in Substack, and you only need the heatmap — DocSend is sharp and focused. Adding Arx would be over-buying.
  • You are post-Series A and the deck is a long-lived artifact. Mature companies share decks for partnership conversations, BD, customer onboarding. DocSend's polish and ecosystem are well-suited to that. The case for an integrated workspace is weaker when you are not running a round.

When Arx is the right answer.

  • You are running a round. You are mid-pipeline, your deck is one of six surfaces you care about, and switching tabs is a tax you can no longer afford.
  • You are running multiple rounds. Some companies run a seed and an extension nine months apart. The same investor list, the same deck history, the same context — useful if it lives in one place.
  • You want the deck analytic to fire downstream actions. Auto-add to the digest. Auto-flag for the next update. Auto-create a "follow up" task for the second-call queue.

The summary.

DocSend is a tool. Arx is a workspace that contains a tool that does what DocSend does. The right question is not "is the standalone tool better?" — DocSend often is, at the margin — but "is the friction of stitching the standalone tool to everything else worth the polish?"

For most founders running a seed round today, our answer is no. We think the round is the unit; the deck is a slice of the round; the slice belongs in the same workspace as the other slices.

If you disagree, DocSend is the right call and we'd be the first to recommend it. If you agree, we built the alternative for you.