Robert Sillo building digital products

Robert Sillo

I build websites for businesses, and write about the problems behind them.

A good business can still have a website that undersells it.

Robert Sillo building digital products

A website should make it easy to understand what a business does, who it's for, and why it's worth choosing. When the business moves faster than the website, that gets harder every year.

I've spent more than 15 years building websites for businesses and agencies. These days, I care as much about understanding what a website needs to do as I do about how it's built.

That's the work I do: understand the business, see what's getting in the way, and figure out with you what's actually worth building or changing.

The business can be fine. The website doesn't always show it.

Sometimes the website is the problem.

More often, the business is doing fine, and the website just isn't showing it clearly enough.

Those are the problems I like thinking about.

Traffic is coming in, but business isn't.

More visitors don't automatically mean more enquiries or sales. Before changing the website, it's worth understanding where the friction actually is.

The business changed. The website didn't.

Companies evolve. Their customers, services, positioning and priorities change. The website can quietly become a version of a business that no longer exists.

The website works. But it isn't helping the marketing.

Ads, content and campaigns eventually send people somewhere. If the website doesn't continue the story or make the next step clear, better marketing alone won't fix it.

You're not sure what actually needs to change.

A website problem doesn't always need the same fix. Sometimes it's one page. Sometimes it's the whole site. What matters is understanding what's actually in the way, not guessing based on how old the site feels.

What are you actually paying for?

A website can cost €1,000 or €20,000 and neither price tells you whether it's the right investment. What matters is what the business needs the website to accomplish and what is actually being built to support it.

Where I actually start.

I don't start with pages, layouts, or a CMS.

I start with the business: what it does, who it's for, and what makes it worth choosing.

Then I look at the website next to that. Sometimes the gap is in the message. Sometimes it's the structure, the design, or how someone gets from one page to the next. Sometimes it's the code underneath.

Once I know where the gap is, I can help decide what's worth building. Then I build it.

Is your website still doing its job?

If you're not sure, that's usually a good place to start.