Contact  //

Ready to build something that actually fits?

No cookie-cutters. No templates. Just your problem, solved properly.

Loading
svg
Open

HOW I WORK //

From first message to live site, and everything after.

Every project I've ever done started the same way: a conversation.

Not a form. Not a quote calculator. Just a chat about what you're trying to do and what's getting in the way.

What comes after that conversation varies enormously, because no two businesses are the same, no two briefs are the same, and no two platforms are the right answer for every job.
But the way I work? That stays pretty consistent.

BEFORE WE START //

A few things worth knowing up front.

I work with one client at a time on active builds.

I don't run a team of developers behind me, what you're getting is me, properly focused on your project.
That means I'm selective about what I take on.I'm not the cheapest option. I'm probably not the fastest either.

But I'm the person who'll still be there six months after launch when something breaks, when your hosting acts up, or when you've just realised you need a whole new section.If that sounds like what you're after, read on.

THE PROCESS //

What every project looks like.

The details vary by project type, you'll find the breakdowns for each further down this page. But this is the skeleton everything hangs off.

#1

The Brief Chat //

You reach out.
We meet over coffee, usually 30–45 minutes.
I ask you about your business, your customers, what you're trying to achieve, and what you've tried before that didn't work.

I don't come armed with a pitch. I come with questions. By the end, I should understand your problem well enough to know whether I can solve it and roughly how.

X X X X

#2

The proposal //

I go away and think.

Then I come back with a scope document, not a vague quote, a real scope.

What I'm building, what platform it'll run on, what's included, what's not, and a fixed price.

If the brief is complex or genuinely exploratory, I'll sometimes propose a paid scoping session first. No ambiguity, no 'we'll figure it out as we go.'

X X X X

#3

Discovery & strategy //

Once you're in, we go deeper.

I gather everything I need: existing brand assets, content, logins, competitor references, the stuff you hate about your current site and the stuff you actually want to keep.

For branding-first projects, this is where we do the brand work before a single page gets designed. For migrations, this is where I audit what exists and map what goes where. For custom builds, this is where I spec the architecture.

X X X X

#4

Design //

I design in the browser for most projects, faster, more honest about what actually works.

For bigger builds I'll work through wireframes first, then high-fidelity designs in Figma.

You get two rounds of design feedback. Not because I'm rationing, because more than that usually means we didn't nail the brief in step three, and we need to go back and fix that first.

X X X X

#5

Build //

This is where I disappear for a bit.

The build phase varies most by project type, a WordPress/Elementor site, a Shopify store, a custom CMS layer, a Craft CMS migration.

Each has its own rhythm.I build on a staging environment and share progress as sections are completed. You're not waiting until the end to see anything.

X X X X

#6

Review & launch //

Pre-launch checklist runs through every page, every form, every link, every redirect.

I don't hand you the keys to something I haven't tested properly.Launch is either scheduled (if you need a specific date) or rolling (when it's ready).

I handle the domain pointing, SSL, caching, and any hosting migration required.

X X X X

WHAT STAYS THE SAME //

Regardless of project type.

#1

You talk to me //

Not an account manager, not a junior, not an offshore team.

Every email, every call, every decision- me.

X X X X

#2

Fixed pricing //

I don't do hourly billing on project work.

You get a fixed price in the proposal and that's what you pay.

Scope changes get discussed, not sprung on you in the final invoice.

X X X X

#3

I stay in the job //

No handoff fog.

I'm there for the build, the launch, and what comes after. If something breaks at 9pm, you've got my number.

X X X X

Contact  //

Ready to build something that actually fits?

No cookie-cutters. No templates. Just your problem, solved properly.

svg