Services Four lanes, one studio

One studio, four lanes.

Most businesses end up with a designer, a web developer, an IT contractor and, lately, somebody promising AI — four suppliers who have never spoken, each solving their part in a way that makes the next part harder. This is all of it under one roof, done by one person who has worked every layer of it since MS-DOS 6. Pick one lane or take the lot; nothing here is sold as a bundle you have to swallow whole.

§01 The lanes

What each one actually involves.

Each lane has its own page, written as the honest version: the stages, the tools and why they were chosen, and the ways the work usually goes wrong. Not a sales page — a description you could hold somebody to.

Brand & Video

Identity systems tested at a bag stamp and a shopfront, print specified for real ink, and film graded for the two screens it will actually be watched on — including rescue grades for footage you already have.

PartsIllustrator · Affinity · DaVinci Resolve · Premiere Pro

How this work goes — Brand & Video

Web & App Design

Static-first sites and stores that load on a bad connection, WordPress where somebody will genuinely edit it, apps that install from the browser — and every layout measured at a true 390 px.

PartsHTML · CSS · JS · SvelteKit · WordPress · Cloudflare

How this work goes — Web & App Design

Networks & IT

Multi-tenant networks segmented properly, DNS and email that just work, backups that have actually been restored — and recovery guides written for somebody reading them at two in the morning.

PartsCisco Meraki · VLANs · Cloudflare DNS · Docker · Linux

How this work goes — Networks & IT

AI Integration

The repeat work your week is made of, taken apart and handed back as something that runs — private where the material needs it, measured everywhere, and documented so it survives the handover.

Partslocal LLMs · retrieval · Whisper · Python · APIs

How this work goes — AI Integration

§02 Why one studio

The handoffs are where projects die.

A designer delivers artwork the developer cannot use at small sizes. The developer builds a site the IT contractor cannot get mail working for. Somebody adds an AI tool that needs data nobody has permission to move. None of them is incompetent; the gaps between them are simply nobody's job, and the client — who is not a technologist — is the one left standing in them.

One studio removes the gaps rather than managing them. The mark is drawn knowing it will be a favicon. The site is built knowing what the mail records have to say. The AI workflow is designed knowing which machine it is allowed to run on, because the same person set that machine up.

The trade is honest and worth stating: you get one person's capacity, not a department's. Large simultaneous programmes of work are not what this is. Small teams with real deadlines, and organisations that want the whole thing to make sense together, are.

100% online
USA & worldwide clients
Since 2010
Pro bono for non-profits

Swipe across — The same path whether the thing is a brand, a website that becomes an app, or a whole office network. Each lane page has its own five stages underneath this one.

§03 How a job runs

No packages, no price grid.

Three tiers on a page are a way of guessing at your problem before hearing it. Describe the problem instead and you will get a scope written for that problem, with the parts we would not do marked as such.

You describe the problem, not the solution. What is failing, what it is costing, and what would count as fixed. If you already know the answer, say that too — sometimes you are right.
You get an honest read on fit, timeline and cost. Including whether this is worth doing at all, and whether some of it is better bought off the shelf than built. That answer is free and it is given plainly.
One thing gets finished first. A finished piece of work teaches both of us more about the next five than any amount of planning, and it does it while the amount at stake is still small.
It is handed over properly. Source, documentation, logins and the reasoning — so it runs without us. A build is a cost once, not a bill forever, and there is no retainer holding it up.

§04 Straight answers

Before you write in.

Can we start with one thing?

Yes, and most clients do. One finished piece of work tells you more about whether this is a good fit than any proposal, and it does it while the amount at stake is still small. Nothing here is sold as a bundle you have to take whole.

Will you work alongside our existing developer or printer?

Happily. Work is handed over in the formats other suppliers actually ask for, with the reasoning written down, precisely so other people can pick it up. A studio that makes itself hard to replace is solving its own problem, not yours.

Do you work on a retainer?

Not by default. A build is a cost once rather than a bill forever, and everything is handed over so it runs without us. Ongoing support exists where a client genuinely wants it, but it is never the thing that makes the work function.

Where are you, and does the time zone matter?

The studio works remotely from Thailand, on Indochina Time, for clients in the United States and elsewhere. In practice that means work happens while you sleep and questions are answered as your day starts. Everything is online; nothing here needs a meeting to be a meeting.

Do you work with non-profits?

Part of every year is reserved for pro-bono work, and it has gone to small charities, community groups and local churches — organisations that needed the technology and the look they could never budget for. If that is you, say so in the note.

Tell us what is stuck.

A real person reads every note, and you will get an honest scope rather than a package.

Leave a note See the work