TEFL RFP · Website & platform · Velocity Labs

Winning an RFP by showing the work, not describing it.

A global TEFL provider invited us to pitch for a website redesign, with a larger platform project behind it. Instead of a document about how we work, we sent two clickable prototypes, built on a brand system I rebuilt from their live site.

My role
Senior Product Designer, workflow lead
Client
Global TEFL provider
Team
Six, from PM to AI engineer
Status
Discovery, design next
Two concepts on laptops: Runway on the left, Departure on the right
25+Agencies pitched to
2Clickable prototypes
1Switch to rebrand
WonChosen as partner

The problem

A global TEFL provider’s RFP for a website and student platform, pitched to 25+ agencies, with no new brand to design from.

What I did

Rebuilt their brand as tokens from the live site, then designed two clickable concepts, one for each kind of student, instead of a proposal document.

The result

Chosen as their partner. We’re in discovery now, and their new brand drops in with one switch.

01 · Context & Problem

An RFP with no brand to work from

The client trains people to teach English abroad. They sent out an RFP for a website redesign, with a bigger project behind it: the student platform. They pitched it to 25+ agencies worldwide.

We had their brief and the competitors they admired, but no new corporate identity. Their rebrand wasn’t ready yet, so anything we designed risked being thrown away the moment it landed.

02 · The Insight

Show them. Don’t tell them.

Most RFP responses look the same: research, process diagrams and a page on how the agency works. The client would be reading 25 of them.

So we flipped it. Instead of describing what we would do, we would show them: two working concepts they could click through on their own laptop or phone, before they had even chosen a partner.

03 · The Breakthrough

A brand rebuilt as tokens

This was the first real test of a design workflow I had built for the studio. With no new CI to work from, I took the client’s live website and tokenised it: the colours, the typography, everything. That became their brand infrastructure, and I built a design system on top of it.

The payoff is that nothing is hard-coded. When the new CI arrives, we swap the tokens and every screen in both concepts updates at once. One switch, not a rebuild.

One source · every screen

Live site

The client’s current website, tokenised as it stands

Source↗
New CI

Their rebrand, ready to drop in

↗
Tokenscolour · type · the rest
Design system

Every component inherits the tokens

Built once↗
Runway

For younger students deciding with their parents

Concept A↗
Departure

For self-sufficient explorers: ask the brand anything

Concept B↗
No new CI? Rebuild the current brand as tokens. When the new CI lands, flip the switch and the whole system follows. Swatches are illustrative.

04 · Exploring Directions

Two concepts, two kinds of student

The client’s students aren’t one audience. Rather than average them into one safe design, we gave each group its own concept, both running on the same tokens.

Concept B, Departure, on a laptop
Departure, for self-sufficient students who like to explore on their own, with an AI touch: ask the brand anything, right from the page.
Concept A, Runway, on a laptop
Runway, for younger students who still lean on their parents, built to guide both through the decision together.

05 · Designing the Pitch

From live site to clickable prototype

01

Tokenise

Live website · brand infrastructure

Captured the current brand straight from the client’s site and turned every colour and type style into tokens.

02

Systemise

Tokens · design system

Built a design system on those tokens, so every component inherits the brand and a rebrand only has to change one layer.

03

Prototype

Two concepts · desktop and mobile

Designed both directions, then shipped them in the lightest code possible, as clickable prototypes the client could open on a laptop or a phone.

04

Present

Six people · one story

Our project manager opened, and each of us took our part: strategy lead, head of design, AI engineer, software developer and me. Everyone was prepared, and the whole pitch pointed one way.

06 · The Outcome

Chosen as their partner

Two things set us apart: speed, and how we presented as one team. The client loved that our proposal came with real visuals they could use, not a write-up of how we work.

The client chose Velocity Labs. They have since shared their new CI, and because the system runs on tokens, bringing it in is a switch, not a redesign.

07 · What’s Next

Discovery, then design

We’re in the discovery phase with the client now. Next comes the design phase: the website first, then the student platform, both on the same token system that won the pitch.

08 · Takeaway

The fastest way to earn trust is to show the work

A token-first workflow let a six-person team turn an RFP into two working prototypes, and turned the client’s rebrand from a risk into a switch.

Contact

Hiring a senior product designer? Let’s talk.

Based in Johannesburg, open to remote roles.