They Opened It for Twenty Seconds. What Does That Actually Mean?
You sent a proposal you spent two days on. The notification says it was opened, and it says the visit lasted twenty seconds. Somewhere between reading that number and closing the tab, most people arrive at the same conclusion: they did not read it, and they are not interested.
That conclusion is wrong often enough that it is worth taking apart properly. A short read is not one signal. It is at least three completely different situations that happen to produce the same number, and they call for three opposite responses — plus a fourth case where the reader was not a person at all.
First, what the number is measuring
Reading time here counts only while the document is actually on screen. Hide the tab and the count pauses; come back and it resumes. So twenty seconds is not “the tab was open for twenty seconds before they got distracted” — it is twenty seconds of the document being the thing in front of them.
That makes it a much better number than a browser-tab timer, and it still has a hard ceiling on what it can prove. It is an upper bound on attention, never a measure of it. A document can sit on screen while its reader takes a phone call. Nothing detects idleness, and nothing here pretends to. Twenty seconds means at most twenty seconds of attention, and possibly less.
If the mechanics of that matter to you, how reading time is measured honestly covers what the alternatives quietly count instead.
Meaning one: they were filing, not reading
The most common cause of a short read is triage. Something arrived, they opened it to confirm it was the thing they were expecting, and they closed it to deal with properly later. This is not rejection. It is a busy person clearing a queue, and the tell is what happens next.
A filing visit is almost always followed by a real one — the same day, or two days later, usually longer, often on a different device. If you get that second visit, the first one carried no information at all and you should stop thinking about it.
If a week passes with no second visit, the filing visit has quietly become something else: the document is in a pile and the pile is not moving. That is a scheduling problem, not a pricing problem, and it wants a different intervention.
Meaning two: the wrong person opened it
The second cause is that the twenty seconds belongs to somebody who was never going to read it. An assistant checking the link works. A contact scanning it before pushing it into an internal thread. Someone confirming that the file is the right one before printing it for a meeting.
This case has a signature: a short visit followed shortly by a long visit that looks like a different reader — a different browser, a different operating system, sometimes a different approximate location. That pair is the classic shape of a document being passed upwards, and the second visit is the one that matters.
The trap is that you cannot distinguish this from the same person on a second device, because nothing labels a forward. A new-looking reader is evidence, not proof, and the honest version of the sentence is “somebody who does not look like my original reader spent nine minutes in it”.
Meaning three: they already knew what was in it
The least intuitive one, and the one people never consider: a short read after a good conversation is frequently a good sign.
If you had a long call on Tuesday and sent the written version on Wednesday, the document contains almost nothing new. Your reader opens it, goes to the number and the timeline, confirms both match what you said, and closes it. Twenty seconds. Nothing is wrong. The document did its job in twenty seconds because the work had already been done in the call.
The rule of thumb that keeps this straight: judge a read against how much of the document was news to the reader. A cold proposal that gets twenty seconds is a bad sign. A confirming document that gets twenty seconds is doing exactly what a confirming document should.
The fourth case: it was not a read at all
Very short visits are also what automated traffic looks like. Chat and mail clients fetch a link to build a preview card the moment it is pasted; security gateways open every link in an inbound email; crawlers do what crawlers do.
Quixli records those and keeps them out of your counters, your alerts and your digest, and a visit too brief to be a read does not raise an alert either. But no filter is total — a corporate scanner that presents itself as an ordinary browser is genuinely hard to separate from a person, and telling a real reader from a scanner is a subject of its own.
The other phantom is you. Your own opens and your colleagues’ are marked and kept out of the client-facing numbers, so a short read in your dashboard is at least somebody outside your workspace.
How to tell them apart
You cannot do it from the duration. You do it from the three things around the duration:
- What happened next. A return visit resolves nearly everything. Filing plus a return is a normal read. Filing with no return is a stalled document. This is why the interval matters more than the number.
- Whether the second visit looks like the same reader. Same browser and system, likely the same person coming back. Different, and your audience may have widened.
- What the document was for. A cold document needs minutes. A confirming document needs seconds. Compare against the job, not against an industry average that nobody can source.
Do not build a benchmark out of other people’s numbers
There is no defensible figure for “the average time a proposal is read for”, and anyone quoting one to you is quoting a number from a population that does not include your documents, your industry or your length.
Build your own instead, and it takes about ten sends. Record the reading time on every document you send along with what the document was and whether the deal closed. After ten you will have a baseline that is actually about you — and the useful comparison was never against an average anyway, it was against your own last five.
What you must not conclude
- Not “they did not read it”. A short visit is consistent with three different readers, two of whom read it perfectly well.
- Not “they are not interested”. Interest is a state of mind; you measured a duration.
- Not “they skipped the pricing”. Nothing records where in a document a reader got to — there is no scroll depth and no section-by-section view, so any claim about which part they read is invented.
The wider version of that last point — what a document tool can and cannot see — is set out in what Quixli tracks, limits included. And the companion question, what separates a document being opened from being read, is the one to read next.