First we agree on what to build.
Then we build it.
Before the first line of code, we need to understand the users, the business and the problem the product should solve.
We design the UX and UI, test the main scenarios and prepare a specification with scope, timeline and estimate. So before development starts, you know what we're building and roughly what it will cost.
What we design and specify
We adapt the scope to the project. Sometimes it takes a full design starting from research; other times an audit of an existing product and targeted improvements are enough.
User research
We look at what users need and what the company is aiming for. Without that, good design is hard to do.
Wireframes and prototypes
We validate key screens and scenarios before development. Design mistakes are cheaper to fix at this stage.
Visual UI design
We design an interface that grows out of the UX and fits your brand.
Design system
We create reusable components and rules that keep the product consistent as it develops.
Specification and estimate
We turn the design into a concrete brief. Scope, functionality, priorities, timeline and cost estimate are all in one place before development starts.
UX audit
If you already have a product, we don't have to start from scratch. We find usability problems and propose specific improvements.
What you get
At the end of this phase, you have materials you can start building from straight away.
Prototype of key screens
User scenarios you can click through before development.
Visual design ready for implementation
An interface handed over in a form developers can build from directly.
Design system and components
Rules that keep the product consistent as it develops further.
Specification with estimate
Scope, priorities, timeline and cost estimate in one place.
The files stay yours, even if another team builds it.
Who we design and specify for
For companies that don't want to go into development blind. If you need to understand your users, validate the design and have a clear scope and estimate before development starts, begin with design and specification.
We also help companies whose existing website or product makes users' work harder than it needs to be.
A clear brief before the first line of code
Design mistakes are cheaper to fix in a prototype than in finished code. That's why we walk through the main scenarios before any programming starts.
In the specification we pin down functionality, scope, priorities and dependencies, and prepare an estimate. So you know what will be done, how long it will take and what budget it will need.
Fewer open questions up front means fewer costly surprises.
Why trust Webikon with design
Design and development go together
When we design, we keep in mind what is technically feasible. If we also build the solution, we can turn the design straight into a working product.
We design for real products
We have experience with websites, apps and digital products where design has to hold up not just on screen, but in development and in day-to-day operation.
Another team can use the materials too
We hand over designs and the specification in a form your own team or another supplier can build on.
We can carry on after the design
If the design is going on to development, you don't need to find another supplier. We follow the design with development, then operation and further development.
Design in practice
At Active24, one design had to serve several brands. For Narnia, we built the site structure around what parents actually look for on it.

One design system for an entire portfolio of hosting brands
Development and ongoing evolution of digital solutions for a web hosting and online services provider.


Website for a church primary school
A new website for a church primary school, with a clear structure for parents and a CMS in which the school manages its own content.

Common questions about UX/UI design
If you can't find the answer here, write to us. We'll be glad to help.
Can we order just design and specification, without development?
Yes. We can deliver design and specification as a standalone phase. The materials are yours, and you can hand them to your own team or another supplier. If you like, we can follow the design with the development itself.
Why does a specification matter?
It reduces uncertainty before development starts. It clarifies functionality, scope, priorities and dependencies, and it is the basis for the estimate. So you have a better idea of what will be done, how long it will take and what it will cost.
How much do UX/UI design and specification cost?
It depends on the size of the product, the number of scenarios and the level of detail you need. For a specific brief, we prepare the scope and estimate before work begins. If you have a set budget, we can fit the design to it.
Do you also do UX audits of existing products?
Yes. We review the existing product, find the weak spots in its user experience and propose specific improvements. If needed, we can then prepare a new design and implement it.
Tell us what you need.
We'll work out the rest together.
Tell us what you need to build or what isn't working in your product today. Together we'll go through the brief and propose the next steps.
No-obligation consultation.
We reply within 24 hours.