futr

White-label delivery

White-label digital delivery for agencies

You hold the relationship. We supply the team behind it.

Johannesburg → worldwide

The proposition

You design it. We build it. Your client never meets us.

futr is the delivery team behind design studios, marketing agencies and IT companies who have won work they cannot staff — or cannot build. We take the brief, or the finished design, and engineer it on the platform the project actually needs.

Everything arrives unbranded, under your name. The client relationship stays yours, the margin stays yours, and the terms that protect both are agreed in writing before the first line of work.

  • 520+Brands
  • 452+Projects
  • 2016Trading since

The commercial situation

The work arrives before the team does.

Every growing agency meets the same week. A client asks for something you can sell but cannot build, or three projects land in the month you were already full. Hiring is a twelve-month commitment against a six-week problem. Turning it down hands the account to whoever says yes.

Without a delivery partner

Turn the work down and watch the account move

Hire permanently against temporary demand

Risk it with a freelancer you cannot cover for

Introduce your client to a full-service supplier

Absorb the overhead into your margin

With futr

Keep the account and the relationship

Add capability for the length of the project

One named owner, senior throughout

Your client never meets us

You set the margin

Who this is for

Three kinds of partner. One arrangement.

  • Design and branding studios

    You create the strategy, the identity and the visual direction. We translate it into websites, commerce, portals and interactive work — engineered on the platform you choose, in your repository where you have one, and handed back for you to present as your studio’s work.

    Typical trigger: a design that needs engineering the studio does not employ.

  • Marketing, communications and social agencies

    You run the campaigns, the content and the accounts. We build and hold the platforms underneath them — sites, landing pages, content hubs, automation and the technical infrastructure a campaign quietly depends on.

    Typical trigger: a campaign underperforming for reasons that belong to the site.

  • IT companies and managed service providers

    You already hold the client and the technical trust. What you may not hold is a brand, UX and web team. We become that capability under your name, so “we handle that too” stops being a stretch.

    Typical trigger: a managed-services client asking for a website.

Integrated agencies with their own digital teams use us differently — for specialist capability, overflow during a heavy quarter, or technical rescue when something has gone wrong.

Engagement shapes

Four ways to work together.

  • Design to build

    You supply approved designs and specifications. We engineer them faithfully, on the agreed platform, in your tools and repository where that suits you. The most common arrangement, and the one studios return for.

  • Full digital build

    We handle UX, interface design and development under your name. You keep the client relationship and the creative or strategic lead. Useful where you have won something outside your normal discipline.

  • Care and support

    Website management, maintenance, monitoring, updates, security and the support queue, delivered behind you. The unglamorous retained work that stops a client drifting to whoever calls them next.

  • Specialist drop-in

    One defined capability placed into your existing team: technical architecture, automation, CRM and third-party integrations, commerce functionality, migrations, motion-led or browser-based 3D work, SEO and migration protection, performance and accessibility, technical rescue, custom portals, or AI-enabled journeys.

We can own a complete build or fill one precise gap. Both are normal.

Capability

What you can hand over.

  • Websites and digital platforms

    Bespoke design and engineering where the site has to carry a serious business. Content architecture, CMS, responsive implementation, technical SEO, accessibility and performance engineering.

  • Ecommerce

    Retail and trade commerce for premium brands — gated wholesale pricing, quote flows, specifier journeys, stock and fulfilment connections. Not just a cart.

  • Campaign and interactive experiences

    Landing platforms, content hubs, motion-led storytelling, browser-based 3D and interaction where it explains something genuinely complex.

  • Portals and automation

    Customer, trade and staff portals. Website automation wiring the site into the CRM, payments, bookings, stock, email and reporting, so it captures and follows up without anyone touching it.

  • Migrations and technical rescue

    Moves off Wix, Squarespace or a legacy build, treated as data, customer-access and search-ranking projects rather than visual rebuilds. Recovery of work another supplier left unmaintainable.

  • Ongoing management and support

    Hosting coordination, monitoring, maintenance, security updates, support, analytics and reporting, optimisation backlogs, lifecycle email and retained technical capacity.

Hosting, maintenance, paid media, SEO, email and ongoing support are included only where they are explicitly scoped.

Platform

Your stack, not ours.

We have no platform to sell you. The right one is whichever your client’s team can operate and you can support after we step back — decided against the content model, the integrations, who maintains it and what you want to carry.

