Sent. Opened.
Read twice.
That is the whole story a link from Quixli tells you — who opened your proposal, when, how long they stayed, and whether they came back.
no credit card · every share link is tracked
Write it here, so the link is yours
Rich text, media embeds, tables, diagrams and live data blocks — all on one canvas. The document lives at an address you control, which is the reason anything after send is visible at all.
And the elements a client document actually needs: in-scope and out-of-scope columns where an exclusion can say what it would take to include it, numbered clauses that renumber themselves when you move one — cross-references and all — and priced packages the reader picks between. Five templates start you past the blank page, and eight themes settle how it looks.
The silence after you send
What you learn after sending
Hear about it while it still matters
An email and an in-app notification land shortly after a real visit — not every refresh, not your own opens. Prefer one summary? Take the daily digest at 8am in your own timezone instead.
Reading right now
See open sessions as they happen, so you know when the document is in front of someone.
Every visit, timed
Each session is recorded with its own duration, and reading time counts only while the document is on screen.
Optional email gate
Ask an unknown reader for an address before the document opens. It is self-reported and never verified — we show it as exactly that.
PIN, expiry & view limits
Put a pincode on a link, give it an end date, or cap how many times it can be opened.
Which part they stopped on
Not just that the proposal was opened — which section held them, which they passed over, and which one they came back to the next day. That is usually the price, and it is the difference between chasing and knowing what to say.
You get it as a sentence, not a table of seconds. And it stops where the evidence stops: this measures what was on screen, never what was understood.
Most of their attention went to “Investment” — 4m 12s of 9m 30s. They came back to “Investment”. They passed over 2 sections.
Time each section spent on screen, counted only while the tab was in front and the reader was active. It shows what was in front of them, not what they read.
Write it, send it, watch it land
Write the document
A proposal, a quote, a scope of work — from a template that already has the scope, the clauses and the pricing in it.
Send a link, not a file
Add a pincode, an end date or a view limit if the contents warrant it.
See what came back
Every session with its duration, the sections that held them, and a PDF report you can send on.
If you send work to clients
One person or five — the question after you send is the same one.
Follow up on the right day
Chase the quote that was read twice, not the one that never got opened.
Show the work was received
A dated record of every session, downloadable as a PDF for the file.
Everyone sees the same activity
A shared workspace with roles, so a hand-over does not lose the history.
Against how you send it today
An attached PDF tells you nothing. A plain link tells you nothing. Both are the reason you are guessing.
| Quixli link | PDF attachment | Plain link | |
|---|---|---|---|
| Know it was opened | — | — | |
| Know when it was opened | — | — | |
| Time spent reading | — | — | |
| Repeat visits, one by one | — | — | |
| Reading right now | — | — | |
| Email alert & daily digest | — | — | |
| PDF report of the activity | — | — | |
| PIN, expiry & view limits | — | — | |
| Always the current version | — |
Compared against sending the same document as a file or as an untracked URL.
The number, or nothing
Any tool can put a figure on a dashboard. What separates them is what happens when the figure would be a guess. Here is what we do instead, in each case where we could get away with guessing.
Reading time stops when the tab does
Reading time counts only while the document is on screen. Hide the tab and the count pauses; come back and it resumes. A document left open in a background tab over lunch does not come back as a 47-minute read. What you quote to a client is time somebody actually spent looking at the thing you sent.
Attention is not reading, and the report says so
You can see which sections of a document were on the reader’s screen, which they passed over and which they came back to. What that measures is what was in front of them — not what went in. The report is written to that limit: it never tells you a section was “read”, because a screen cannot know it. You get the part that is true, which is the part worth acting on.
A typed-in address is never shown as a confirmed one
Every session is graded identified, self-reported or anonymous. An address someone typed into the email gate is badged self-reported and says, on the badge, that nobody verified it. An address you mailed the link to is not treated as an identity at all — links get forwarded — so it reads “someone with the link sent to …” instead of being printed as a name.
A count that can only be wrong one way says so
Unique readers are shown as “≥ 12”, not “12”. A reader who blocks cookies looks like a new person on every visit, so the figure is a floor rather than a total. We would rather print the sign than let you repeat a number to a client that we cannot stand behind.
The free plan withholds identity rather than blurring it
On Free, the reader’s name, device, location and per-browser id are withheld outright, not obscured behind an upgrade prompt with the answer sitting underneath it. The same rule covers the alert email, the in-app bell and the PDF report. Free shows the first three readers of each document, up to twenty people in total, and once you have seen someone they never lock again.
A price we cannot confirm is not printed
Every figure on the pricing page is read from the billing catalogue at request time, never from a number remembered in the code. If it cannot be read, the page shows no price and points you at a person, and the checkout refuses to open rather than failing at the payment step after you have already decided to buy.
Embedded integrations you love
Bring your favorite tools directly into the document you send.
Latest from the blog
The Security Questions a Client’s IT Team Will Ask About Your Link
Eight questions, straight answers, including the four where the honest answer is that the thing does not exist: no SOC 2, no ISO 27001, no SAML SSO, no customer audit log, and no residency guarantee.
How to Write a Design Rationale That Survives a Client Review
Creative work sent without a rationale gets reviewed as taste, and taste is an argument nobody wins. How to convert every decision into a constraint, the five sections, why you should show the option you rejected, and the adjectives to cut.
What Happens to a Shared Link When the Person Who Sent It Leaves?
Three possible answers, two of them bad: links that die with the account, ownership that silently transfers, or links that keep working with somebody told they are unowned. What Quixli does, what it costs, and the offboarding checklist.
Questions, answered
What exactly do you track?
That a share link was opened, when, by which visitor, how long each session lasted and how many times they came back — and, section by section, which parts of the document were on their screen and for how long. Sections are identified by their headings. That last part measures what was in front of the reader, not what they read: nothing can tell you whether somebody was reading, and the report never pretends otherwise.
Do I find out who the reader is?
If you sent the link to a named address, or if you switched on the email gate, an address sits next to the sessions. A gate address is typed in by the reader and never verified, so we label it as self-reported rather than as proof of identity.
How quickly do I hear about a view?
An email and an in-app notification go out within a minute or two of a real visit — bots, your own opens and glances too short to count are filtered out. A daily digest arrives at 8am in your own timezone if you prefer one summary.
Does the reader know they are tracked?
Every shared document carries a link to a privacy notice written for the person who received it, which states what is recorded — the visit, the duration, and which sections were on their screen — and what is not. Tracking nobody could find out about is surveillance, not analytics.
Can I lock a link down?
Every share link supports a pincode, an expiry date and a maximum number of views, and you can end access at any time.
What does Quixli do when it is not sure?
It says so, in the number itself. Reading time counts only while the document is on screen, so time in a background tab counts as nothing. An address typed into the email gate is labelled self-reported, never confirmed. Unique readers are shown as a floor — "≥ 12" rather than "12" — because a reader who blocks cookies looks new on every visit. And a price we cannot read from the billing catalogue is not printed at all.
Can my team see it too?
A team workspace puts shared documents, roles and their activity in one place, billed per active member. On your own, a personal workspace does the same for one.