Insights & updates
Product updates, tutorials, best practices, and stories from the Quixli team.
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 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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 We Built Real-Time Collaboration
A deep dive into building real-time collaboration with Yjs CRDTs, Hocuspocus WebSocket server, and ProseMirror integration.