WordPress & WooCommerce

Editor-operable sites and commerce without developer lock-in. The most requested, and the most often built badly.

Shopify

Where the established commerce ecosystem genuinely fits the requirement.

Webflow

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

Payload CMS & Next.js

Custom content structures, heavy integration, high performance, technically ambitious work.

Custom platforms

Where the requirement stopped being a website some time ago.

Migrations

Off Wix, Squarespace or legacy builds — treated as data, access and ranking projects.

The terms

What protects your relationship, agreed before the first line of work.

Not negotiated after something has gone wrong. These are in writing at the start of every partner engagement.

  1. 01Permanent non-solicitation. We do not approach your client during the engagement or after it. Not for twelve months — at all.
  2. 02No futr branding. No logo, no credit line, no footer link, no backlink, nothing in the page source that names us.
  3. 03No unauthorised client contact. We do not contact or meet your client unless you put us in the room. If you do, we follow the role and language you set.
  4. 04The relationship stays yours. You remain the commercial and strategic lead, and it is never treated as shared.
  5. 05You control the margin. We quote you at delivery level. What you charge your client is your business, and we neither need nor want to see it.
  6. 06Your tools and cadence. Where practical we work in your project board, your channels, your repository, your naming conventions and your reporting rhythm.
  7. 07Handover without hostages. Repository and history, credentials in the right party’s name, documentation, a maintainable implementation, CMS access and training.
  8. 08Confidential portfolio treatment. White-label work is never named, published or shown as ours. Partner references only ever with that partner’s permission.

Formal NDA availability, IP transfer, warranty period and data-processing obligations are covered in the partner agreement rather than asserted here.

How delivery runs

Six phases, weekly evidence, one named owner.

01Understand

Commercial discovery, constraints, stakeholders, success measures, decision criteria

02Define

User journeys, functional scope, technical approach, dependencies, delivery plan

03Design

Interface system, key pages, prototypes, interaction and motion specifications

04Engineer

Working builds, CMS, integrations, analytics, staging

05Prove

Device and browser QA, Core Web Vitals, WCAG 2.2 AA on core journeys, security review, launch-readiness gate

06Launch & evolve

Deployment, monitoring, training, handover, prioritised improvement backlog

On design-to-build engagements, phase 03 becomes a design review and technical validation of your work rather than a design phase — checking that what you have drawn can be built to standard, and telling you where it cannot, before anyone commits.

One named senior person owns the outcome. Progress is shown as working artefacts, never a percentage, with formal gates at strategy, design, build completion and launch readiness. Change is classified — clarification, correction, scope trade or scope addition — and additions carry an impact statement before any work starts.

Proof

Most of our best work has someone else’s name on it.

That is not evasion — it is the arrangement working. There are three levels of visibility here, and yours would be the first.

  1. 01Partner work — invisible. Never shown, never named, no expiry. It is not a gap in this document; it is the thing you would be buying.
  2. 02Direct client work — shown with permission. Everything that follows. Published, live, and open to being checked.
  3. 03Our own ventures — open to inspection. We own them, so there is nothing we cannot tell you, architecture included.

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

Digital products · direct client, published with permission

Off Wix without locking anyone out.

A live digital-product business had outgrown Wix and could not leave. Thirteen thousand customers held orders and downloads they had already paid for, and nothing in a Wix export is shaped like the record WooCommerce needs in order to honour them.

We reconstructed the entitlement join Wix does not export — customer, order, product, file — migrated to WordPress and WooCommerce, and mapped every indexed URL across two platforms that do not agree on structure. Orders arriving mid-migration were reconciled: a live shop is not a copy, it is a copy and then a reconciliation.

Customers migrated
13,000
From → to
Wix → WordPress
Scope
Migration · design · SEO · support
Relationship
Ongoing, under SLA
Off Wix without locking anyone out.

Migrations are where rebuilds actually fail, and the failure is silent until a customer cannot open something they bought.

Three months after migration: 14.7K clicks · 68.3K impressions · 21.6% CTR · position 3.9. No before-and-after is claimed — the previous store had no Search Console, so no baseline exists. The performance is strong; the improvement is unprovable.

Consulting engineers, in practice since 1964 · direct client

Sixty years of engineering, made legible.

