The internal tools nobody puts in a portfolio.
Client portals, admin consoles and operational dashboards. The software a team opens every morning deserves the same standard as the homepage, and usually gets nothing like it.
01 How it works
-
Design the one screen that matters
Most people log in to answer a single question. That answer goes first, with the depth available underneath rather than spread across six tabs.
-
Roles and a paper trail
Once more than one person uses a console, every action needs an owner and a timestamp. Auth, roles and audit logging are part of the build, not a later phase.
-
Fast on real data
Dense tables, long histories and slow connections are the normal case. The interface is built against that rather than against a seeded demo.
02 Straight answers
- Can you build on top of our existing API?
- Yes. Meridian was a calm interface designed over a legacy system that could not be replaced mid-flight.
- Do you handle authentication?
- Yes — sign-in, roles, permissions and session handling, wired to whatever identity provider you already use if there is one.
- Is this different from a marketing site?
- Completely. Marketing sites persuade once; internal tools get used every day. The standard is the same, the priorities are not.
03 Also relevant