Design that sells: UX/UI design

If your site looks good but brings in no enquiries, the cause is usually the layout. The button disappears into the background, the key information sits three scrolls down, and the form asks for things nobody wants to share. Customers compliment a site like that, then close the tab. So we start UX/UI design with one question: what should the user do on this screen? Everything else is arranged around that answer.

The headline has to stop the reader, the offer section has to explain what sets you apart from competitors, and the call to action has to be the obvious next step. If we set the goals and audience earlier, as part of website strategy and direction, the design is that plan translated into screens. If there was no strategy phase, we ask the same questions on the first call.

You can tell a good design by the fact that the user never has to think: they know where they are, what they can do and what happens after a click. That clarity comes from heading hierarchy, spacing, contrast and the order of sections, so that is where we start. Colours, photos and details come once the layout works.

The design is made in Figma and moves from a structural sketch to an interface ready for code. We do not use ready-made themes: every screen is drawn from scratch, around what your site is meant to sell and to whom. We set the exact scope in the quote, but in practice it almost always consists of these elements:

• Wireframes and prototypes

  from a low-fi sketch to a clickable prototype you can walk through on your phone like a finished site.

• UI design

  typography, colours, imagery and details that match your brand and serve the job of each screen.

• Design system, if the site is meant to grow

  components, typography and colours you assemble new pages from.

• Responsive variants

  mobile-first design, from screens 375 px wide up.

• Conversion-focused design

  one call to action per section and a user journey with no dead ends.

• Prototype testing, if you add it

  we check it with real users before it reaches code.

We start with low-fi wireframes: the bare structure, no colours or photos. At this stage we talk about the order of content and the route the user should take; the shade of the button can wait. Once the layout is approved, we move on to UI design: typography, colour, imagery and detail. Finally we link the screens into a clickable prototype you can walk through on a phone and a computer like a working site.

You review the design in Figma with comment mode on. You leave a note on the exact element, so you do not have to write an email about 'that blue button on the left' and we do not have to guess which one you mean. Each stage includes two rounds of revisions. After a well-run strategy phase they are usually enough, and if it turns out a third round is needed, we quote it separately and tell you before we start.

You approve the design before any code is written, so you never pay to rework finished views. Whoever builds the site gets the full set: every screen, state and responsive variant. With us, the design and the code are handled by the same person, Kacper Baranowski, so nothing gets lost between the wireframe and the website build and code.

Most of your customers will open the site on a phone, so we start the design at a 375 px wide screen and only then expand it to desktop. Buttons sit within thumb reach, forms are short, and the most important information fits on the first screen. Desktop gets more space and the same logic.

For the site to sell, we keep one main call to action per section, lead the journey with no dead ends, and place trust signals where doubts appear. Contrast, readable type, a visible focus state and keyboard use are planned in the wireframes already, because WCAG 2.2 AA accessibility is one of our acceptance criteria for a site, and it is cheaper to design it in from the start than to fix it after launch. If animation and 3D are in scope, this is also where we decide where motion helps and where it distracts.

Stores and apps add states that are easy to forget: an empty cart, a form error, data loading, a confirmation after sending. We design them together with the main views, because those are the moments when users most often give up. On the prototype you see them before your customer ever would.

The price depends on the number of views, states and variants, on whether you need a full design system, and on whether you already have a visual identity. A business card site with a few views is a different scope from a site with an offer, a blog and landing pages, so we do not give one figure without a call. You get a free quote with the scope and schedule written out within 48 hours of the call, so you decide knowing the figure and the dates.

If you have a brand book or visual guidelines, we follow them. If you do not, we set the visual direction together during the design stage, and if you want, we extend the scope to an identity built from scratch. You can also add three standalone items to the design, at the same prices as in our pricing. They pay off most when your own team will grow the site later, or when the customer journey is long and costly, as in a store or an app.

• Design system

  components, typography and colours described so that your team can grow the site without asking us about every change. You can hand it to your developer or leave the build to us. From PLN 2,500 net.

• Usability testing

  before the design is closed, we test the wireframes with real users from your target group. You learn where they stop and why they leave before anything reaches code. From PLN 1,500 net.

• Mobile screen design

  phone views designed separately, laid out for thumbs and a smaller screen instead of an automatic downscale of the desktop. From PLN 1,200 net.

After sign-off you get the Figma source files: every screen, component and style. You can pass them to another vendor or to your own team without asking anyone for permission. If a design system was in scope, you also get a component library for assembling new pages without designing from scratch.

If we build the site, the design goes into code one to one, with the same spacing, states and motion, and you have 30 days of free fixes for bugs in our code, counted from acceptance. If someone else builds it, they get a complete set of materials and nothing is left to interpretation. Either way, the live site looks like the approved prototype.

When you want to add a section, a campaign landing page or a new subpage after launch, you assemble it from the ready components of the design system instead of ordering a design from scratch. A year on, the site still looks like one whole, and every change takes less time.

Design is part of every offer we have. For business websites it leads to an enquiry or a call. In online stores we design the buying path from the product page to payment. For industry websites the layout follows the habits of that industry's customers: a menu and booking for a restaurant, a portfolio for a contractor, proof of expertise for a law firm.

In digital products we start with user flows and a clickable prototype before any code exists. That is how we work on a web app and a mobile app, where gestures and thumb navigation come into play. You can also order the design on its own, for example for your own developer. Tell us what you are building and when in the form at the bottom of this page. We reply no later than the next working day, and you get a quote with the scope and schedule within 48 hours of the call.