Journal 038
From Calculator to Clarity
Wayli began with calculators, questions and a growing realisation that the real product was understanding.
Nick B.
Journal entries
Journal 037
When AI Retrieves the Wrong Page
A technically healthy website can still produce a poor AI answer when the retrieval system selects the wrong evidence.
Journal 029
Building for a New Audience
As AI becomes a new audience for the web, websites are beginning another period of adaptation. This is why we're choosing to build AI Readiness in public.
Journal 030
Review: What Six AI Systems Said About Wayli
Six independent AI reviews reached different scores but repeatedly identified the same questions about clarity, audience, trust and evidence.
Journal 027
The Day AI Couldn't See What We Could
While testing Wayli with browser AI, we discovered something unexpected: sometimes AI isn't looking at the same information as you.
Journal 028
The Day Giving 100% Became Possible
We discovered our own assessment could never award a perfect score. The problem wasn't the methodology. It was our implementation.
Journal 026
Why We Didn't Let AI Write Your AI Report
Building an AI Readiness product taught us something unexpected: the most trustworthy AI report might be the one that AI never writes.
Journal 025
We Were Selling the Wrong Thing
The biggest improvement to AI Readiness wasn't a better engine. It was realising what people should not have to pay for.
Journal 024
The Report Improved Because We Listened
The biggest improvement to our latest AI Readiness report wasn't caused by changing the engine. It happened because we acted on what the previous report told us.
Journal 023
The Score Was Never the Goal
We thought we were improving an AI Readiness score. What we were really improving was how clearly we explained ourselves.
Journal undefined
Why We Build in Public
We don't publish because we have all the answers. We publish because we're still looking for them.
Journal undefined
How AI Understands Your Business
A plain English explanation of how AI forms an understanding of a business and how Wayli measures it.
Journal 018
The Product Changed Before the Website Did
Testing Wayli didn't just improve our website. It changed what AI Readiness was becoming.
Journal 019
We Asked AI to Test 100 Businesses
Testing one website taught us about Wayli. Testing one hundred began to teach us about AI.
Journal 020
Businesses May Be Less AI Ready Than They Think
Our first benchmark suggests many businesses may be harder for AI to understand than their owners realise. It's an early observation—not yet a conclusion.
Journal 021
The Pattern We Didn't Expect
We thought we'd find one big problem. Instead, we found lots of small ones. That changed how we think about AI Readiness.
Journal 022
One Hundred Isn't Enough
One hundred businesses gave us our first evidence. It also reminded us how much we still have to learn.
Journal 016
Wayli Doesn't Stop at the First Question.
The first question is rarely the real problem. Wayli exists to understand what people are actually trying to decide.
Journal 017
We Tested Wayli on Wayli
Before asking anyone else to trust our Understanding Engine, we pointed it at ourselves.
Journal 015
We Never Pivoted. We Just Kept Asking Better Questions.
Looking back, Wayli didn't change direction. Each project simply revealed a deeper question than the one before it.
Journal 014
The Report Was Never the Product
We set out to improve a mortgage page and ended up questioning whether Wayli should generate reports at all.
Journal 013
The Engine Already Knew
The report looked incomplete, but the missing understanding was already there.
Journal 012
The Day AI Left the Critical Path
The biggest breakthrough wasn't teaching AI to make better decisions. It was deciding that it shouldn't make them at all.
Journal 011
We Became Our Own First Customer
AI Readiness wasn't built by looking for customers. It started by trying to understand whether AI understood Wayli.
Journal 010
Everything Felt Important Until It Didn't
One of the hardest lessons wasn't deciding what to build. It was deciding what not to build yet.
Journal 009
AI Readiness Started as an Internal Tool
We weren't trying to build another product. We were trying to understand how AI would understand Wayli.
Journal 008
Every Calculator Started Looking the Same
The biggest breakthrough wasn't building another calculator. It was realising they all followed the same pattern.
Journal 007
Retirement Isn't Really About Retirement
Building the Retirement Planner changed the question from 'When can I retire?' to 'When does work become optional?'
Journal 006
The Best Financial Decision Isn't Always About Money
While comparing mortgage overpayments with investing, we discovered that people weren't always trying to maximise wealth. Sometimes they were trying to buy time.
Journal 005
The Student Loan Calculator Taught Us About Tipping Points
Three simple scenarios revealed that the most important number wasn't the repayment. It was the point where the decision changed.
Journal 004
The Software Was Never the Hard Part
I expected to spend most of my time writing code. Instead, I spent it learning how to ask better questions.
Journal 003
We Stopped Asking AI to Write Code
The biggest improvement wasn't better code. It was asking better questions.
Journal 002
A-I Didn't Build Wayli Alone
AI helped me learn faster, but it never replaced the thinking behind the project.
Journal 001
Why Wayli Exists
I thought I was building better calculators. I slowly realised I was trying to solve a different problem.