Portfolio

Builds you can open, not screenshots you have to trust.

Five brand sites and one web app, built end to end. Every card below opens the running demo: the brands are fictional, the interfaces are not.

See the builds Discuss your own

5 brand sites · 1 web app · sample content only

The builds

Five interfaces, five different jobs.

Filter by what you need: a brand site that has to sell, or an application with a workflow behind it.

fizz.demo

Brand siteDemo build

Fizz & Co.

A soda brand that sells flavour, not health claims.

A direct-to-consumer landing page: full-bleed product hero, a spec marquee, four flavour sections with their own personality, a twelve-can box builder and an FAQ that answers the awkward questions.

Colour-blocked flavour sections, each with its own type and tone
Working crate builder with quantity steppers and a live total
Reviews and FAQ written in the brand voice, not template copy

Landing pageProduct configuratorArt direction

Open the demo

pearl.demo

Brand siteDemo build

Pearl & Co.

The same commerce template, re-skinned for bubble tea.

A second brand on the Fizz template: new palette, type and photography, the same prepare-and-build structure. It is the honest test of whether a template survives a different product.

One template, a second brand system: colour, type and photography swapped
Six-cup tray builder and subscription copy
Same components, different voice — no layout rewrite

Landing pageBrand systemProduct configurator

Open the demo

casa-bella.demo

Brand siteDemo build

Casa Bella

A London estate agency that reads like a magazine, not a portal.

Property search, listing cards with measured detail, six neighbourhood guides, an agent directory and a journal. The structure a real agency site needs before it can look calm.

Search with neighbourhood, property type, bedrooms and price filters
Six area guides written as content, not as SEO filler
Journal, valuation flow and saved-homes states

Property searchContent systemLead capture

Open the demo

petnest.demo

Brand siteDemo build

PetNest

Pet care, a shop and a booking flow in one place.

Services, products, vets, reviews and an appointment flow on one page set. Every section ends in the same next step, which is what most local-business sites get wrong.

Service and product catalogues with consistent card anatomy
Vet profiles, reviews and a booking CTA in every section
Booking and newsletter forms with real validation states

Landing pageCatalogueBooking

Open the demo

gumstory.demo

Web appDemo build

GumStory

Paste a Gumroad link, get a first-person story you can publish.

A web app rather than a landing page: it fetches the product, drafts an 800–1,400 word memoir-style article, checks it against Medium policy, plans a 30–60 day calendar, then publishes and syndicates to X and Threads through Buffer.

Link-to-draft workflow with a compliance gate before publish
Editor with rewrite assistance and a day-by-day content calendar
Canonical public page with reading time and open-graph tags

AI workflowEditorPublishing and syndication

Open the demo

runway.demo

Brand siteDemo build

Runway

Six looks, styled head to toe — tap a pin to see the piece.

A shop-the-look storefront: full-length photography, six outfits, and a pin on each piece. Isolating a look opens its tray with sizes, a single add-to-bag and the full outfit at a 10% bundle price. Checkout is deliberately left out — the bag is a shortlist.

Hotspots pinned to the photograph, one per piece
Per-look tray with sizes, add-all bundle pricing and a running bag
A shortlist that downloads instead of collecting payment

LookbookShop the lookCart interactions

Open the demo

What these are: demonstration builds with fictional brands and sample content, published so you can judge the interface rather than a claim about it. They are not client work, and no metric or testimonial on this page is presented as a measured result.

How they are built

The same discipline on a product page and on a web app.

A marketing site and an application are different problems; the constraints are the same — readable content, honest states, and no dependency on a page builder.

One brand system per build

Palette, type and photography are chosen for the product, not reused from this site. Fizz and Pearl share a template precisely so you can see what changes and what does not.

Built to be edited

Content sits in data files, sections are components, and nothing depends on a page builder. Changing a headline or a product does not mean rebuilding the page.

Screenshots from the running build

The images on this page are captured from the deployed sites with a script in the repo, so they cannot drift from what the link opens.

Next step

Your product could be the next build on this page.

We scope the smallest version that answers a real question — then show it running before you commit.

Book a Discovery Call See the live demos

No obligationFixed scope, fixed feeApproval stays human

See how engagements run