Acies.ai
BI dashboard for the payments industry. Founding designer; built the platform from the ground up.

Acies.ai is a BI platform built for the payments industry. As founding designer I shaped the product from a blank canvas into a shipping platform.
- 2020–2022
- Founding Designer
- Acies.ai
- Founder + engineering
Problem
Productized through a payment processor
Acies.ai reached the market through a parent payment processor (Freedompay), serving its external customers rather than launching as a standalone SaaS. That distribution model shaped scope, branding, and how the product had to fit into an existing payments stack.

Research and feature scoping
Before any UI, the team aligned on what BI for payments actually had to do. I worked alongside the CTO and engineers to document feature scope, persona needs, and the gaps in tools customers were already using.

Reach from store-level to enterprise
The same product had to answer questions for a single-store operator and a regional analyst comparing portfolios. Holding that range without splintering into two products was the central design constraint.
Approach
Information architecture and KPI spec
I mapped IA, sketched navigation models, and spec'd every KPI — definition, source, and how it composed with others — before designing screens. That work made later decisions repeatable instead of one-off.

Design system as foundation
Tokens, components, and charting primitives lived in a system from day one. It kept dashboards, builders, and admin surfaces visually and behaviorally consistent as the product grew.

Iteration history
Earlier explorations — shown here as iteration history, not the shipped product — stress-tested density, navigation, and the dashboard-building mental model before we converged on the final direction.

Custom report builder, responsive
The builder let non-analysts assemble views from segments, filters, drilldowns, predictions, and multiple chart types — and it had to behave on a laptop and a tablet without splitting into separate experiences.

What I designed end to end
- Dashboards and dashboard building
- Segmentation, filters, and drilldowns
- Predictions, insights, and summaries
- Multiple visualization types tuned for payment data
- Imports, exports, and scheduled reports
- Loyalty workflows
- Settings, admin, and account surfaces
Outcome
Flagship sales dashboard
The default surface most users land on — KPIs, trend lines, comparisons — engineered to make high-cardinality payment data glanceable while keeping a drilldown one click away.

Reports that travel
Saved views, imports/exports, and summaries — built so an analyst can author once and operations teams can consume on their own cadence.

Visualization breadth
Bars, lines, distributions, geo, and composite views — tuned for the long tails, seasonal swings, and sparse segments payment data actually produces.
