/

/

BTE CRM Platform

BTE CRM Platform & Landing Page

One app to run a printer sales and service business across Latvia: orders, invoices, couriers and service requests, on desktop and mobile.

UI/UX Design

Product Design

E-Commerce Design

2024

“

After several half-finished works with other UX/Designers, Artis was like a solution to all previously unorganized things. With an easy approach, from the word go. The work is dynamic and understandable to everyone and the result is impeccable.

After several half-finished works with other UX/Designers, Artis was like a solution to all previously unorganized things. With an easy approach, from the word go. The work is dynamic and understandable to everyone and the result is impeccable.

Oskars Štāls

BTE

Overview

Overview

BTE ran its day on an in-house CRM that was hard to use, with spreadsheets and email covering whatever the CRM couldn’t do. I redesigned the CRM so orders, invoicing, couriers, service requests and team messages are in one app, and I designed and built a Framer website to launch it at an industry trade show.

The challenge

The challenge

Biroja Tehnikas Eksperts sells, rents, services and supplies printers for businesses and public institutions across Latvia. As it grew from Kuldīga to Riga and other locations, its workflow stopped keeping up.

The company already had an in-house CRM, but it was hard to use and lacked many features the team needed, so a lot of the work happened in spreadsheets and email instead. Branch managers couldn’t see daily sales, unpaid invoices or open service requests without checking several places. Orders arrived by email, so time-sensitive requests from municipalities and schools were easy to miss. Courier tasks were written down by hand, and nobody could track delivery status or see who had too much on.

Spreadsheets & Emails

Daily sales in emails

68%

Manual service requests

44%

Invoice spreadsheet

25%

The brief was a CRM that handles the daily work in one place, and a website to present it at an industry trade show.

The brief was a CRM that handles the daily work in one place, and a website to present it at an industry trade show.

The brief was a CRM that handles the daily work in one place, and a website to present it at an industry trade show.

Before - an order in the old CRM

Who uses it?

Who uses it?

Four groups of people use the CRM, and each needs something different from it, so I designed the screens around their roles.

Branch / work manager

Branch / work manager

What they need

The state of the day at a glance, and the numbers per branch

Answers spread across the old CRM, spreadsheets and email

Office and sales staff

Office and sales staff

What they need

Register orders, update item status, contact the customer

Requests buried in email threads

Service technician

Service technician

What they need

A request with the customer, the equipment and the parts in one place

What was missing in the old CRM

Courier

Courier

What they need

Assigned deliveries, addresses and customer details on the phone

Hand-written task lists, no status tracking

Discovery

Since BTE already had a CRM, I started by auditing it. I took screenshots of every module (orders, invoices, service, couriers, customers, catalog, procurement and the dashboard) and marked each problem on the screens in Figma. I also worked from the Riga office and went through the old dashboard with the owner, marking each widget as needed, to shrink, or to move.

Audit of the old orders list, with numbered issues

The audit showed the same problems across modules. Order tags used so many colours that none stood out, filters and corner styles changed from page to page, and lists were crowded with labels, which made them hard to scan.

The audit showed the same problems across modules. Order tags used so many colours that none stood out, filters and corner styles changed from page to page, and lists were crowded with labels, which made them hard to scan.

The audit showed the same problems across modules. Order tags used so many colours that none stood out, filters and corner styles changed from page to page, and lists were crowded with labels, which made them hard to scan.

Reference board. How other ERP and CRM products solve the same patterns.

At the same time I collected examples of how other ERP and CRM products handle tabs, tags, breadcrumbs, forms and dashboards, and used Material Design components and articles on mobile navigation and the serial position effect as reference.

User flows

I designed each module as a sequence of states so the developers could see every step. Four flows carry most of the daily work.

A service request starts when staff add the customer, the items and the customer’s equipment. The request is then handed to a technician, who can be swapped later. A handover and acceptance act closes the repair, and the device is issued back to the customer.

A service request starts when staff add the customer, the items and the customer’s equipment. The request is then handed to a technician, who can be swapped later. A handover and acceptance act closes the repair, and the device is issued back to the customer.

A service request starts when staff add the customer, the items and the customer’s equipment. The request is then handed to a technician, who can be swapped later. A handover and acceptance act closes the repair, and the device is issued back to the customer.

In an order, staff update the status of each item and contact the customer from inside the order, and the app confirms when the message has gone out.

In the catalogue, a new product can be created from an existing one in three steps (name, price, extra details), with technical parameters added and confirmed afterwards, so similar printers don’t have to be entered from scratch.

