Delivery model
How we work
Five stages, a client portal you can open at any time, and the same pod on your account from kickoff to retainer.
- Home
- How we work
Delivery model
You should be able to see
the state of the work
without asking.
Most agency friction is informational: what was agreed, what was approved, what is late and why. We solve it by writing things down in one place that you can open at any time, and by keeping the same people on your account rather than a rota.
Five stages
From first call
to running programme.
Stage 01
Discovery
Structured asynchronous workshops in Miro and Loom, plus one or two live sessions. The output is a written brief and a set of success metrics, signed off in the portal before anything is designed.
Stage 02
Design
Figma with comment-based review. Two rounds are included in fixed-scope work, and the rounds are defined so nobody has to argue about what counts as a round.
Stage 03
Build
Continuously updated staging URLs. Every approval is logged against the thing it approved, so “we never signed that off” is a question with an answer.
Stage 04
Launch
A go-live checklist covering analytics, SEO, accessibility, security and legal pages. We do not launch on a Friday.
Stage 05
Grow and operate
Retainer work with live dashboards and a short monthly narrative written by a person. The dashboard says what happened; the narrative says what it means.
Qualified leads
184+31%
Cost per lead
£41−22%
JanJunDec
- Lead qualifier agent 412 handled
- Awaiting your approval 3 items
- Next release Thu 09:00
The client portal
Scope, timeline, approvals, invoices and performance — in one place.
The portal is not a status page we update when we remember. It is where the work happens: approvals are given in it, invoices are raised from it, and the dashboards read from live data.
- Live scope, so “is that in scope?” has an answer
- Timeline with dependencies, updated as things move
- Approvals logged against the exact artefact approved
- Invoices, with what they cover
- Performance dashboards reading from live data
- Agent review queues, where agents are running
It is also a fair sample of the kind of thing we build for clients.
Communication
A cadence you can
plan around.
| Rhythm | What happens |
|---|---|
| Weekly | A written update. What moved, what is blocked, what needs you. |
| Fortnightly | A call, with an agenda circulated the day before. |
| Always on | A shared Slack Connect or Teams channel with your pod in it. |
| Contractual | Response-time commitments written into the agreement, not implied by tone. |
| Quarterly | A retainer review against the success metrics agreed at kickoff. |
Team structure
Cross-functional pods,
not a resourcing pool.
| Role | What they own |
|---|---|
| Strategist / account lead | Owns the outcome and the relationship. One person, not a rota. |
| Designer | Figma, design system, and the RTL mirror when the build is bilingual. |
| Developers | One or two, depending on scope. The people who wrote it are the people who fix it. |
| Marketer | Channel execution, analytics and the monthly narrative. |
| AI engineer | Agent build, evaluation sets, guardrails and the review queue. |
Pods are assigned to a portfolio of clients and stay put. Specialist guilds — SEO, paid media, AI engineering, front-end — run across both offices so the pod can pull in depth without you meeting a stranger.
Coverage
London and Dubai,
one working day.
Headquarters
London
- HoursMon–Fri, 08:00–18:00 GMT/BST
- CoversUK and Europe
- CoversUK and Europe
- Emailhello@1ree.com
GCC office
Dubai
- HoursMon–Fri, 09:00–18:00 GST
- CoversUAE, Saudi Arabia, Qatar, Bahrain, Oman, Kuwait
- CoversThe GCC
- Emaildubai@1ree.com
A single working day, 06:00–18:00 UK time
Dubai 09:00–18:00 GST
London 08:00–18:00 UK
06:0009:0012:0015:0018:00 UK
Dubai pod — opens the day
London pod — closes it
Seven hours of overlap for handover and escalations
In UK winter the Dubai day starts an hour earlier again, at 05:00 GMT.
Next step
Tell us what you are trying to move.
Thirty minutes, no deck. We will tell you what we would do first, what it costs, and whether we are the right people for it.