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.

4 min

Written by

It started with a Reddit discussion about mortgages.

Someone was frustrated that they'd paid tens of thousands of pounds but their mortgage balance had barely moved.

The maths wasn't wrong.

The explanation was missing.

What changed

Instead of thinking about interest and principal as numbers, we started thinking about them as understanding.

Rather than saying:

You paid £51,800 in interest.

We asked:

What percentage of today's payment is actually reducing the mortgage?

That simple shift felt far more meaningful.

It answers the question people are really asking:

"Am I actually getting anywhere?"

Why it mattered

That conversation exposed another problem.

Every time Wayli becomes smarter, it generates another insight.

Every insight becomes another card.

Every card makes the page longer.

Eventually the page becomes a report.

We realised the problem wasn't too much interpretation.

It was giving every interpretation equal importance.

What I learned

The answer should always come first.

Everything else should exist because the user becomes curious.

That led to a much bigger idea.

Perhaps Wayli shouldn't generate reports at all.

Perhaps every engine should simply produce:

  • Your Answer
  • Why?
  • What changed?
  • What could change this?
  • See the evidence

The evidence changes.

The questions don't.

That felt like the first glimpse of a universal Wayli output model.

Spark

Inspired by:

  • Reddit discussion