Accountancy practice

The problem

Every enquiry an accountant gets opens with "how much do you charge" and "when's my deadline" — a data problem, not a trust problem. A pub or a joiner needs to feel like people; this practice needs to answer two questions correctly, which the other three concepts don't have to solve at all.

What I did

• Almost no scroll animation on this build — the philosophical decision. Every motion answers a user action: sorting a table, filtering it, drawing a chart on first view. Nothing plays at you, because an accountant's site behaving like a showreel would be the wrong pitch.
• The fee table sorts by service or price and filters by availability, with GSAP's Flip plugin lazy-loaded only on first interaction — it never loads for a visitor who just reads the table.
• The deadline tracker computes real dates from the visitor's own clock, correctly rolling to next year past the date — not a hand-written "due in 9 days" that's still true eight months later.
• The hero's client dashboard is real, working UI rather than a photograph of a handshake, three tabs of tabular data for a fictional client who is, deliberately, the same pub the Broadsheet concept builds for.

What it proves

The same standards as paid work: a performance budget it has to come in under, WCAG 2.2 AA as a floor rather than a finish, and no page that takes six seconds on a phone. Nobody briefed this and nobody signed it off, which is the honest limit of what a concept can show you.