Design

Interface design (UI/UX) for services, accounts and CRM systems

Interface design (UI/UX) is a direction of the Design service at Best Boost Partners for web services, personal accounts and CRM systems. The studio’s own designer starts from user scenarios and a screen map, builds a prototype that can be clicked through, and then draws the screens: tables, filters, forms and dashboards with their empty, loading and error states. You receive the source files of the layouts, the clickable prototype and a design system that developers build from.

What do we do in an interface design?

  1. User scenarios

    We write down who uses the system and what each role does in it step by step: creates an order, checks a report, approves a payment. The scenarios show which screens are needed and which actions happen most often.

  2. Screen map

    The screen map lists every screen and the transitions between them. The map shows how many steps a task takes and where a user can get stuck.

  3. Clickable prototypes

    Wireframe screens are linked into a prototype that can be clicked through in a browser. You and your staff walk through the main scenarios before the visual design and the development start.

  4. Tables, filters, forms and dashboards

    Working screens are drawn for real data: long names, empty cells, hundreds of rows. For tables we define sorting, filters, bulk actions and column settings, and for forms the order of fields, hints and input checks.

  5. Empty, loading and error states

    Every screen is drawn as it looks with no data, while data loads and when something fails. The messages say what happened and what the user can do next.

  6. Design system for developers

    Colours, text styles, spacing, icons and components with their states are collected into a design system. Developers assemble new screens from ready components and do not wait for a layout of every screen.

What do you get with an interface design?

  • A document with user scenarios by role and a screen map with the transitions.
  • A clickable prototype of the main scenarios, opened by a link in a browser.
  • Layouts of all screens with empty, loading and error states, as source files.
  • A design system: components, their states, text styles, colours, spacing and icons.
  • A specification for developers describing the behaviour of tables, filters, forms and notifications.

When is an interface design needed?

  • You are planning a web service, a personal account or a CRM and want to check the logic on a prototype before paying for development.
  • The internal system works, but new staff need long training, and the same mistakes in forms and tables repeat.
  • Developers add screens without a designer, and the same action looks and behaves differently in different parts of the product.
  • A site is getting a personal account or an admin panel, and their screens need one shared set of components.

Frequently asked questions

What is the difference between UX and UI in your work?

UX covers the logic: the scenarios, the screen map and the prototype that shows what a user does step by step. UI covers the look of the screens: grid, typography, colour, components and their states. We do both parts in this order, and the visual design starts after the prototype is approved.

Why is a clickable prototype needed before the design?

A prototype is cheap to change, and a finished interface is expensive to change. Walking through the scenarios on a prototype shows missing screens, extra steps and unclear names before the designer draws the final layouts and the developers write code. The prototype also serves as a shared reference for the client, the designer and the developers.

Can you design the interface of a CRM that Best Boost Partners will develop?

Yes. Best Boost Partners has a separate service, CRM development, so the interface can be designed as a stage of that project or as a separate order for your own developers. In both cases you receive the same set: layouts, a prototype, a design system and a specification.

Tell us about the project

Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.

Prefer to talk first? Write to us on WhatsApp or by email.

Task

What do you need? Choose one or several.
Topic of the site

Project

An example helps us understand the style and scale you have in mind.
CMS or platform

Contact

How should we reply?