Reviewed: spryplan.com homepage (12 mobile screenshots, 24 Sep 2026) and the full text of the blog post "Ways of Working Template (Free, 2026)", dated 10 Jun 2026, the newest card on the homepage.
Structural read against the pages as published · 7-point Decision Friction Model
The seven Decision Friction checks were applied to web copy instead of email. The hero headline stands in for the subject line, the hero paragraph for the lead, and the section headings for the feature to outcome check. The score is structural: the order in which information reaches the reader. It is not a design, SEO or deliverability score.
Scope and limits. Twelve mobile screenshots of the homepage and the full text of the latest post. Gaps between screenshots were not reviewed. No links were followed and no analytics were available, so nothing here is a funnel number.
AVERAGE 31 / 7 = 4.4 · BAND 3.5 to 5.5 · COMPETENT BUT LEAKING
Clear and professional, nothing embarrassing, and the information arrives in the wrong order. That is the band where nothing looks wrong, which makes the leak expensive.
The seven patterns, explained. Each pattern is a recurring structural failure in the order information reaches the reader. Six were found on these pages.
The button verb places the reader outside the action, observing the company's offer instead of making their own decision. "Learn more" is guest language. "Fix my reporting" is ownership language.
On Spry
"Book demo", "Request pricing", "Request access to Spry".
The copy leads with what the product does instead of what changes for the reader.
On Spry
Steps two and three: "Sync and reserve" and "See the insights" describe mechanics before results.
The headline announces the topic like a folder tab. It gives no consequence and no reason to open.
On Spry
The article title "Ways of Working Template (Free, 2026)" names the topic and the year.
Everything carries equal weight, so no single item or next step dominates.
On Spry
The dashboard cards show several percentages side by side, and the headline number, Deep work 15%, has no legend entry.
An improvement is claimed with a bare figure or an adjective instead of a before/after pair with a baseline and a measured result.
On Spry
"3-5 hours save per week" and "40% more focus time" state a gain with no starting point.
The outcome is buried behind qualifications, context or disclaimers, so the caveat arrives before the point.
On Spry
The hero states the consequence first: "Every hour has a cost."
No third-party voice, named result or sourced number appears, or the proof sits below the point where it would reduce hesitation.
On Spry
The impact block and the blog post carry no customer name, quote or source.
The demo integrity issues in the Demo data tab are an extra finding, not an eighth pattern.
The block titled "See measurable impact" carries four figures and nothing measurable about them. There is no company, no team size, no period and no before value. A reader who wants to trust "87% fewer status calls" has no way to ask: 87% of what, for whom, over how long?
"3-5 hours save per week"
"50% fewer follow-up meetings"
"40% more focus time"
"87% fewer status calls"
The savings promise also changes between pages. The homepage says 3-5 hours a week. The related reading on the blog post promises to cut 6 to 10 hours of meetings a week in one title, and to go from 8 hours to under 4 in another. The article's own example goal, 18 hours down to 12, is a sixth. A buyer comparing the pages finds three promises and no method behind any of them.
The "18hrs" stat has a second problem. The homepage presents it as time lost per team member. The article says knowledge workers at 150+ person companies spend 15 to 25 hours a week in meetings, with no source, and uses 18 to 12 as a hypothetical goal. "Spent in meetings" and "lost" are different claims, and the site treats them as one.
"18hrs lost per team member weekly"
Blog post · goal example"Reduce average meeting hours per person from 18 to 12"
The article teaches the standard the homepage misses. It says "Improve meeting culture" is not a key result and asks for a baseline, a target and a date. The proof block has none of the three.
The homepage asks for "Book demo" in the nav and again under the hero. Each of the three tiers ends in "Request pricing" with no price on it. The blog post closes its product section with "Request access to Spry" and its footer block with "Book demo". Three action names cover what is one funnel, and each one places the reader outside the action, waiting for the company to respond.
Nav and hero: "Book demo"
Starter, Growth, Enterprise: "Request pricing"
Blog post, product section: "Request access to Spry"
Blog post, closing block: "Book demo"
The nav also holds "Meeting Cost Calculator", the one asset that delivers the homepage promise ("Put a price on time") in seconds. It sits as a text link at the same weight as "Blog". Neither hero CTA points to it. A reader with thirty seconds of curiosity has one visible route: talk to sales.
The tier copy adds no way to self-select. Starter is "For small teams ready to cut wasted time." Growth is "For scaling orgs with more complexity." Enterprise is "Advanced security & integrations." No seat count, no feature difference, no starting price.
The article does one thing right here. "See your team's meeting load" is ownership language: the reader performs the action. The next words, "Request access to Spry", hand the reader back to a queue.
Spry's promise is accurate time accounting. The demo screens do not pass a simple check. None of the demo data is labeled as illustrative.
"Meetings time 18% 12%" (green up arrow)
"Transition time 33% 13%" (red down arrow)
"Buffers 43% 7%" (red down arrow)
Small copy details sit in the same family: the impact card reads "hours save per week", and the FAQ heading reads "Frequently asked question", singular.
The opening is reader-first and specific: a new hire arrives with old habits and books a 30-minute sync for a Slack message. The six norms are concrete. The post earns attention. The structure then works against the product.
The intro says the free template is at the bottom. The next section says here it is, and later the text calls it the template at the top of the page. A reader who scans for the download and finds it early has no reason to reach the product section.
"The free template is at the bottom."
"If you're here for the template, here it is."
"How Spry Helps You See If It's Working" comes after the template, six norms, goals, three document types, the personal version and before the FAQ. The reader who came for the template has already left. The bridge also leads with mechanics: calendar analytics, hours in meetings, recurring meeting cost.
The "How to Work With Me" section lists six items and offers no file, link or CTA. The only download in the text is the company guide.
The FAQ says the guide belongs to the COO, Head of People or a founder. The product section says "Spry gives managers the data". The stat is about companies of 150+ people, while the homepage opens with a Dev team and a Starter tier for small teams. Three audiences appear in one page.
A post about meeting overload, on a site with a free Meeting Cost Calculator in the nav, does not mention the calculator anywhere in the body text reviewed.
"Ways of Working Template (Free, 2026)" names the topic and the year. It works as a search title. It gives the reader no consequence for the meeting problem the article itself describes so well.
Read type: UX-level, from screenshots and article text. Not instrumented. No analytics access was available, links were not followed, and no funnel numbers are stated.
"See your team's meeting load"
"Request access to Spry"
To close this section with data, the click-through from article CTA to first meaningful action would need to be traced in the product analytics: article view, CTA click, form or signup completion, first value event.
Every finding traces to one root cause. The product's promise is measurement, and the pages do not demonstrate measurement anywhere the reader looks.
A reader reaching "See measurable impact" has one question: measured where, on whose team, over what period? The page does not answer it, and the next click is a sales conversation. That is where the structural score loses its points.
This teardown is diagnosis only. The solutions for every finding above are delivered through the Decision Friction Review.