8+ years in business

Roots in the financial sector

Design for systems and apps.systems. Custom UI/UX for your system.Custom UI/UX for your operation.

Corporate system, operations dashboard or app:
Leven designs the screens around the people who use them.
Corporate system, operations dashboard or app: Leven designs the screens around the people who use them.

Talk to a specialist

Use & rules

  1. Flow
  2. Screens
  3. Test

In a corporate system, every screen serves a business
rule. Leven studies the operation, listens to operators
and designs the flow before the screen.
In a corporate system, every screen serves a business rule. Leven studies the operation, listens to operators and designs the flow before the screen.

Stage 2 of 3: Screens

A clear rule on every screen. Fields, alerts and permissions designed for
the business rule and the operators' routine.

Leven meeting room with a glass board, two chairs and a phone on the table
With the operators.
Leven office room with a blue sofa, a coffee table, a TV on the wall and a camera on a tripod
For the users.
  • Operation study
  • Task flow
  • Screens and rules
  • Clickable prototypePrototype
  • Engineering handoff

Screen and system,
one project.

Leven's design team
works alongside the engineers who

build the system.

Lobby of the Leven office building, with a marble floor and a lit gardenBuilding terrace with a pergola, grass and armchairs, facing the city

Users don't guess. The interface shows the next step, the key data and the rule that applies to each task of the day.

Users don't guess. The interface shows the next step, the key data and the rule that applies to each task.

No screen goes to code without approval.

Leven 8+

Complex inside,
clear on
the screen.

Leven meeting room with a long table, office chairs and windows onto the city at dusk

Picture the system your team opens
daily. Each record in its place, each

alert with its action at hand, no extra screens.

Leven designs for that.

That's how we design every system. From the operation to the interface.

ProjectsFor systems

From the internal ERP to the customer's app, designed screen by screen.Interface design for those who operate and those who buy.

Every system starts with a study of how it's used.We design ERPs, dashboards, SaaS platforms and custom apps.

We map who operates it, which tasks they repeat and where they get stuck. Then the flow becomes screens in a clickable prototype, walked through by your team and approved before engineering starts.Every screen starts from studying the operation: who operates, what they need to do and which rule applies at each step. Leven serves companies of every industry and size, from simple to complex.

Every screen goes to engineering with a clear rule.Design and engineering follow the Leven method together.

  • CorporateManagement

    systems and ERPERP and back office

    Approvals, routines and reports designed for people who spend all day in the system.Approvals, routines and reports designed for people who live in the system.

  • Your customer's appCustomer app

    In the buyer's handIn the buyer's hand

    Ordering, payment and support in short flows, tested in the prototype.Ordering, payment and support in short flows, tested in the prototype.

  • SaaS platformScale

    Many companies, one interfaceSaaS platform for many companies

    Sign-up, setup and use designed so every company understands the product from the first screen.Sign-up, setup and use designed so every company gets it from the first screen.

  • Management dashboardMetrics

    Data from the whole operation on one screenData from the whole operation on one screen

    The metric that calls for action comes first, with the path to act on it.The metric that calls for action comes first, with the path to act on it.

Interface and use

The design of every Leven system has these parts:

Before engineering starts, Leven studies the operation and maps each task.
Then it designs the flow and the screens of the system or app and builds a
clickable prototype, used by your team as if the system already worked.
That way, the business rule and the operators' routine reach the code.

Talk to a specialist
  • Task map

    Who operates, what they do daily
    and where the task can get stuck.

  • Clickable prototype

    Clickable screens, one by one,
    for the team to validate.

  • Final interface

    System and app screens
    handed to Leven's engineering.
    System and app screens handed to engineering.

Friction in the system

The cost of a
bad screen shows up in the operation.

Finance

Data

Data without context: decision makers
open other screens before acting
Data without context: decision makers open other screens before acting

Leven Tecnologia. Metric and action on
the same screen, in decision order.

Finance

Forms

Fields that repeat what the system
already knows: the team retypes it all

Leven Tecnologia. A field only where the rule asks.

Finance

Permissions

Different profiles on the same screen:
each one sees what they never use

Leven Tecnologia. One screen
for each user profile.

Finance

Alerts

Error messages with no way out:
operators open a ticket and wait
Errors with no way out: operators open a ticket and wait for an answer

Leven Tecnologia. Errors
with the action right beside them.

When you hire us

Design and code with
a single owner:

Leven.
Design and code with a single owner: Leven itself.

Lounge in the Leven office with sofas and a wooden slat partition
  • Design team

    Carefully selected and trained in the
    Leven method, alongside engineering.
    Carefully selected and trained in the Leven method, alongside engineering.

  • Financial roots

    Started out with major Brazilian banks,
    advisory firms and brokerages.

  • Built at Leven

    The people who code the system start from
    the approved prototype.

  • Systems that can't stop

    24/7 support, with optional hosting
    on servers run by Leven.
    24/7 support, with optional hosting on Leven's servers.

Where we design

Meet the people who
design your system.

Your system's screens are born here, in the same house that will code and support the product.

Talk to Leven

Who answers to youWho answers

Every conversation is with the team responsible
for the system, through every phase,
until delivery.
Every conversation is with the team responsible for the system, until delivery.

Non-disclosure agreement

Business rules, screens and system data
are protected by a signed
confidentiality agreement.

Fixed timeline and price

Before the first screen, the timeline, price
and scope of the system are set
in the contract.

  • Our cases
  • Scope
  • About
  • Method
Talk

Clear interface,
stable system

At Leven, interface design is part of software development. Engineering receives the approved flow, screens and the prototype, and the QA team tries to break the system before release. Users find the flow your team has approved.At Leven, interface design is part of software development. Engineering receives the approved flow, screens and prototype, and the QA team tries to break the system before release.

  • ERP designed
  • Access profiles
  • App for clients
  • Clear flow

Example

An app your
customers understand
with no manual at all.

Book a call
Phone with a banking app open on the home screen: the cards with the balance, shortcuts for top-up, transfer, send and analytics, and the latest transactions

YOUR PROJECT

Let's design
every screen of

the system.

Describe the system or app and who will use it. Leven's
design team organizes the scope together with you.
Describe the system or app and who will use it. Leven's design team organizes the scope together with you.

Email[email protected]Phone+55 51 97400-4448