Selected work & directions

Proof in the product. Ideas in the open.

Explore the N9 Agent Builder and a set of interface concepts that show the kinds of software we can shape. Every card is labeled so a design direction is never mistaken for a shipped client case study.

How to read this page: “Live N9 product” links to something you can use today. “Interface concept” is a visual product direction, not a client endorsement or delivered project.

Product gallery

From AI creation to connected operations.

Each direction begins with a workflow and the people who need it, then becomes an interface, backend and set of connected decisions.

Live N9 product

N9 Agent Builder

N9’s active agent-building experience turns a brief into an agent identity, instructions and working logic for review.

AI agentsProduct UI
Open the builder
StoreMerchant interface concept
Interface concept

StoreMerchant

A commerce operations direction connecting product catalog, orders, stock and fulfillment in one workspace.

CommerceInventory
Explore the solution
OneDashboard interface concept
Interface concept

OneDashboard

An executive overview concept for revenue, operations and exceptions with a clearer path from metric to action.

AnalyticsDashboards
Explore web applications
CRM & Pipeline interface concept
Interface concept

CRM & Pipeline

A customer relationship workspace concept with pipeline stages, follow-ups and activity context.

CRMSales
Explore CRM solutions
Mobile Operations interface concept
Interface concept

Mobile Operations

A mobile product direction for live work, approvals and operational visibility away from the desk.

iOSMobile
Explore mobile apps
Property Tools interface concept
Interface concept

Property Tools

A resident and property experience direction spanning service, documents, neighborhood tools and future spatial views.

PropertyResident app
Explore real estate
What makes a case study real

The work is more than a screenshot.

When a client project is approved for publication, we will show the original challenge, scope, constraints, shipped product and outcomes we can substantiate.

  1. 01What the team needed to change.
  2. 02What was actually designed and built.
  3. 03What systems and workflows were connected.
  4. 04What happened after launch, with permission to share it.

Have your own version in mind?

Tell us about the workflow and the people it needs to serve. We can shape a focused first release.

Start a project