From a one-page brief to a site and a client dashboard

The client and copywriter were already writing when I joined, with no structure underneath. In that copy I found three pages, not one: a landing page, how it works, and industries. The industries copy held a page per sector, so a healthcare buyer wouldn't scroll past six other sectors to reach patient data.

I told the client; she asked me to recommend the rest. I added pricing and contact pages: a company that hides its prices is hard for a compliance officer to trust.

The seven industry pages and an 'Other industries' page share one template; only the regulations, the failure example and the exposure change. That kept eight pages affordable to build, and easy to compare.

The old site was dense and technical about a subject that already frightens people. The redesign went light: generous whitespace, one idea per section, short lines.

I worked through it section by section with the copywriter; keeping a section short means deciding what it won't say.

The failure examples carry the weight. Each industry shows a two-line exchange: a caller asks if the call is recorded, and the AI ignores it and asks for an account number. The breached regulation sits underneath. A compliance officer sees the risk in one read.

The comparison table is where this broke down. The client wanted brevity everywhere but more detail here, and a dense table works against the site's tone. It took longest, and it's still the heaviest thing on the page.

The client had always hired freelance designers directly. At the wireframe review there were five of us on the call, and she read the greyboxes as finished design while paying for everyone's time. It didn't land.

I took a separate call with her alone and relayed what she wanted to the team; our founder agreed to change course. Wireframes gave way to a written structure for each page, with a few real examples per section: she chose, the copywriter rewrote to fit. From then on she worked one-to-one with me, so I ran the calls, summaries and coordination alongside the design.

She wanted the call-to-action moved on the industries section. I thought her placement pulled attention off it, but my opinion isn't an argument to a paying client.

I ran both layouts through Clarity's predicted heatmaps; mine held attention on the button. That's a model's guess from a static image, not real behaviour, and I said so. It took half an hour and turned a matter of taste into evidence.

The second deliverable showed verification results to Sonosift's own clients. The brief took several calls to pin down; underneath, it was a link-and-password page with status, findings, history and downloads.

I modelled it on trust centres, the pages security and compliance vendors use to publish their own posture, because readers already know the genre:

• Status leads, in plain words. The reader's question is 'are we clear?', so a sentence answers it before any detail, not a score that invites argument about the scale.
• Frameworks separated from local jurisdictions. They're read by different people at different times; a client in four markets scans for their own geography.
• Reports are dated bundles, downloadable whole. Findings go on to auditors and executives, so the unit is the document set, not the screen.
• A monthly archive, not a current state. Audit defence rests on compliance held over time.

Support sits on the page too: the first reaction to a failed check is 'what does this mean for me?', and answering in place beats an email thread.

I prototyped it in Figma Make in about a day, so she could open it from a link and hand it to her own clients.