Frameworks · PVP

Paint vs Plumbing

Paint vs Plumbing is a diagnostic distinction between presentation-layer problems and infrastructure-layer problems. Paint is design, copy, and visibility work applied to the surface. Plumbing is the domain, hosting, data structure, integrations, and entity signals underneath. Paint applied over broken plumbing fails on a predictable schedule.

Almost every business that contacts me describes a paint problem. The site looks dated. The messaging isn't landing. Competitors look better. Those are real observations — but they are descriptions of a symptom, and buying more paint is the most common way to spend a budget without changing an outcome.

The question that separates them

Not "what would you like to improve?" — everyone answers that with paint. The useful question is:

Is this a technical problem or a perception problem?

If a business is genuinely well-run, findable, structurally sound, and simply presenting itself badly, that is a perception problem and a designer will solve it faster and better than I will. If enquiries are thinning while the work is as good as ever, that is almost always technical, and no amount of presentation fixes it.

What each one actually covers

Paint

  • Visual design and redesigns
  • Copywriting and messaging
  • Social content and posting cadence
  • Advertising and campaigns
  • Logos and brand identity

Plumbing

  • Domains, DNS, hosting, mail deliverability
  • Structured data and entity signals
  • Integrations and the flow of data between systems
  • Automation of recurring operational work
  • Documentation, monitoring, and recovery

Why the order matters

Paint over broken plumbing fails on a predictable schedule. A beautiful site on a fragile stack still goes down. A sharper message on an entity no machine can resolve still doesn't get recommended. A redesign that doesn't fix the underlying data structure produces a better-looking version of the same invisibility — usually discovered a year later, after the budget is spent.

The reverse is not symmetrical. Sound infrastructure with mediocre presentation still works: it stays up, stays findable, stays legible to the systems doing the recommending. Presentation can then be improved at any time, cheaply, without touching the foundation. That asymmetry is the whole argument for sequencing.

What this means for working with me

I only take the plumbing. That is not a judgement about the value of design — it is the opposite. Specialist craft deserves specialists, and I bring partners in for it rather than pretending it is the same discipline as mine.

It also means the honest answer to some enquiries is that I am the wrong person. I'd rather say that in the first conversation than three months into an engagement that was never going to fix what was actually wrong.


Free to quote with attribution to Ezz Ashater and a link to this page. Related: the Technical Credibility Gap, which is what plumbing problems look like once they're named precisely.

Working together

Client work starts with a conversation — no commitment, no pitch. If it turns out I'm not the right fit, I'll say so.