Selected work
Marketing website rebuild for a B2B services firm
Engagement at a glance
- Business Website
- Professional services
- 2025
- Independent B2B services firm
What happened
Challenge
An outdated single-page site that loaded slowly, ranked poorly and gave prospects no reason to trust the firm — while competitors invested in their web presence. Everything the firm sold sat in one undifferentiated scroll, so there was no page for any individual service to rank for and nothing to send a prospect who had asked about one specific thing. Sales conversations kept starting from zero because the site had done none of the qualifying work beforehand.
Approach
We rebuilt the site as a fast, multi-page marketing platform: structured service pages, a clear inquiry funnel, semantic SEO foundations and a design system the firm can extend without a developer on retainer. Each service became its own page with its own scope, its own questions answered and its own route into the contact form. The design system is a small set of composable sections, so service content can follow a consistent template rather than require a new page design.
Outcome
The firm received dedicated service pages, an enquiry path from each page and a reusable content system. Sales can share the URL for the relevant service rather than explain where to scroll on a single-page site. The delivered structure lets the team extend the service content without redesigning the platform.
Measurement context
This account documents the delivered site structure and enquiry journey. Comparable before-and-after loading measurements, enquiry conversion data and delivery duration are not published. It therefore does not establish a measured performance or conversion uplift.
Why this stack
Next.js and TypeScript were chosen for a reason that had nothing to do with scale: the firm had no developer on retainer, so the deciding factor was whether a marketing person could add a service page without breaking the others. A typed component system makes that a fill-in-the-fields exercise rather than an editing-JSX one. Tailwind kept the design decisions in the markup where they are visible, instead of in a stylesheet nobody would maintain.
What we would do differently
We modelled the content after designing the first two pages rather than before, and paid for it: the third and fourth service pages needed fields the model did not have, so the components were revised once the copy was already in them. On the next build of this shape we would settle the content model first and let the layout follow it, which is the sequence we now use as standard.
Stack
- Next.js
- TypeScript
- Tailwind CSS
Contact
Something similar in flight?
Describe where it currently stands and what worries you about it. You will get a considered reply from an engineer, not an autoresponder.