Three tiers of visibility. Yours would be the first.

1. 01Partner work — invisible. Never shown, never named, no exceptions and no time limit. It is not a gap in this document; it is the thing you would be buying.
2. 02Client work — shown with permission. Everything in the next section. Published, live, and open to being checked.
3. 03Our own ventures — shown in full. We own them, so there is nothing we cannot tell you, architecture included. If you want to interrogate how we actually build, start there.

A studio that shows you its partner work would show yours to the next studio.

No house style. That is the point.

Thirty WordPress builds in twelve months, across sectors with nothing visually in common. If you are handing over a design, what matters is that we execute yours — not that we have one of our own.

• Industrial & manufacturing

  Shopfitting · signage · suspension tuning · HVAC

• Professional services

  Attorneys · immigration & visas · logistics

• Health & clinical

  Dentistry · aesthetics · non-profit care

• Retail & e-commerce

  Bridal wear · cosmetics · label printing · water

• Hospitality & venue

  Cocktail bars · lounges · cafés

• Corporate & enterprise

  Insurance web shops · security manufacturing · staff portals

Move a live business off Wix without locking 13,000 customers out of what they had already paid for.

• Reconstructed the entitlement join Wix does not export — the row linking a customer, an order, a product and a downloadable file, which WooCommerce needs and no Wix export is shaped like.
• Mapped every indexed URL across a structure the two platforms do not agree on, then watched rankings through the cutover rather than hoping.
• Rebuilt design and front end on WordPress, with the store operable by the client afterwards.

Customers migrated

13,000

From → to

Wix → WordPress

Scope

Migration · design · SEO · support

Relationship

Ongoing, under SLA

Why it matters to you · Migrations are where rebuilds actually fail, and the failure is silent until a customer cannot open something they bought. If you have won a replatform, this is the risk you are really quoting on.

Full case study: futragency.com/work/miss-angler

Make a specialist building-services engineering firm legible to the people who commission buildings.

• Scroll-driven video and motion carrying the technical story, composited rather than run from JavaScript, and degrading to a readable page where it is unsupported.
• A content model their own team operates — no black-box build, no dependency on us to publish a project.
• Performance and accessibility treated as budgets to build against, not as an audit afterwards.

Sector

Consulting engineers

Founded

1964

Platform

Next.js · Payload CMS

Scope

Identity · design · build · motion

Why it matters to you · If your studio designs motion-led work and needs it engineered without the performance falling over, this is the closest reference point.

Full case study: futragency.com/work/spoormaker

Explain where a wireless mesh network physically sits inside a working mine, and why it holds.

• An interactive 3D model of a mine, navigable in the browser, showing device placement in real context.
• Trade and retail routes modelled as distinct journeys rather than one catalogue with different prices.
• Technical specification presented as pages rather than buried in PDF downloads.

Sector

Industrial infrastructure

Hard part

Interactive 3D in-browser

Routes

Trade · retail · specification

Why it matters to you · The 3D is not decoration — it is the explanation. Where a client sells something genuinely complex, this is what replaces twenty minutes of talking.

Full case study: futragency.com/work/scan-rf

Reposition a financial advisor as a retirement partner, competing on confidence rather than products, inside a compliance regime.

• Positioning and content architecture rebuilt around the decision a client is actually making.
• A custom CRM behind every form on the site, so an enquiry arrives as a record rather than an email.
• A content model that keeps regulated claims reviewable instead of scattered through page copy.

Sector

Financial services

Constraint

Regulated content

Hard part

Custom CRM behind every form

Why it matters to you · Regulated sectors are where most agencies subcontract, because the copy cannot simply be written well — it has to survive review.

Full case study: futragency.com/work/retirement-counselors

Build a brand end to end — name, identity, messaging, store, acquisition, email and automation — from one team.

• Naming and identity through to a working store, without the handoffs that usually lose the positioning.
• Lifecycle email built on what someone did rather than when a campaign was remembered.
• Acquisition running against the same positioning as the site, not a separate brief.

Scope

Name → identity → store → acquisition

Platform

E-commerce

Hard part

One team, no handoffs

Why it matters to you · Useful where you have won something wider than your discipline and would rather not assemble three suppliers to deliver it.

Full case study: futragency.com/work/vita-serena

The two we can show you completely.

Ours, not clients’. Which means every technical decision is open to inspection — useful if you would rather audit the engineering than admire a screenshot.

• Get Yachties

  A two-sided marketplace for yacht crew: matching, verification, and the schema that has to hold both sides honest.

  Our own, so there is nothing we cannot show you. If you want to interrogate how we actually build rather than how it looks, start here.

• GridLoop.ai

  Custom AI that gives executives their time back, built as the demonstration of what web and digital automation can do.

  Where a client is asking for AI and you need someone who will say plainly which parts should not be automated.

Both are labelled as ventures wherever they appear. Neither is presented as client work, here or anywhere else.

Your stack, not ours.

• WordPress & WooCommerce

  The most requested, and the most often built badly. Editor-operable rather than developer-locked.

• Shopify

  Where commerce genuinely fits it. Custom build only where it genuinely does not.

• Webflow

  When your team wants hands on the front end after handover.

• Payload & Next.js

  When the content model is the hard part, or performance is the point.

• Migrations

  Off Wix, Squarespace or a legacy build — without losing rankings, orders or customer access.

What you get when it ends.

The portfolio question nobody asks until it is too late: what happens when this supplier goes away.

1. 01The repository, with its history — not a zip of the final state.
2. 02Every credential, in your name rather than ours.
3. 03Documentation written for whoever maintains it next, on the assumption that it will not be us.
4. 04A CMS your client can operate without calling anybody.
5. 05No futr branding, no credit line, no backlink, nothing in the page source that names us.