A specialist building-services engineering firm whose value took twenty minutes to explain out loud. The people who commission buildings were deciding long before that conversation happened.

Identity, design, development and motion as one engagement, on Next.js and Payload CMS. Scroll-driven storytelling with video composited for reliability rather than rendered live. The content model is operated by their own team — no black-box build, and performance and accessibility were constraints to build against rather than an audit afterwards.

In practice since
1964
Platform
Next.js · Payload CMS
Routes
7
Accessibility
WCAG 2.2 AA on core journeys
Sixty years of engineering, made legible.

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

Range

Range, briefly.

  • SCAN RF Projects — industrial, wireless infrastructure

    An interactive browser-based 3D model of a working mine, showing where a wireless mesh network physically sits and why it holds. Trade and retail modelled as distinct journeys, and technical specification presented as pages rather than buried in PDFs. The 3D is not decoration — it is the explanation.

  • Retirement Counselors — regulated financial services

    Repositioned from financial advisor to retirement partner, competing on confidence rather than products, inside a compliance regime. A custom CRM behind every form on the site, so an enquiry arrives as a structured record rather than an email.

  • Vita Serena — wellness, direct to consumer

    Built end to end: naming, identity, messaging, store, acquisition, lifecycle email and automation. One team, no handoffs — which is where positioning usually gets lost.

  • Kahindo — New York luxury fashion

    A decade-long relationship that began with press introductions at a fashion show in Johannesburg. The client has been featured in Vogue and WWD.

  • M/Y La Pausa — prototype, yacht charter

    A charter site for a 26-metre Ferretti Custom Line: full-bleed photography, serif display with a gold accent, a specification strip doing the selling, and staggered scroll reveals built in CSS rather than a JavaScript animation loop. Our own prototype, not client work — and deliberately unlike anything else here.

    Light, serif, Mediterranean. If you want evidence there is no house style, this is it.

Ours rather than clients’, and open to technical inspection because we own them: Get Yachties, a two-sided marketplace for yacht crew with matching, verification and a schema that holds both sides honest; GridLoop.ai, a custom AI venture; and the La Pausa charter prototype above. All are labelled as ventures or prototypes wherever they appear. None is presented as client work.

Handover

Handed over so completely you could never call us again.

That is the point. Partners come back because the work holds, not because they are locked in.

  1. 01The repository, with its history — not a zip of the final state.
  2. 02Every credential, held in the right party’s name.
  3. 03Technical documentation written for whoever maintains it next, on the assumption that it will not be us.
  4. 04A maintainable implementation, on a platform your client’s team can operate.
  5. 05CMS access and training where applicable.
  6. 06Enough information for another competent team to take the project over.
  7. 07No futr branding, no credit line, no backlink, nothing in the page source that names us.

Commercials

Quoted to you. Never to your client.

  • Per-project delivery

    Each project is scoped and quoted against the actual requirement. There is no universal rate card, because superficially similar projects involve materially different work — the same page count can be a fortnight or a quarter.

  • Retained capacity

    Monthly technical availability where you need reliable capacity rather than one defined deliverable. Useful when you are pitching work you have not won, servicing several accounts, or want technical cover you can promise.

  • You control the margin

    We quote you at delivery level. You set the end-client proposal, the fee and the markup. We do not need to see it.

  • Controlled change

    Out-of-scope work is never silently absorbed or silently invoiced. It receives an impact statement covering cost, timeline and dependencies, and is approved before it starts.

Most partnerships begin with one contained project rather than a framework agreement — typically £1,500 to £3,500 depending on the brief, the designs supplied, functionality, integrations and dependencies. An indicative entry range for one defined engagement, not a package.

Not included unless scoped: hosting and ongoing maintenance · platform and software licences · content creation · major design changes after approval · open-ended revisions · unspecified integrations · new functionality introduced after scope approval · third-party service costs · data migration not in the original brief.

Next

Bring something you have won — or keep turning down.

Send one live brief. We will tell you what we would do and what we would not — a concise recommendation covering platform, scope, delivery shape, dependencies and commercial approach.

Book thirty minutes →

Send a brief — info@futragency.com · WhatsApp +27 71 604 3335 · the full white-label terms

Four ways in

However you prefer.

Marine and yacht enquiries go straight to a named senior contact, and nothing is published without permission.