PIPELINEGuide
Web design: examples from practice
How professional web design is actually used in the daily operations of small businesses — concrete processes instead of product promises, including the cases where it didn't work.
In practice, web design almost always starts with exactly one process, not with an overall concept. A design that's handed over as a system survives a change of agency — a design that only exists as an image file doesn't. Expansion only happens once the first step has demonstrably worked in real operations.
01 — Practice
What this looks like in concrete terms
A design that's delivered as a system survives a change of agency — a design that only exists as an image file doesn't.
A typical starting point looks like this: the business names the one process that causes the most trouble. What already exists in terms of logo, colors, visual language — and what works.
After going live, you don't expand immediately but observe. Components and rules are documented and handed over.
02 — Fit
When it's worth it
- The process in question occurs at least weekly.
- It follows rules you can write down — even if there are exceptions.
- Today it's manual work that no one enjoys doing.
- There's one person who decides, not three who need to coordinate.
- You can name what would tell you it worked.
03 — Scope
When we advise against it
- The process is still changing. As long as you're adjusting the process itself, manual work is more flexible and cheaper.
- Exceptions outweigh standard cases. Then you're automating exceptions, and that gets expensive.
- There's no data foundation. Without digitally available source data, the basis is missing.
- Volume is too low. With five transactions a month, no system pays off — not even an affordable one.
- The real bottleneck lies elsewhere. If you don't have enough inquiries, you don't need faster processing.
04 — Questions
Frequently asked questions
What if we don't like any of the directions?
Then we go back to the discovery phase — usually that means something important about the business hasn't been understood yet. It rarely happens, but better to start fresh than to force a design.
Who owns the files?
You do. You get the source files and the documentation. If you work with someone else later, they can continue with them.
Will this look good on mobile too?
We design the narrow view first, because that's where the majority of visitors arrive. The wide view is the easier case, not the other way around.
How many revision rounds are included?
Two rounds per draft are standard and usually sufficient, because the directional decision is made after the first presentation. Additional rounds are possible but noticeably extend the timeline.
Do we even need custom design?
Not necessarily. If you need a site with five pages and no brand ambitions, a well-adapted standard system is the more sensible choice. Custom design pays off when you need to stand out from competitors or manage many pages.
Do you also provide image material?
No, that's not part of the design system. But we specify exactly what kind of images are needed and recommend suitable sources or a photographer if required.
What about accessibility in design?
We check contrast, font sizes, focus presentation, and click areas against WCAG 2.1 AA. That's significantly cheaper in design than later in implementation.
05 — Next
Related pages
- Web design — Overview
- Web design — viability
- Web Design — Team and Acceptance
- Web Design — Duration
- Web Design — Contract and Ownership
- Web design — Provider comparison
- Web Design — How It Works
- Web design — common mistakes
- Have a website created
- Landing page
- Website relaunch
- All guides
Web design by region
Next step
We'll look at your starting position.
Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.