Stop sending your sales deck as a PDF.

What happens to a PDF after you send it?

It starts a life you cannot see. Your contact downloads it, saves it to a shared drive, forwards it to a colleague with a one-word question and maybe prints it for a meeting. Each of those is a separate copy, frozen at the moment you exported it.

Then the versions pile up. Picture the sales team at Harbor Logistics, whose deck is called Sales_Deck_FINAL_v7.pdf. Versions five and six still sit in inboxes on the buyer's side, and nobody is sure which one their finance lead read before the pricing call. The deck was fine. The way it travelled was the problem.

How does your deck look on their phone?

A lot of first reads happen on a phone: between meetings, in a taxi, in the minute before a call. A PDF made from widescreen slides arrives on a tall, narrow screen as a row of tiny landscape pages. The reader pinches, zooms, scrolls sideways through the pricing table and gives up on the chart labels. Nothing about your offer changed, but now it reads like work.

A deck sent as a web page can reflow. Headings stay large, text wraps to the width of the screen, tables stack and the reader scrolls down the way they read everything else on a phone. You do not design a second, mobile version. The same pages adapt.

Try this firstBefore you send anything, open it on your own phone and read it from start to finish. If you would not read it that way, neither will they.

What if you need to change something after sending?

You will. A price is wrong, a date moved, legal wants a sentence softened, or the buyer asked for a second option on the call. With a PDF, every change means a new file and a new email that starts with an apology. Now there are two copies in their inbox, and you are relying on them to delete the old one.

With a link, you fix the page and the link shows the new version. Nobody digs for the right attachment, and the colleague who opens a forwarded link next week sees the current deck, not last Tuesday's.

One rule keeps this honest: if a change matters to their decision, say so. Quietly swapping a price is how trust goes. Send a short note, such as "We added the annual pricing option you asked about. It is on page 5." Keep the version history too, so you always know which version a reader saw.

Can you see what happened after you sent it?

With an attachment, sending is the last thing you know for sure. After that you are guessing. Did they open it? Did it reach the person who signs? Did they stop at the price?

A link can tell you what happened, as plain facts. In Decktrace, every open shows when it happened, on which device and in which language, how long the reader was active on each page, how far they scrolled and whether they came back. When your link is shared further, you see the new readers too. Your own previews and link scanners are left out, and readers on an open link are counted by device. Readers see a short notice about what is measured, so none of it happens behind their back.

Take Brightlane's proposal for Harrow Retail, "Cut onboarding time in half." Olivia Bennett verified her email when she opened the link, so the report shows her verified address. She read it on her phone, went through all six pages and spent the longest on the rollout plan, where she also asked a question. Your follow-up now has a subject, and it is the rollout, not "just checking in".

Two cautions. Facts are not feelings: a long time on the pricing page might mean interest, confusion or someone copying numbers into a spreadsheet. And on an open link you see an anonymous reader on a phone, with an approximate location, not a name. That is still far more than an attachment tells you.

When is a PDF still the right call?

Sometimes the file wins, and pretending otherwise would be bad advice.

• Procurement portals and tenders. If the buyer's process asks you to upload a document, upload the document.
• Anything that will be signed. Contracts and order forms need a fixed version that cannot change after signature. A page that updates is the opposite of what you want there.
• Readers who will be offline. A board pack read on a flight, or a reviewer whose network blocks outside links.
• A buyer who asks for one. Some people keep a file of everything. If they ask for a PDF for their records, send it.

The pattern that works is a link as the main thing and a file on request, made from the same source so the two never disagree. If your deck already exists as slides, you do not have to start over either. Save it as a PDF and Decktrace keeps it page by page inside a web deck, with its text extracted so questions and reading data work on it. PowerPoint import and rebuilding pages as editable web pages are coming soon.

How do you send a link without it feeling odd?

A bare link can look like spam, and "click here" tells the reader nothing. Write the email the way you would hand someone a document across a table:

• One line on why you are sending it and what it answers.
• The link with a plain label, such as "Harrow Retail proposal, six pages".
• How long it takes to read, so they can pick the moment.
• An offer of a PDF if they prefer one.

Decide up front whether readers verify their email before the deck opens. It gives you a verified email for each reader, and it adds a step. For a buyer you already talk to, it is a fair ask. For a first message to someone who has never heard of you, an open link asks less of them.

A checklist for your next proposal

• Read it on your phone, start to finish, before anyone else does.
• Send one link from one source, not a numbered file.
• Decide whether readers verify their email before it opens.
• Say in the email what the deck answers and how long it takes to read.
• Fix mistakes on the page, and tell the buyer when a change affects their decision.
• Keep a PDF ready for portals, signatures, offline readers and anyone who asks.
• Read what happened before you follow up, then follow up on that.