For tech & SaaS · Midlands

Your site gets read like your product.

For a product company, the marketing site is read as a build-quality signal. Scroll story, motion and speed say more than the feature list.

Scroll story · the buying signal
01 · the real issue

Buyers judge the product by the page.

Before the trial, before the call, someone opens the marketing site and decides how well-built the product probably is. Three ways that judgment goes.

The judgment is instant
A laggy marketing site reads as a laggy product. Unfair, maybe, but it's the first build-quality signal a buyer gets, and they take it.
One idea per screen
Feature dumps lose. A scroll story that lands one idea at a time sells the thinking as well as the software.
The demo above the fold
Buyers want to see it work, not read about it working. If the product's first appearance is a bullet list, the tab closes.

This page runs on the same rules it's selling: one idea at a time, the concept below doing the demonstrating, and no numbers I can't stand behind.

02 · the site

What good looks like for a product.

This is Cadence, a SaaS concept I built to show the standard. Hover it and it walks through itself.

  • 01One idea per screen

    The story unfolds as you scroll, one claim at a time, each one shown rather than asserted.

  • 02A demo above the fold

    The product tour starts before the pitch does. Buyers who can see it working stop needing to be persuaded.

  • 03Pricing, published

    Honest numbers on the page. "Talk to sales" as the only answer reads as "brace yourself".

  • 04Speed that matches the pitch

    If the site claims fast software, the site had better be fast. Every millisecond spends credibility.

Cadence is a concept, not a real product. Yours gets built on your feature set, your story, your numbers.

CONCEPT · SAAS PRODUCTCadencehover to view it live →
live preview
03 · the other half

The jobs that leak between the tools.

A site starts the conversation. These run in the background of most product companies, and every one is a small build.

1

The demo request, lost in the inbox

Today

Demo requests land in a shared inbox alongside invoices and newsletters. Whoever notices first replies, and the hot ones cool while everyone assumes someone else has it.

What I'd build

Requests routed the moment they arrive: qualified with two or three questions on the form, dropped into the right person's calendar, confirmation out automatically.

Ask about this
2

Copy, paste, CRM

Today

The site form sends an email, and someone retypes it into the CRM later. Later sometimes means never, and the pipeline quietly stops matching reality.

What I'd build

The form writes straight to the CRM with the source attached, so every lead exists once, in the right place, with a record of where it came from.

Ask about this
3

The changelog nobody updates

Today

The product moves weekly; the public changelog says March. Prospects read it as a product that's stalled, which is the opposite of the truth.

What I'd build

A changelog that builds itself from the work: release notes drafted from your merged changes, reviewed by a human, published in a click.

Ask about this
4

Getting a new customer's data in

Today

Every new account shows up as a spreadsheet mess. Your team maps and retypes it by hand, and the customer waits to see any value while onboarding drags. The import is the bottleneck, not the product.

What I'd build

An import step built into your product: AI maps and cleans a customer's messy file into your schema, and a person signs off every mapping before anything commits. Or I run it as the done-for-you migration your customer authorises directly, so a new account is live in days, not another fortnight of retyping.

Ask about this

Every one is a small build that connects to the tools you already run. If you want the numbers for your own setup, I'll build you a proper ROI on the jobs worth doing.

04 · working together

Four steps, no ceremony.

You've shipped software, so you know how this usually goes wrong. Here's the whole process.

Step 01

A quick call

Twenty minutes. I look at your current site and how leads actually move through it, then tell you honestly where the quick win is and where there isn't one.

Step 02

I build the demo

You see a real, clickable version of the site on your product and your story, not a proposal deck about one.

Step 03

We wire it in

It connects to the CRM, the calendar and the tools you already run. Nothing that works gets rebuilt.

Step 04

Looked after for life

The product moves weekly, so the site keeps pace. That's the part other builders hand over and forget.

05 · what it costs

Priced like a line item, not a hire.

Most product companies take the subscription: nothing upfront, one monthly amount, and the marketing site stops competing with the roadmap.

Starter
£149/mo
Nothing upfront · 12-month term

The product site done properly. Scroll story, demo up front, published pricing, hosting, changes and care, bundled.

Start with Starter
Rather pay once? Builds start at £595 with care plans from £49 a month. The full ladder is on the pricing page, and I'll always tell you if the smaller option fits.

The site is the first thing they judge. Make it pass.

Fifteen minutes on the phone and I'll tell you what I'd build, what it costs, and whether it's worth doing at all. If your current site just needs a faster hero, I'll say so.