The distance between a headline and what you actually get

What we're tracking

• •A vendor's first profit is a signal, and a trade-off When you commit to a tool, you are committing to the company behind it. You want it to still be there in three years, still fixing bugs, still adding the thing you will need next year. A vendor's financial health is part of what you are buying, even though it never appears on the feature list.
• •A headline multiple is not a return The same gap appears in how deals are reported. SaaStr described one of its older fund companies being acquired: "It is selling for 3.8x what we paid to get in years ago" [2]. On paper that reads like a strong outcome. The real return, after dilution across the years in between, comes in under 1.6x.
• •The agent you still have to build Automation is increasingly sold as something you assemble yourself. At Xerocon London, Xero showed XeroForce, and described it plainly: "We showed customers how to create agents that automate key workflows using simple, natural language prompts" [3]. No-code tools that let you build your own agents are genuinely useful, and they lower the barrier to automating repetitive accounting work.
• •"In the coming weeks" is not "today" Google's weekly recap led with a feature that is close but not here: "Visual screenshots in Google Meet meeting notes will soon be generally available, pre-configure admin settings in advance" [4]. The recap is explicit that this is a forthcoming rollout, and it asks administrators to set up their controls ahead of time.
• •The performance you never see Some of the most consequential work in software is the part a buyer never notices. GitHub published an engineering piece on how it case-folds code during search: "How a branch-free loop and byte-space arithmetic let GitHub case-fold every byte of code search at >45 GiB/s on a single core" [5].
• •What runs through the day Five different announcements, one recurring shape. A profit that comes with slower growth. A multiple that shrinks before it is realised. An automation whose cost has quietly moved to you. A feature that is weeks away. And engineering work you will only ever notice by its absence. In each case the headline is true and the useful detail sits just behind it.