I don't just advise. I build and ship.

Websites, product surfaces, and the systems running behind them. Designed and built by one person, shipped in weeks, and handed over running so your team owns it after I leave.

Book a callSee the outcomes
What changed

Six systems, before and after.

Every number below is either measured against a live system or taken from a verified record, with the date and the source on the case study.

Mack, for CMS Surveyors

Home energy surveys · UK

An AI operator went live inside the business in May, and by August the operations director was building his own automations on it without me.

emails triaged since going live in May
10,715
agent sessions in the last seven days
3,409
standing automations the team now runs
40

BeforeEleven people, ten mailboxes, and a CRM that only told you anything if somebody remembered to open it. Work moved by whoever happened to notice it. The operations director spent his day being the routing layer between an inbox, a calendar and a job board, which is not what a co-founder is for.

Read the case study

BookerBot

Multi-tenant voice and messaging platform · UK

One system answers the phone, the texts and the WhatsApp for five businesses, and books the job while the customer is still in the conversation.

median from an inbound message to the agent’s reply
8 sec
from a web form submission to a live outbound conversation
~2 min
client workspaces on one codebase
5

BeforeEnquiries arrived from ad campaigns, website forms and the phone, landed in an inbox or a voicemail, and waited for somebody to have a spare half hour. Most of the ringing round happened the next working day, by which point the faster company had the job.

Read the case study

Thingiverse Labs

The world’s largest 3D printing community

A platform too big to move fast got a community surface that ships in days, built by one person on a subdomain.

unique visitors in its first 15 measured weeks
49,858
of them to one partner challenge, run with Raspberry Pi
16,712
changes required to the legacy platform
Zero

BeforeThingiverse has millions of makers and a codebase old enough that every good community idea, an events map, a design challenge, a calculator, queued behind platform work measured in quarters. The community kept asking. The roadmap kept not moving.

Read the case study

SUPA

Grocery delivery · South Africa

The marketing team generates its own on-brand content, because the brand guidelines are compiled into every prompt.

brand-locked images generated for SUPA
693
content pieces drafted for review
527
approved, scheduled or published by the brand team
107

BeforeGetting social content made meant briefing designers and waiting on revision rounds, and generic AI image tools produced content that looked like AI, not like SUPA. Volume and brand consistency pulled in opposite directions.

Read the case study

Do Gooder

Charity effectiveness research · UK

A question about where donations actually go became a public database that grades UK charities on the accounts they file, not the adverts they run.

UK charities graded on their filed accounts
14
head-to-head comparisons, every pair of the fourteen
91
live flag rules, each with its threshold published
6

BeforeChoosing between two charities meant reading two sets of annual accounts. They are public, they are long, and they are written for a regulator rather than for a donor. The figures that reach the public get chosen by whoever is doing the fundraising.

Read the case study

EPC Guide

Landlord compliance · England and Wales

A 27.6 million record public register became a postcode box that tells one landlord which measure moves their house to band C and what it costs.

homes resolved out of 27.6M public certificates
19.7M
organic clicks in 89 days, from 170,180 impressions
2,345
live pages, 318 of them one per local authority
518

BeforeA landlord renting out a home below band C has a deadline, a £10,000 spend cap and no way to find out what their own property needs. The certificate already lists the measures. It is buried at the bottom of a page nobody scrolls, in codes, with no total. Every other answer online is written by whoever sells the measure being recommended.

Read the case study
Business impact

What these systems have actually done.

Four businesses, four live systems, every figure measured against the production database that produced it. Each one links to the case study it came from, with the date, the source and the caveat.

Manual work absorbed

650hours

Roughly 16 weeks of full-time work that nobody had to do, across four businesses.

How that is calculated

  • 10,715emails triaged× 2 min
  • 527content pieces drafted× 20 min
  • 693brand-locked images produced× 10 min
  • 67voice calls handled× 5 min

Counts are measured. The per-unit minutes are my estimate of the manual equivalent, deliberately conservative, and shown so you can substitute your own. The total is floored, not rounded.

10,715emails triaged without anyone opening an inboxMack
49,858people reached in fifteen weeksThingiverse Labs
1,220images and content pieces produced on brandSUPA
8 secmedian reply to an inbound enquiry, day or nightBookerBot
40standing automations running without supervisionMack
5businesses served by one system, each isolatedBookerBot

Counts measured against the live production databases behind each system: Mack and SUPA on 11 Aug 2026, BookerBot on 12 Aug 2026, Thingiverse Labs via the Vercel Analytics API on 4 Aug 2026. The 1,220 figure is 693 images plus 527 drafted pieces, of which 107 were approved by a human.

Ninety days apart

Today

47 tools. None of them talk to each other.

fig. 1 · today
fig. 2 · ninety days in · ● live

Ninety days in

One pipeline the work moves through, and you can see where it is.

Same team. Different structure.

  • Six people doing what a system handles in twenty minutes.

    Those six people doing the work you actually hired them for.

  • The redesign has been in review for three months.

    Something live in ten working days. Then the next thing.

  • The website was built by someone who left, and nobody will touch it.

    A stack your own team can change on a Tuesday without asking permission.

  • Your team could build this. They have no time, no mandate, and nobody has ever shown them how.

    They’ve shipped it once with me, and they ship the next one without me.

The offer

One obvious first step, then three ways to carry on.