The courier list shows how many open deliveries each courier has. On a phone or tablet, couriers see their own orders with the address and customer details.

The courier list shows how many open deliveries each courier has. On a phone or tablet, couriers see their own orders with the address and customer details.

The courier list shows how many open deliveries each courier has. On a phone or tablet, couriers see their own orders with the address and customer details.

Iterations

I worked module by module and reviewed each version with the owner. Before starting on the modules, I tried several visual concepts in light and dark and built a colour scale from BTE’s brand pink.

Before

After

The first dashboard redesign used oversized type and carried over the old widgets. Over the next rounds I cut the font sizes, shrank the widgets the owner flagged and settled on five cards: company news, new orders, unpaid invoices, couriers and price requests.

The first dashboard redesign used oversized type and carried over the old widgets. Over the next rounds I cut the font sizes, shrank the widgets the owner flagged and settled on five cards: company news, new orders, unpaid invoices, couriers and price requests.

The first dashboard redesign used oversized type and carried over the old widgets. Over the next rounds I cut the font sizes, shrank the widgets the owner flagged and settled on five cards: company news, new orders, unpaid invoices, couriers and price requests.

Low stock, maintenance and production widgets were tested but didn’t make the cut.

Design decisions

Managers start on the home screen, because their main problem was piecing together the state of the day from several places. It shows company news, new orders with their production or sourcing status, unpaid invoices, open tasks per courier and the latest price requests.

The numbers are in a separate daily report: today’s store sales and subscription revenue compared with last month, invoice and service totals per branch, active rentals and planned maintenance. The home screen lists what needs doing, and the report shows how the business is doing.

The numbers are in a separate daily report: today’s store sales and subscription revenue compared with last month, invoice and service totals per branch, active rentals and planned maintenance. The home screen lists what needs doing, and the report shows how the business is doing.

The numbers are in a separate daily report: today’s store sales and subscription revenue compared with last month, invoice and service totals per branch, active rentals and planned maintenance. The home screen lists what needs doing, and the report shows how the business is doing.

Each order is one record from intake to invoice, with the customer, shipping address, items, prices and status. Orders used to live in email; now everyone works from the same record.

The customer page collects branches, order history, service history, invoices, offers, the customer’s equipment and the goods they’ve ordered, so whoever takes a call or a repair has the whole history in front of them.

Messaging is part of the app. Company news with replies, direct messages and comments on work tasks replaced separate chat tools, so conversations stay next to the work they’re about.

Messaging is part of the app. Company news with replies, direct messages and comments on work tasks replaced separate chat tools, so conversations stay next to the work they’re about.

Messaging is part of the app. Company news with replies, direct messages and comments on work tasks replaced separate chat tools, so conversations stay next to the work they’re about.

I reordered the sidebar by how much each module is used day to day and fixed the active state so nested pages always show where you are.

Design system, themes and mobile

Design system, themes and mobile

The final design has 19 modules, from orders and rentals to production, service and price requests, across 131 desktop screens, with mobile versions of the main views. A shared design system of components keeps them consistent and gave developers a clear spec to build from. Every screen has a light and a dark version, because staff spend long hours in the app and some of them work in low light.

Modules

19

19

Desktop screens

131

131

Themes Light & Dark

2

2

BTE presented the new CRM at trade show and needed a website for it. I designed and built one in Framer, crm-erp.lv, which presents the CRM’s main features with real product screens.

BTE presented the new CRM at trade show and needed a website for it. I designed and built one in Framer, crm-erp.lv, which presents the CRM’s main features with real product screens.

BTE presented the new CRM at trade show and needed a website for it. I designed and built one in Framer, crm-erp.lv, which presents the CRM’s main features with real product screens.

Outcome

The shared spreadsheets and order emails were retired, leading to fewer missed orders, faster invoicing and time saved every day.

The shared spreadsheets and order emails were retired, leading to fewer missed orders, faster invoicing and time saved every day.

The shared spreadsheets and order emails were retired, leading to fewer missed orders, faster invoicing and time saved every day.

What I learned

What I learned

Auditing the old CRM before designing anything showed me that many of the problems came from inconsistency, not missing features. Fixing the patterns once in a design system solved them across all 19 modules. Next, I’d test the courier and technician screens with the people who use them on the road, since most of my feedback came from the owner.

Got a project? Let’s talk.

Let us make something great together. Book a free 30-minute call.

Got a project? Let’s talk.

Let us make something great together. Book a free 30-minute call.

Got a project? Let’s talk.

Let us make something great together. Book a free 30-minute call.