Position
I work out what the company actually does better than the alternatives, in language a buyer would recognise. Positioning that cannot survive a sales call is not positioning.
Brand development is the work of making what a company says match what it actually does — positioning, the identity system that expresses it, and the campaigns that carry it to a market.
Positioning fails in one of two ways. Either it was written in a room and never tested against a buyer, or the business moved and the words did not. I rebuild the position from what the company actually does now, then build the system that expresses it — and hand you the keys rather than renting you a dependency.
I work out what the company actually does better than the alternatives, in language a buyer would recognise. Positioning that cannot survive a sales call is not positioning.
Identity, type, colour, layout, and the rules for using them — built as a system your team can run, not a set of files they have to ask permission to use.
Website and content architecture, structured so each page competes for something specific rather than every page competing for everything.
Campaign build, then a real handoff — documentation, the reasoning behind the rules, and the training to run it. I would rather leave than be needed forever.
Positioning is the argument — what you do, for whom, and why it beats the alternatives. Branding is how that argument is expressed: name, identity, voice, and the system that keeps it consistent. Branding without positioning produces a company that looks confident and cannot explain itself, which is the more common and more expensive failure.
Not by default. I build the positioning, the system, and the first campaigns, then hand them to your team with the documentation and training to run them. Where a team genuinely needs ongoing capacity I can stay on as a long-term partner, but the goal is to leave you able to run it — a permanent retainer for work you could own is a bad trade for you.
Yes, and it is usually part of this work rather than a separate project. Site architecture is where positioning either becomes findable or does not — the structure decides what each page can rank for, and content written before the structure is settled tends to get rewritten.
I co-build the business model, the metrics that matter, and the first ninety days of execution — then stay through the quarter that proves it works. Sometimes that starts from a napkin. More often it starts from chaos.
I map what's actually happening — not what the org chart says — cut the steps nobody defends, and leave behind systems that hold under load. Unglamorous work. Usually where the fastest margin is hiding.
I own the technical side the way I own the rest of it — what gets built, what doesn't, and whether it can be afforded once it's live. The building itself goes through The Creative Collective, the studio I co-run, so a business I'm in gets a product team without having to hire one.
A conversation about what you are building and what is blocking it — no charge, no deck. If there is a fit we scope a defined first phase with a clear deliverable and an end date.