---
title: "What I do: measurement, marketing, sites"
description: "Most people who get in touch have been asked to do more with a smaller team. I help decide what to hand to software, then I build and run it."
url: https://growthlabs.work/services.md
canonical: https://growthlabs.work/services
publisher: Growth Labs
image: https://growthlabs.work/share/index.png
type: Article
contentHash: c7a494f1fb0ad753e0a9e2856f25c4c088bb6ff2164f76f40a3014e731895c5f
tokens: 758
summaryUrl: https://growthlabs.work/services.md.summary.md
---

<!-- aeo:section start="lede" -->
# What I do

Most people who get in touch have been asked to do more with a smaller team. I help decide what to hand to software, then I build and run it.

<!-- aeo:section end="lede" -->
<!-- aeo:section start="three-places-to-start" -->
## Three places to start

- [Measurement](https://growthlabs.work/services/measurement): Your forms, CRM, analytics and ad accounts traced against each other every day, the differences explained, the gaps I can verify fixed with your approval. Start here if nobody trusts the dashboard.
- [Marketing operations](https://growthlabs.work/services/marketing-operations): One recurring job first - expert content to campaign, for most B2B teams - run by agents with a named reviewer on your side, then the next job.
- [Websites and platforms](https://growthlabs.work/services/websites-and-platforms): New sites and platforms built so agents can run them, or your existing site worked on every week through Site Brain. I work with what you have first and only suggest a rebuild when it's actually worth it.

<!-- aeo:section end="three-places-to-start" -->
<!-- aeo:section start="how-i-work" -->
## How I work

### Diagnose (Two weeks, fixed price)

Two weeks. I read how things actually run - the jobs, the tools, the numbers, who approves what - and write up what I'd hand to agents first, what should stay with people, what it would cost to build and to run, and what I wouldn't do. If the job and the access are already clear we skip this, and I find out what I need during the build.

### Build (One job, fixed price)

One job, with an agreed volume, a named reviewer on your side, and acceptance you can check. I quote a fixed price and I don't go past it without asking first. What you get at the end is the thing running, not a plan for it.

### Operate (Monthly)

I run what I built, month to month. The agents do the routine work, your people keep the decisions, and you get a monthly readout: volume, quality, cycle time, cost. Business-hours coverage, with me as the named person on my side, and the total running cost - my fee plus the tools - stated up front. If you want to take it in-house, you keep the licences and the playbooks, name an owner, and it keeps running.

<!-- aeo:section end="how-i-work" -->
<!-- aeo:section start="how-it-runs" -->
## How it runs

Under the three places to start there's one system, and these are the five things about it I'd want to know if I were handing someone my marketing.

- **Several models, picked per job.** Claude, Codex, Gemini and other providers, picked by what the job needs. I choose the model for each job and can change provider where the workflow allows it. We agree the budget and the limits up front, and I'll tell you which provider sees your data.
- **A person at every gate.** Nothing publishes, sends, spends or changes a site without a named approver's yes.
- **Everything on record.** Every proposal, approval and change, with what it replaced, so you can see who did what and put it back.
- **It keeps the record of your account.** What was tried, what worked, who approves what, so the operation survives staff changes.
- **You can see what it costs.** An agreed budget per job and per month, with a cap, before it runs.

It's the same system I run my own sites with.
<!-- aeo:section end="how-it-runs" -->