You learned how to design websites. But nobody really taught you how to understand the businesses behind them.
One thing I’ve been thinking about more as I’ve gained experience as a web designer is this:
How are we actually supposed to understand business?
Most of us didn’t study business.
We learned HTML and CSS. Maybe JavaScript. We learned Figma, Photoshop, WordPress, Elementor, responsive design, typography, colour, layouts and UX.
We learned how to make things look good and, hopefully, work well.
But then a client comes along and says:
“We need a new website because we want to get more customers.”
Suddenly, we’re dealing with a completely different question.
That’s not really a web design question.
It’s a business question.
And I think this is something that web designers, especially newer ones, don’t always talk about enough.
We can become quite good at building websites without ever really learning how the businesses behind those websites work.
I’m starting to realise that we don’t necessarily need to become business experts.
But we probably do need to understand business better than we think we do.
You Don’t Need an MBA
The first thing I’d say is that understanding business doesn’t mean you need to become a business consultant.
You don’t need to know how to build a five-year financial forecast. You don’t need to understand every part of accounting, tax, operations or corporate finance.
You simply need to understand enough about a business to answer one important question:
“What is this website actually supposed to do for this business?”
That question changes the way you approach a project.
Instead of immediately thinking about the homepage, fonts, colours and animations, you start by asking:
What does the business sell?
Who does it sell to?
How does it make money?
Why do people choose it?
What problem does it solve?
And what does the business actually want to happen when someone visits the website?
These questions aren’t really about design.
But the answers should influence the design.
Start With the Business, Not the Website
I think this is where I’ve probably changed my own thinking the most.
When we start a website build, it’s very easy to immediately think about the website itself.
What’s going in the header?
What should the footer look like?
How many pages do we need?
What colours are we using?
Which fonts?
What images?
What does the homepage look like?
All of these things matter.
But we can become so focused on building the website that we forget to ask some much more basic questions:
Who am I actually trying to reach?
What do I want them to do?
What is this business actually selling?
Why should someone choose it?
Imagine a business owner tells you:
“We need a modern website.”
What does “modern” actually mean?
Maybe they want something visually impressive.
But maybe what they’re really saying is:
“Our current website makes us look smaller and less professional than we actually are.”
That’s a very different problem.
Or perhaps a client says:
“We’re getting lots of enquiries, but most of them aren’t the right kind of customer.”
Again, that’s not simply a design problem.
There could be an issue with positioning, messaging or targeting.
Understanding the business gives you context for the design decisions you’re making.
The website stops being something you’re simply building for the client and becomes something you’re building to support what the client is trying to achieve.
Learn How the Business Makes Money
This is probably one of the simplest and most useful things a designer can understand.
How does this business make money?
That’s it.
You don’t need their entire financial history. You just need to understand the basic model.
Do they sell products?
Services?
Subscriptions?
Consultations?
Bookings?
Courses?
Are they trying to generate leads?
Do people buy directly from the website, or does the website simply get people to contact the business?
Consider two businesses.
The first sells inexpensive products online.
The second sells a high-value professional service.
Both might technically need a website, but the way you approach them could be very different.
The first might need a very efficient purchasing journey.
The second might need to spend much more time establishing trust, demonstrating expertise and answering questions before someone makes contact.
The website is serving two different businesses.
So the design should reflect that.
Understand the Customer
Once you understand what the business sells, the next question is:
Who is buying it?
This sounds obvious, but it’s surprisingly easy to overlook.
A business might tell you:
“Our website is for everyone.”
Usually, that’s not very helpful.
The more clearly you understand the customer, the easier it becomes to make decisions about the website.
What does this person care about?
What are they looking for?
What questions do they have?
What might make them hesitate?
What would make them trust this business?
What information do they need before they’re comfortable taking the next step?
This is where business understanding starts connecting directly with web design.
If I know what a customer is worried about, I can think about how the website should address that worry.
If trust is important, perhaps testimonials, case studies, credentials and clear information need to be prominent.
If speed is important, perhaps the website needs to get the visitor to the relevant information quickly.
If the purchase is complicated, perhaps the website needs to educate rather than simply sell.
The design is still my responsibility.
But I’m making those design decisions with a better understanding of the person on the other side of the screen.
Understand the Customer Journey
A website doesn’t exist in isolation.
A customer might discover a business through Instagram, Google, a recommendation from a friend or an advert.
They might then visit the website, look around, leave, come back three days later, send a WhatsApp message and eventually become a customer.
The website is one part of that journey.
I find it useful to think about it like this:
Business → Marketing → Website → Customer → Sale → Delivery → Relationship
The website sits somewhere in the middle.
That matters because sometimes a client will come to you expecting the website to solve everything.
But a website can’t fix every business problem.
If nobody knows the business exists, a beautiful website doesn’t automatically create demand.
If the product isn’t right for the market, better typography won’t fix it.
If enquiries aren’t being followed up, a great contact form won’t solve the whole problem.
And if the business doesn’t have a clear offer, redesigning the homepage may only hide the real issue temporarily.
This isn’t a reason for a designer to become pessimistic.
It’s actually quite freeing.
You don’t have to solve every business problem.
You just need to understand enough to know what problem the website is actually being asked to help with.
Ask Better Questions
This might be the most practical lesson I’ve taken from all of this.
Sometimes the best thing a web designer can bring to a project isn’t another design idea.
It’s a good question.
Before building a website, I think it’s worth asking a few key questions.
About the Business
- What do you sell?
- Who do you sell it to?
- What problem are you solving?
- Why do customers choose you?
- What makes you different?
About the Customer
- Who is your ideal customer?
- What are they usually looking for?
- What questions do they ask?
- What concerns or objections do they have?
- What makes them trust you?
About the Goal
- Why are you building or redesigning the website?
- What isn’t working with the current website?
- What would you like the new website to achieve?
- Do you want more enquiries, bookings, sales, awareness or credibility?
- What would make you say, “This website is working”?
About the Website
- What do you want visitors to do?
- Should they call you?
- Send an enquiry?
- Book something?
- Buy something?
- Visit your physical location?
- Learn about your services?
You don’t need to ask all of these questions every time.
But they give you somewhere to start.
And sometimes the answers will reveal that the client doesn’t actually know what they want yet.
That’s okay.
Part of our job can be helping them clarify the problem.
But You’re Still a Web Designer
There’s another side to this that I think is important.
Once you start thinking about business, it can be tempting to go too far in the other direction.
You are not suddenly responsible for running the client’s business.
You don’t need to tell them how to price their products.
You don’t need to redesign their entire marketing strategy.
You don’t need to become their sales consultant.
And you definitely don’t need to pretend you know more about their industry than they do.
They are the expert in their business.
You are the expert they hired to help translate part of that business into a digital experience.
That distinction is important.
The client knows their industry.
You know how to communicate information through a website.
The more you understand about their world, the better you can do your job.
Understanding Business Makes Design Easier
This is probably the biggest reason I want to get better at understanding business.
It actually makes design easier.
When you don’t understand the problem, every design decision can feel subjective.
Should the button be here?
Should this section be bigger?
Should we use this image?
Should the headline say this or that?
But when you understand what the business is trying to achieve, decisions become easier to make.
If the goal is to generate enquiries, the website should make that journey clear.
If the goal is to establish credibility, the website should communicate why the business can be trusted.
If the goal is online sales, the purchasing journey becomes important.
If the goal is simply to provide information, then clarity and accessibility might matter more than adding another impressive animation.
Good design isn’t just about making something look good.
It’s about making decisions that make sense.
And understanding the business gives you more information to make those decisions.
The Goal Isn’t to Become a Businessperson
I’m still learning this myself.
The more experience I get, the more I realise that being a good web designer isn’t just about knowing how to use the tools.
The tools are important.
But eventually you start asking a bigger question:
“Why am I building this?”
That’s where business understanding becomes useful.
I don’t think web designers need to become business experts.
I think we need to become curious about the businesses we work with.
We need to ask better questions.
We need to understand who the customer is.
We need to understand what the business is trying to achieve.
And then we need to use our own skills to help communicate and support that.
Because ultimately, the website is not the business.
It’s a tool that exists to serve the business.
And perhaps one of the biggest steps we can take as web designers is learning to look beyond the website itself.






