The Words Are the Interface

I can design a layout in an afternoon. I can build the component, wire up the backend, ship it.

The thing that stalls me every time is the sentence above the fold.

Not the color palette. Not the grid. The words.

The part nobody warns you about

When I rebuilt my own site recently, the design took a weekend. The copy took two weeks — and I’m still editing it.

That’s embarrassing to admit as someone who calls himself a designer and developer. But I think it’s actually normal, and most people just don’t say it out loud.

Design has rules you can lean on. Spacing scales, type systems, color theory — there’s a right answer you can reason your way toward. Copy doesn’t work like that. There’s no grid for a sentence. You’re not arranging elements, you’re deciding what’s true about yourself or your product, and then saying it in the fewest words that still land.

That’s a different skill. It’s closer to editing than writing — most of the work is deciding what to cut.

Why it matters more than the interface around it

Here’s the thing that took me a while to actually believe: the interface is the frame, the copy is the message. People forgive an ugly button. They don’t forgive not understanding what you do.

I’ve looked at dozens of portfolios and product pages while working on Jetdomains and my own site. The ones that don’t work almost never fail because of bad design. They fail because the headline could belong to anyone. “Innovative solutions for your business” tells a visitor nothing about who’s talking or what problem gets solved. It’s copy shaped like a sentence but doing none of a sentence’s job.

The good ones are specific. They pick one true thing and say it plainly. That specificity is what makes something feel like it was written by a person instead of assembled from a template — which, not coincidentally, is the same thing I noticed about the personal sites that stuck with me.

What’s actually hard about it

For me it’s not vocabulary. It’s distance. I know Jetdomains too well to see which part of it actually matters to someone hearing about it for the first time. Every sentence I write about it feels either too obvious or too buried in context only I have.

I think that’s the real challenge with copy for your own work — portfolio, product, whatever it is. You’re too close to know what’s load-bearing and what’s just familiar to you. A stranger reading it has none of that context, and the words have to do all the work a conversation would normally do for free.

A few things that have actually helped me get unstuck:

Write it like you’d say it out loud to one specific person. Not “our audience” — one person, by name if you can picture them. It kills the corporate flattening almost instantly.

Cut the sentence in half, then cut it again. The first draft is always explaining. The second draft is just stating.

Steal structure, not words. Reading how other people build a sentence — the rhythm, where they choose to stop — taught me more than any copywriting guide. You’re not copying their line, you’re noticing how they made room for the idea to land.

Say the specific thing, not the impressive-sounding thing. “I build systems that hold up after launch” beats “innovative, scalable solutions” not because it sounds better, but because it’s the one sentence a competitor literally cannot copy-paste onto their own site.

The uncomfortable conclusion

I don’t think copywriting is a skill you bolt onto design or development. I think it’s the actual product, and design is the delivery mechanism for it.

That’s a harder thing to accept than it sounds, because it means the hours I spend rewriting one headline aren’t a distraction from the “real work.” They are the real work. The interface just makes it visible.