Welcome to the S3A blog

This is the S3A Technologies studio journal. For years we have shipped websites, web applications, brand systems, mobile apps and growth programmes, and almost none of the reasoning behind that work has been written down anywhere outside a client document. That is what this fixes. Three kinds of post will appear here: writeups of recent projects covering what the brief was, what we tried and what actually worked; opinions about performance, typography, identity and shipping under pressure, argued rather than asserted; and reference material for clients — what to ask an agency, what to push back on, and how to read the dashboards we hand over at the end of an engagement. It is written for the person deciding whether to commission something and the person who has to live with it afterwards, which are frequently the same person.

What will you actually find here?

Three kinds of writing will appear here, and each earns its place for a different reason rather than filling a content calendar on a schedule. One looks backward at finished work once the deadline pressure is gone and there is room to be honest about what nearly did not work. One argues a position rather than merely asserting it, because most craft opinions worth having are contested by somebody. And one exists purely to save a client a phone call they would otherwise have had to make, months into an engagement, once a question finally surfaces. None of the three is written to rank for a keyword; each has to justify itself as something worth a reader's actual time, which is a higher bar than most company blogs bother clearing. The categories below are not exhaustive forever, but they are the shape of what to expect for now, and each entry explains specifically what it covers.

Project writeups. Not case studies with the difficulty edited out — the brief, the constraint, the thing we tried that did not work, and the decision that resolved it. The full case studies live under our work; these posts are the reasoning behind them.

Craft opinions. Performance, type, identity, and the compromises that come with a real deadline. So far that has meant arguing that Core Web Vitals are a growth lever rather than a checklist, and that the cheapest performance win is usually one image nobody optimised.

Client references. The questions worth asking before you sign something. Brand vs. identity vs. logo exists because three very different scopes routinely arrive with similar price tags, and knowing which one you are being sold is worth more than any negotiation tactic.

What this blog will not be

SEO-bait. Listicles padded with stock graphs. AI-rewritten LinkedIn slop. Ten Reasons Your Business Needs A Website In 2026. None of that, and not because it is beneath us to write it, but because it does not work as writing or as marketing. That is not a stylistic preference, it is a practical one: the kind of writing that exists only to occupy a keyword is obvious to read and useless to act on, and publishing it would undercut the one reason anybody would trust this page in the first place, that somebody with their name attached to it thought the thing being said was actually true. If we do not have something worth saying, we do not publish anything at all rather than filling the slot with something safe and forgettable. A quiet month with nothing new here is a better signal about the studio than a month filled with posts nobody needed.

How do we decide what to publish?

One test decides it: the post has to cost the writer something, a real project, a real opinion, or a decision that could genuinely have gone the other way, rather than a safe restatement of something already settled. In practice that means a post has to clear three bars before it goes up. It has to be specific enough to argue with, because if nobody could reasonably disagree with it, it is a definition rather than a piece of writing. It has to contain something we learned by doing rather than by reading, which is why most posts here point at an actual project rather than a general theory. And it has to be useful to somebody who will never hire us, because advice that only works if the reader buys something from you afterwards is advertising wearing paragraph breaks instead of a call to action.

That standard means fewer posts. It also means the ones that exist are worth the time it takes to read them, which is the only trade we are interested in making.

Who is this for?

Three audiences will find a reason to read this, though most people move between all three over time rather than staying in one lane permanently. One group already knows us and is looking for context they were never formally handed at the time a decision was made. Another is still deciding whether to work with us and wants evidence beyond a portfolio that, by its nature, only ever shows the projects that went well and never the ones that taught us something the hard way. The third owes us nothing commercially and is welcome regardless, because most of what we know here was learned from people who wrote things down in public without charging anybody for the privilege. Each of the three groups below explains specifically what that particular reader should expect to get out of spending time here.

Clients, current and former. Treat this as documentation you did not have to ask for. When we hand over an analytics dashboard, a brand system or a Moodle install, the reasoning behind the configuration ends up here rather than only in a call you half-remember.

People still deciding. Treat it as evidence of how we think before you ever see a proposal. You can tell more about an agency from how it argues a technical trade-off than from its portfolio, because the portfolio only shows the projects that went well.

Other practitioners. Take what is useful. Most of what we know we learned from people who wrote things down without charging for it, and this is the part of the debt we can repay.

What should you read first?

It depends on what you actually came here for. If you are trying to make a site faster right now, start with the hero-image post: it is one fix, it usually takes under an hour, and it moves the needle further than anything else at that price, which is exactly why it is worth reading before anything more theoretical. If you are commissioning identity work and want to know what you are actually paying for, a brand is a system, not a logo explains what should be in the deliverable list before you sign anything, so you can tell a real system from a mark with a few templates bolted on. And if you are weighing search spend against reputation spend and unsure which comes first, SEO gets you found, ORM keeps you trusted covers why running one without the other quietly leaks the exact customers you paid to attract in the first place.

Tell us what to write about

The useful posts usually start as somebody’s question. Pricing, choosing a stack, hiring an agency versus building in-house, what an audit should actually contain, when to rebuild rather than patch — if you want any of it explained, send it our way. We would rather answer a real question than guess at a topic, and the questions clients ask in the first meeting are consistently better than anything a keyword tool would suggest.

← Back to all posts