The first step has a fixed price and it is on this page. Everything after it is priced per piece of work rather than off a rate card, because a landing page and an operations rebuild are not the same size of job and pretending otherwise helps nobody. You get the number before anything starts, and it does not move afterwards.

01Start here

The audit

£849Two weeks · fixed fee

If I cannot find something worth more than the fee, you do not pay it, and you keep everything I built. If you carry on into a build, the fee comes off it in full within 60 days.

Book a call

Start here.

I go through what you actually have. The site, the funnel, the tools, the path a piece of work takes through the business. You get a map of your own operation with costs on it, ranked by what is worth fixing first, and one of those fixes already built and running by the end of it. About four hours of your team’s time. No discovery call theatre.

  • A map of what you actually have
  • Costed, ranked roadmap
  • One fix built and live
  • Findings you can act on without me
022–6 weeks · fixed fee

Design and build

The part your customers actually see.

Marketing sites, landing pages, product surfaces. Designed properly and built to move, not dropped into a template. I build on whatever your team can still maintain once I have gone, from the CMS you already run through to a custom front end, and I will tell you plainly which of those your situation calls for rather than the one that suits me.

Priced on how many unique templates there are, and whether the content comes with it.

Design and build · A stack your team can run · Analytics and tracking wired in · Documented handover

034–8 weeks · fixed fee

Systems and automation

I build it. You own it.

A custom system for one specific expensive problem. Pipelines, integrations, internal tools, agents where they genuinely earn the complexity and plain software where they do not. Shipped to production, documented, and handed over with your team trained to run and change it. No lock-in, no seat licence, no dependency on me.

Priced on how many systems have to talk to each other, and how tangled the data is.

Production system · Full documentation · Team training · 30 days of support

04Two to three days a week

Embedded

Not a fractional advisor. A builder on your team.

I embed with your engineering, design and ops people and ship. New work, hardening what is already running, and pulling your team up to the point where they build the next one themselves. I will sit in the leadership meeting if it makes the work go faster. I will not produce a board deck instead of the work.

Priced by the day. The only variable is how many days a week you want.

Shipped work every month · Your team levelled up · Existing builds maintained · Cancel any month

How this actually goes

No discovery call theatre.

  1. 01
    Day 1

    I go through what you actually have

    Not a workshop. I read the site, the funnel and the analytics, and I sit with the people doing the job and follow the path a piece of work really takes through your business, including the bits nobody has written down.

  2. 02
    Days 2–5

    The map, with costs on it

    What is broken, what it is costing you, and what nobody has noticed. Every recurring task, how long it really takes, how often. Ranked by what is worth fixing first. This is usually the uncomfortable part.

  3. 03
    Days 6–10

    One thing is built and running

    Not a prototype and not a slide about a prototype. Something in production, doing work, that stays yours whether or not you carry on with me.

  4. 04
    Weeks 2–8

    The build, if you want it

    Fixed fee, fixed scope, shipped in weeks. You see it working in your environment as it goes, not at a reveal at the end.

  5. 05
    Handover

    Your team runs it without me

    Documentation, training, and the code in your repositories. The measure of a good engagement is that you stop needing me and the thing keeps running.

Things I’ve built

Systems, not slide decks.

The client work is above, with the numbers. These are the rest: my own products and the system that maintains them. Every one is running right now, every picture is the real screen.

All work and case studies
In their words
“We were paying for leads and then losing them to our own admin. Now every enquiry gets a reply in a couple of minutes, day or night, and the calls we make are with people who already expect to hear from us.”
Director, CMS Surveyors
Rees Calder
Who you get

Rees Calder.

Fifteen years in marketing and product, agency and in-house, up to CMO. Then I got tired of writing recommendations other people never built, and taught myself to build. Now I run a business on software I wrote, and I install the same thing inside other people’s companies. One person. No account manager between you and the work.

Based
Cape Town. Remote, any timezone.
Works with
Founders and heads of ops at SMBs
Not a
CS graduate. Self-taught, in production.
Leaves behind
Running systems your team owns
The route hereFull CV →
  • Marketing Manager · iMakr2012–15
  • Head of Marketing · MyMiniFactory2015–17
  • Strategy & Growth Manager · the tree2017–20
  • Strategy & Growth Lead · Nucco (UNIT9)2020–21
  • Business Development & Strategy Director · Avantgarde2021–24
  • Founder · Levity2024–now
  • Head of Product & Partnerships · MyMiniFactory2025
  • Chief Marketing Officer · Thingiverse2026
Brands along the way

Jaguar Land RoverKiaNikeRaspberry PiJust EatEIT FoodThingiverse

Before you book

Five reasons to not book the call.

  • You want a strategy deck, a maturity model, or a workshop. I don’t sell those and I’d be bad at it.
  • You want the work announced rather than working. If the goal is a press release or an AI story, hire an agency.
  • You want to fire people and need a consultant to hold the pen. I take work off teams, not teams off payroll.
  • Nobody senior can make a decision inside two weeks. Fixed-fee work dies in approval queues.
  • You need someone in a specific office five days a week. I’m in Cape Town, I work remote, I travel when it matters.
One next step

Thirty minutes. Bring the thing that annoys you most.

A site that is not converting, a build nobody will touch, a process eating your week. You leave the call knowing whether it is fixable, roughly what it would take, and whether I’m the right person for it. If I’m not, I’ll say so on the call.

Book a call

Not ready to book? rees.calder@levityleads.com reaches me directly, and I answer them myself.