Insights & updates
Product updates, tutorials, best practices, and stories from the Quixli team.
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.
What Document Analytics Can Never Tell You
The limits are the feature. What no amount of document tracking will ever tell you — which section they read, who they are, how many they were, why they did not open it — and the four things it genuinely can.
How to Write a Discovery Questionnaire Clients Actually Complete
The only client document whose success is measured by what comes back. Why a questionnaire is usually an internal checklist made public, four rules before you write a question, and the grouping change that makes a long one routable.
How to Submit a Proposal to a Procurement Process
A tender response is a compliance document that also has to persuade. Why inverted-pyramid advice is wrong here, where format compliance is free marks, and why the tracking blackout is the process rather than your tooling.
Sharing a Document With Your Team Without Losing Track of Who Sent What
Two people, two links, one client, and neither can see the other’s numbers. Four rules that fix it — including the visibility default, the part admins always see whatever it is set to, and why forwarding a client link internally corrupts the data.
You Sent a Report to Nine People. How Do You Find Out Who Read It?
A report has an audience, so the question is who has not read it — and one shared link cannot answer that. The per-recipient setup that can, what to read instead of engagement, and two ceilings to know first.
How to Write a Renewal That Is Not Just an Invoice With a New Date
A renewal is the one proposal where you already have the evidence, and it is still the one most often lost. Why the client is really asking what would happen if they stopped, the seven sections, and why proposing to stop doing something is your most credible paragraph.
How to Send a Proposal to Several People at the Same Company
Three to eight people will have an opinion and you have one address. When a link per person is worth it, why the address you mailed it to still is not an identity, and the one rule with no exceptions.
What Your Reader Can and Cannot Find Out About Themselves
The same arrangement from the other chair. What the reader is told, what a curious one can establish for themselves, what genuinely works if they would rather not be counted — including the two signals we do not honour.
Do Your Own Views Show Up in Your Document Analytics?
Your own opens and your team’s are marked and kept out of every client counter, alert and digest — and shown separately with no names. Why exclusion alone was not enough, and the three ways it still fails.
How to Write a Handover Document at the End of a Project
A handover is read in March by somebody who has never met you, after something has broken. The eight sections, why the “why we did it this way” entries are the part that cannot be reconstructed, and the ownership transfer checklist people get wrong.
How to Name and Version a Document a Client Will Receive
The document name is the only part of your work everyone reads, including people who never open it. A naming rule that survives their filing system, and the versioning discipline a link needs — because editing in place is silent.
What to Say When a Client Asks If You’re Tracking Them
Start with the word yes, on its own. What to say next depending on which of four things they were actually worried about, five phrasings that lose the room, and what to do if they ask you to stop.
Was That a Real Reader or a Link Preview? How to Tell
An open in the same minute you sent is almost never your client. The three kinds of non-human visit, the one that no filter can reliably catch, and the four-signal test that identifies it.
What Belongs in a Capability Deck
A deck you present and a deck you send are different documents, and most people send the first. The seven things a sent capability deck needs in order, why a deck with no price gets forwarded to nobody, and what to cut.
Should You Password-Protect a Document You Send a Client?
A PIN is a real control with a real cost: it has to reach the reader somehow, and the reader it most often blocks is the senior one who arrived through a forward. When it earns its place, and why a PDF password is a worse version of it.
How Long Should You Keep Read Data? Less Than You Think
Read data answers one question, and that question expires when the deal does. What keeping it costs you, exactly what Quixli retains and for how long — including the default we think you should argue with — and a routine that survives a busy month.
Opened Versus Read: Which One Does Your Document Tracking Actually Know?
Opened is measured. Read is inferred from time on screen, and time on screen is an upper bound on attention. Understood is not knowable at all — and the sentence you write matters more than the number.
How to Write a Case Study a Prospect Will Actually Finish
A case study is evidence, not marketing, and it fails by being about the sender. How to open on the constraint rather than the client’s name, the seven parts, why every number needs its method attached, and why sending three is sending none.
Should a Proposal Link Have an Expiry Date?
An expiry date does not choose who it stops — and the reader it stops is disproportionately the late-arriving senior one who can sign. The four cases where it earns its place, and the better instrument for the rest.
Consent, Cookies and Tracked Links: What GDPR Actually Applies
Two laws govern this, not one: ePrivacy Article 5(3) governs the cookie, GDPR governs the data, and confusing them is why people either panic or ignore it. What each requires, cited, plus the signal we do not honour.
They Read It and Did Not Reply: What Silence Means at One Day, One Week, One Month
A two-day silence and a two-week silence are different events. What an open with no reply means at each interval, the return visit that overrides all of them, and the rewrite to resist.
The Client Onboarding Document: What to Send After They Say Yes
The gap between a signature and real work is where small projects lose their first fortnight. Why an onboarding document is an operations manual rather than a welcome letter, the seven sections, and how to write the access list that decides week one.
Where Should Pricing Go in a Proposal?
Burying the number does not delay it — it makes the reader hunt for it while thinking about nothing else. Where the price belongs, the four things that must sit beside it, and the difference between a validity date and an expiring link.
What a Tracked Link Actually Collects — and What It Doesn’t
The full inventory, both columns. Six things a tracked link records, six things people assume it records and it does not, what happens to all of it afterwards — including the retention default we think you should argue with.
Five Opens in One Afternoon: Has Your Document Reached a Committee?
A cluster of opens in one afternoon usually means your document was circulated. The three innocent explanations to rule out first, the texture of a real committee read, and the control not to reach for.
The Project Status Report Clients Actually Read
Green, green, green, red is how status reporting fails, and trust dies at the transition rather than at the red. Six sections in the order that gets them read, why percentages are worse than states, and how to escalate in small amounts.
How to Structure a Proposal So the Part That Matters Is Read First
The conventional proposal order is sequenced by the work you did, not by what the reader needs. The inverted-pyramid version, the three sections read least, and how to test an order when no tool can show you which section was read.
Should You Tell a Client You Can See They Opened It?
Disclosure and narration are different questions with opposite answers. Yes, they should always be able to know. No, you should almost never tell them what the numbers say — and here is exactly when the exceptions apply.
Is There a Best Day to Send a Proposal? What Your Open Times Can and Cannot Prove
A timestamp is a fact about your clock, not your reader’s. Why day-of-week theories die on contact with your actual send volume, how to test one properly, and the two timing patterns that work on a single document.
How to Write a Statement of Work
A scope document is read by somebody who is annoyed, in six months, and was not in the room. The eleven sections in order, how to write an acceptance criterion that turns “done” into a test, and why change control is how you say yes.
Should You Send a Proposal as a PDF Attachment or a Link?
An attachment generates no evidence at all, by construction. A link asks for a click people are trained not to make. What each really costs, and the trap in the obvious compromise of sending both.
Is It Ethical to Track a Document You Sent?
Measuring a document you made and profiling the person who reads it share a name and nothing else. Three tests for where the line sits, the case that does not resolve cleanly, and the features we declined to build.
They Read It on a Phone: What That Changes, and What It Does Not
Device tells you about the circumstances of a reading, not the reader’s intent. What a mobile visit genuinely implies, why it inflates your reader count, and the pattern of phone-then-laptop worth acting on.
What to Put in a Quote or Estimate (and What to Leave Out)
A quote is the shortest document you send and the one where a missing sentence costs the most. What goes in, in what order, why the exclusions section is the whole document, and why a single number is an ultimatum rather than a quote.
Does a Proposal Need a Cover Page?
A cover page spends your most valuable screen on two facts both parties already have. What the convention was actually for, why the link preview inherited its job, and the four cases where it still earns its place.
They Opened It for Twenty Seconds. What Does That Actually Mean?
A twenty-second read is three different situations wearing the same number: filing, the wrong reader, or a document that only had to confirm what was already agreed. How to tell which one you are in.
How Long Should a Proposal Be? (And How to Find Out for Your Own Work)
Every published answer is an average over industries that have nothing in common. Here is why length is a proxy for the wrong thing, and a ten-send measurement that finds the real number for your own work.
They Never Opened It: What Silence Actually Means
No opens at all is the one signal with no ambiguity in it, and the one most often misread as rejection. What it really diagnoses, why it is trustworthy, and the five things to check before you change a word.
What “Unique Readers” Actually Counts — and Why It Has an “At Least” Sign
A unique-reader count merges signed-in and gate-identified visits and falls back to the browser. Four things move it in both directions — and one, much larger, that only ever moves it one way.
How to Follow Up on a Document You Know Was Read
You know it was read. They do not know you know. What the signal is really for — timing and framing, never a sentence — and what to send in the four situations you will actually be in.
Should You Ask for an Email Before Someone Can Open Your Document?
A gate buys you an address given at the moment of intent — and never a verified one. What it genuinely gets you, why its cost is invisible in your own numbers, and how to measure that cost properly.
What a Forwarded Link Can and Cannot Tell You
Nothing in your analytics ever says “forwarded” — you infer it. What a forwarded link actually looks like in the data, why the address you mailed it to is not the reader, and how to write for the person you never sent it to.
What a Second Opening of Your Proposal Actually Tells You
The first open is a response to a notification. The return visit, the long read, the second reader and the silence are the four patterns that actually carry information.
How Accurate Is IP-Based Location, Really?
Country resolution is near-certain; city resolution is not, and its error is systematic rather than random. Why an entire region piles into one capital, and what to do about it.
Why “Time Spent Reading” Is Usually Wrong — and How to Measure It Honestly
A reading time computed from when a tab opened and closed only ever exaggerates. Here is the method that does not — measuring in confirmed slices, and crediting nothing for silence.
Email Open Tracking vs. Tracked Document Links: What Each One Actually Measures
A tracking pixel measures an image request. A tracked link measures a reading session. They fail in different directions, and only one of them can see a forward.
How Do You Know If Someone Read Your Proposal?
Read receipts, tracking pixels, PDF attachments and tracked links — what each one actually measures when you are waiting on a proposal, and where each one lies to you.
How to Create a Professional Proposal Document in Minutes
A step-by-step guide to creating professional business proposals in minutes — from structure and pricing to sharing and tracking.
Document Sharing Best Practices: View Limits, Expiration Dates, and Access Control
Best practices for document sharing — including view limits, expiration dates, PIN protection, audit trails, and access control policies.
How to Share Documents Securely with PIN Protection and Expiry Links
Learn how to share documents securely using PIN protection, expiring links, view limits, and audit trails to protect sensitive business content.
How to Create Shareable Documents Online (Without Google Docs)
Learn how to create and share professional documents online with rich formatting, access controls, and export options — no Google Docs required.
How We Built Real-Time Collaboration
A deep dive into building real-time collaboration with Yjs CRDTs, Hocuspocus WebSocket server, and ProseMirror integration.
Introducing Quixli: A New Way to Build Documents
Meet Quixli — a modern document creation platform with a powerful block editor, real-time collaboration, and smart organization tools.