Railway tracks branching beneath overhead wires

The fastest part of a website project is rarely the bit holding it up

The prototype was ready by lunch. The decision took a fortnight.

Imagine a software company redesigning the product section of its website. The agency has mocked up a page with a “Book a demo” button. Sales likes it. The product team wants buyers to try the software first. Both routes look fine in the design, which is partly how the question makes it through sign-off. It comes back when a developer asks where the button should go.

By then, there are six pages with the same button.

A better first review

In a traditional agency process, strategy, design and development tend to have their own milestones. That can give a complicated project some order. It can also mean that a developer sees a decision for the first time when everyone else thinks it’s settled. The client gets a change request for a conversation they could have had three weeks earlier.

For the software company, I’d get the designer, developer and the person responsible for demo enquiries to look at one working page. Use real copy and wire up the button. If the answer is “book a demo”, follow the route far enough to see who picks up the enquiry. If the company wants people to try the product, find out what a new user can actually do in the first five minutes. Both conversations are easier when you can click the thing you’re discussing.

Bring in the person who’ll update the site, too. Give them a second product to add. The hero might look immaculate until they paste in the one product name that runs to three lines. Or they might ask where to put the integration guide because the template gives every product a video slot and only two products have videos. That’s a much better time to find out.

Where the new tools earn their keep

Shared components make it easier to put that first page together and change it while there’s still only one of it. An AI tool can help generate awkward test content, such as long labels or a set of product descriptions of wildly different lengths. You can see what breaks before a real customer or editor does. The decision about what deserves a place on the page still belongs to the people who understand the product.

Promethean Research’s 2026 digital agency benchmark found that about a third of surveyed agencies had implemented AI across their businesses. That’s a measure of adoption. For a client buying a website, an agency’s use of AI only tells you so much about when the work will be ready. Ask when you’ll see your own content in a working page and who’ll be there to make a decision about it. Promethean Research’s 2026 agency benchmark

There’s still a place for formal review. If a product claim needs legal approval, give legal the actual words early enough to do something about them. Test keyboard navigation on the working page and check it again before launch. There’s little value in saving a day on build if the same problem has to be corrected across six templates.

What to ask in the pitch

Pick a page where you know there’ll be a disagreement. Ask the agency what they’d put in front of you first, who they’d invite to the review and what they’d expect you to decide. A sensible answer should tell you what you need to bring, too. The real copy. Someone from sales who knows where the enquiries go. A content editor with half an hour to try the page.

If you’re planning a rebuild with Studio Gallant, bring us the page your team keeps getting stuck on. We can start there. Digital design at Studio Gallant

Photo by iridial on Unsplash.