Accounts 218
| Account | Segments | Owner | Open deals | Pipeline | Win probability | Last activity |
|---|

UI/UX & product design · Portfolio 2026
We design mobile apps, websites, SaaS products and enterprise software — and we build them. This page is a cross-section of our concept work, from consumer apps to the complex, custom software enterprises run on. Every concept screen is live interface, not a flat mock-up: hover it, switch the tabs, click through.
Contents
Apps designed for a thumb and a few spare seconds. Two concepts in two very different moods — a money app that has to feel safe, and a travel app that has to feel like the trip already started.
01 — Mobile · Fintech
A personal finance app for people who check their balance more than their email. Balance and this week's spending sit on the first screen, card controls are one tap away, and sending money is a keypad and a name — nothing else.
Opened three banking apps to work out whether she could afford a weekend away, then gave up and guessed.
Sees her balance and this week's spending before the tram reaches the next stop — and freezes a lost card in one tap.
The first screen answers "how much do I have" and "where is it going" before anything is tapped.
Freezing a card is the first control, not buried in settings — the moment someone needs it, they're stressed.
The send flow is a person and an amount. Confirmation happens on the button itself.
02 — Mobile · Travel
A booking app for small, characterful stays. Photography leads, prices are shown per night with the total one line below, and once booked, the trip screen becomes the one thing a traveller needs at the door.
Fell for a cabin, reached checkout, and found fees that doubled the price. Closed the app.
Sees the full price on every card, books in three taps, and has the key-box code waiting on the trip screen.
The full price sits under the nightly rate on every card, so nobody feels tricked at checkout.
Price and Reserve stay pinned while the guest scrolls photos and reviews.
After booking the app switches from shopping to logistics — when, where, and the key-box code.
A selection is shown here. The Mobile apps page has every concept, with its use case and the design decisions behind it.
Pages whose job is to convert. A SaaS landing page that explains a product in one scroll, and a product page that sells a €649 chair to someone who can't sit in it.
03 — Web · SaaS landing page
A marketing site for an accounting automation product. The headline states the outcome, the product shot proves it, and pricing is on the same page — because finance buyers want the number before the demo.
Ledgerly matches every bank line to an invoice, flags what doesn't fit, and hands your accountant a clean month — automatically.
Bank lines matched to invoices with 98% accuracy, learning from every correction.
Only the lines a person needs to see, with a suggested fix for each.
Export to Xero, QuickBooks or DATEV with one click at month end.
1 bank account
500 transactions
5 bank accounts
5,000 transactions
Exceptions inbox
Unlimited accounts
SSO & audit log
Dedicated manager
Read five vendor sites that all said "streamline your workflow" and never mentioned a price.
Understands the outcome in one headline, sees a real product screen, and knows the price before she books a demo.
"Close the books in hours" is what a CFO repeats in a meeting; the feature list comes second.
A real-looking product shot, including a messy "Unknown" line, makes the claim believable.
Finance buyers qualify themselves on price; hiding it costs more leads than it protects.
04 — Web · E-commerce
A product page for a furniture brand. Big imagery, upholstery swatches that recolour the product as you pick them — try it — and delivery, returns and dimensions answered before anyone has to ask.
Couldn't picture the chair in moss green and worried about delivery dates and returns.
Recolours the chair herself, sees delivery and the 100-night trial under the button, and pays monthly.
Swatches recolour the product itself, not a tiny chip — the step that most often stalls a furniture purchase.
Delivery time, trial and guarantee sit under the button, where hesitation actually happens.
The monthly option is beside the price, not in a footnote, for buyers comparing against their budget.
A selection is shown here. The Websites & e-commerce page has every concept, with its use case and the design decisions behind it.
Dense, dark consoles for power users — sales ops, analysts, operations leads. More rows per screen, an icon rail instead of a sidebar, keyboard-first everything, and colour used as data: every hue in a tag or a chart means something.
05 — Dashboards · CRM
Two hundred accounts, one screen. Segment tags, owner, pipeline and win probability sit in a single row so a sales-ops lead can scan, select and re-assign in bulk without opening a record.
| Account | Segments | Owner | Open deals | Pipeline | Win probability | Last activity |
|---|
Exported the CRM to a spreadsheet every Monday to see which deals were at risk and who owned what.
Filters, selects twelve at-risk accounts and reassigns them in under a minute, without leaving the console.
36px rows and tabular numbers keep 12 accounts in view without the table turning into noise.
Ten segments read faster than a percentage, and the colour shifts as a deal warms up.
Actions appear only when rows are selected, floating where the eye already is.
06 — Dashboards · Analytics
The control-room view for fulfilment. Every KPI carries its own 14-day trend, the main chart separates orders from returns and backorders, and a live feed shows exceptions as they happen.
Learned about a missed carrier pickup from an angry customer email the next morning.
Sees the exception in the live feed within minutes and reroutes the parcels before the cut-off.
A sparkline in every KPI answers "is this normal?" before anyone asks.
On a dark canvas, a soft glow marks the series that update in real time.
The feed only shows what needs a human — a late carrier, a short pick, a failed payment.
07 — Dashboards · Automation
Accounts-payable teams build their own invoice workflow: capture, extract, three-way match, then either post automatically or route to a person. No tickets to IT, and every rule is readable at a glance.
Keyed every invoice by hand and checked it against the PO and goods receipt in two other systems.
Built the workflow himself; nine in ten invoices now post on their own and he reviews only the exceptions.
Triggers, AI, logic and actions each have a hue, so the shape of a workflow reads from across the room.
Each branch shows how many invoices took it — the canvas doubles as a report.
Every setting explains itself in one sentence; finance users never see an expression editor.
A selection is shown here. The SaaS & dashboards page has every concept, with its use case and the design decisions behind it.
ERP software in two visual languages: a light, quiet workspace for the people who live in it eight hours a day — finance, warehouse, HR, procurement — and a navy boardroom view for leadership. Colour is reserved for status and for the one action on each screen.
08 — ERP · Finance
Controllers live in this screen for the month-end close. We cut it down to the four numbers they report upward, one cash-flow chart, and the receivables they need to chase today — everything else is one click deeper.
| Customer | Invoice | Due | Status | Amount |
|---|
Spent the first week of every month pulling numbers from four reports and chasing overdue invoices by email.
Opens one screen with the four numbers she reports upward and sends overdue reminders straight from the list.
Overdue receivables sit above the fold with bulk reminders, so the screen ends in an action, not a report.
Neutral for money in, accent for money out — the same rule on every chart in the product.
⌘K reaches any invoice, vendor or report. Finance teams type faster than they click.
09 — ERP · Inventory
Planners need to know what will run out before it does. Stock cover is shown in days, not units, and the bin map turns a 2,000-row spreadsheet into a picture of where the warehouse is full.
| SKU | Item | On hand | Cover | Status | Reorder |
|---|
Found out a product had run out when the pickers did.
Sees "2 days of cover" in red and raises the purchase order from the same row.
"6 days left" is a decision; "412 units" is a lookup. Status chips use text and colour, never colour alone.
Raising a PO happens from the table that surfaced the shortage — no context switch into another module.
The bin heat-map answers "where is there room?" for the receiving team in a glance.
10 — ERP · Sales
One board from first quote to delivered order. Account managers see value per stage at the top of every column, and every card shows the one thing blocking it from moving right.
Spent stand-ups explaining why deals were stuck instead of unsticking them.
Opens the board, sees the blocker on every card and the value per stage, and ends the meeting early.
Stage value sits on the column, so the forecast reads left to right without opening a report.
"Awaiting credit check" or "Stock short" tells the owner what to do next.
Same data, two views — the board for stand-ups, the list for bulk edits.
11 — ERP · People
Shift managers approve leave against real coverage. The calendar shows who is out across the next two weeks, and the request panel tells them whether approving it leaves the floor short.
Approved leave, then discovered the shift had no certified forklift driver that day.
Sees the coverage warning before she clicks approve, and decides in seconds.
The warning ties a request to the skill it removes from the shift — the real reason managers hesitate.
Non-working days are tinted so the eye lands on the days that need staffing.
Leave type is written on the bar as well as colour-coded, so it survives print and colour-blindness.
12 — ERP · Procurement
An inbox for approvers. Click any request on the left — the drawer shows the budget impact and the approval chain, so a sign-off takes seconds instead of an email thread.
Approved requests from email threads without knowing what was left in the budget.
Works down an approval inbox with budget impact and the approval chain beside every request.
List and detail side by side — approvers move down the queue without losing their place.
Every request shows what it does to the remaining budget before anyone signs.
The step tracker shows who approved, who's next, and which steps only apply above a spending threshold.
13 — ERP · Mobile
Pickers work with gloves on and one hand free. Big targets, a scanner that's always ready, and a pick list that orders itself by walking route.
Every tap target clears 48px so it works with work gloves and on a moving forklift.
The list sorts by bin location, so the next item is always the next shelf.
A single full-width button at thumb height. The rest of the screen is information.
14 — ERP · Leadership
One overview, three lenses. Switch between CFO, COO and Sales views and the KPIs change to what that role reports on — try it. AI-written insights on the right explain the movement and link to the fix.
Asked an analyst for the same numbers every month and waited two days for them.
Switches to her CFO view, reads three written insights, and exports the board pack herself.
Same data model, different first screen — leaders never wade through someone else's metrics.
Every AI note names the cause and a next step, so it's a to-do list, not a commentary.
The layout prints to A4 landscape as-is; export is one click from the header.
15 — ERP · Manufacturing
Machine health for the plant manager. Each asset shows its OEE as a ring, the shift timeline shows exactly when each line ran, idled or stopped, and maintenance work orders sit beside the cause.
Heard about line 3 stopping at the end-of-shift meeting, hours after it happened.
Sees the stop on the shift timeline as it happens, with the work order already raised.
One shape per machine, comparable across the row; the number sits inside it.
The timeline shows when a stop happened, which is how a manager links it to a changeover or a shift handover.
Work orders reference the machine card that raised them, so nobody has to cross-reference IDs.
16 — ERP · Projects
An ERP rollout tracked inside the ERP. Phases, owners, progress and milestones on one timeline, with a today line so the steering committee sees what is late in the first second.
Built a status slide every Friday that was out of date by Monday.
Shares the live timeline with the steering group; late tasks show in red on their own.
The lighter fill shows how much of each task is done, so plan and reality share one line.
Only tasks behind the today line turn red. Everything else stays in its phase colour.
Steering-committee gates are their own shape, readable even in a black-and-white print.
17 — ERP · Customers
Everything the business knows about one customer, on one page: credit position, open invoices, order trend and every touchpoint from sales, support and finance in a single timeline.
Took a new order without knowing the customer was 32 days overdue on an invoice.
Sees credit use, open invoices and every touchpoint on one page before she says yes.
Credit use and slow payment sit next to the order button, before the next order is placed.
Emails, calls, tickets and reminders from every department, filterable but never split up.
"Invoices · 12" tells you whether a tab is worth opening before you open it.
A selection is shown here. The ERP & enterprise page has every concept, with its use case and the design decisions behind it.
The parts of enterprise software nobody screenshots for Dribbble — and the parts that decide whether a custom system gets adopted. Each tile below is a working pattern we reuse and adapt for bespoke builds: grids, permissions, rules, imports, audit trails and dispatch.
18 — Patterns · Complex software
Twelve patterns for data-heavy, multi-role, regulated software. Every tile is live — sort the grid, tick permissions, switch environments, open the command palette.
Trained new staff for weeks on a bespoke system nobody enjoyed using.
Uses grids, rules, imports and permissions that behave like the best SaaS tools — so training takes days.
| PO | Vendor ↕ | Amount ↕ | Status | Due ↕ | Owner |
|---|
| Module | View | Create | Approve | Delete |
|---|
A selection is shown here. The Complex & custom software page has every concept, with its use case and the design decisions behind it.
By industry
The same craft, tuned to the rules of each business. Every industry has its own page of designs.
Foundation
Every product we design sits on a system of tokens, components and patterns — delivered as a Figma library and as code-ready tokens — so the fiftieth screen is as consistent as the first and engineering builds from the same source.
Light and dark sets — use the theme switch above.
Aa Display 40
Page title Title 24
Section heading Heading 16
Body and table text Body 13
Column label Label 11
How we work
ERP redesigns fail when they start in Figma. Ours start on the shop floor and in the finance office, with the people who use the software eight hours a day.
Shadow users, map roles, audit the current screens and the spreadsheets people keep beside them.
Information architecture and task flows per role — what each person needs to see first.
Clickable Figma prototypes for the highest-traffic tasks, built on the design system from day one.
Moderated sessions with real users on real tasks; we iterate before a line of production code.
Annotated specs, tokens and component docs, plus design QA through the build.
FAQ
Straight answers to what people ask most before starting a design project. Can't find yours? Write to sales@advorize.com — every enquiry is answered within two working days.
We research how people use a product, map the flows they need, design the screens and the design system behind them, test them with real users, and hand engineers a specification they can build from. Advorize also builds the product, so the design is made to ship rather than to present.
It depends on the number of user roles, screens and states, and how much research is needed. A focused app or website is usually priced as a fixed-scope project; large ERP or SaaS products are often split into phases. We give a written estimate after a free discovery call, so you know the cost before any work starts.
A focused mobile app or website typically takes four to eight weeks from discovery to developer handoff. Complex SaaS, ERP and custom systems are usually designed module by module over two to four months, with the first module ready for development early.
Both. Advorize is a design and development studio, so the same team that designs the screens builds the web app, mobile app or internal system — and runs design QA during the build.
Fintech, travel and hospitality, communities, retail and quick commerce, manufacturing and logistics, plus healthcare, real estate, education and customer support. Each industry page on this site shows designs made for its specific rules.
Yes. We work with clients across India, the USA, Canada and the UAE, plan overlapping working hours with your team, and answer every enquiry within two working days.
Figma files with every screen and state, a clickable prototype, a design system with tokens and components, user-flow maps, and annotated specs for developers. You own all of it.
Yes. Redesigns start with an audit of the current product and interviews with the people who use it, so we fix what actually slows them down instead of only changing how it looks.
All designs on this page are by the Advorize design team. Company names, people and figures shown inside the screens are illustrative.