# Ark CX

*Create and maintain a customer experience that is genuinely your own.*

Ark CX is your own design system, built to work across whatever you already run. We ship it as components into your own stack, connect them to your core, and keep the system current with your team.

## Most design systems arrive with a platform. This one works with what you already have.

Ark CX is your own design system for the customer experience. Your brand, your
patterns and your journeys, held in one place and shipped as the components your
teams actually build with.

It works with the platforms you already run. Your core, your origination and
your app can come from different vendors, and the experience still holds
together across all of them. We build it with your team and keep it current, so
it stays yours as your products and your brand change.

## The challenge

Every bank and lender has a brand. Very few have one place where the brand and the screens agree.


- **Your screens came from different places**: The app, the website, onboarding and servicing were built at different times by different teams. Each one reads the brand slightly differently, and your customers see all of it.
- **Design systems stop at the screen**: Component libraries and token tools describe the interface. They do not reach your core, your identity checks or your decisioning, so somebody still assembles the journey by hand behind them.
- **The good ones arrive with a platform**: You can buy a serious design system today. The price of entry is moving your bank onto the vendor that owns it, and what you get is shared with everyone else on the same system. If you are not replatforming, there is nothing on the shelf for you.

## How we help

Ark CX gives you one definition of your experience, then keeps it true everywhere it ships.


- **Decide it once**: The judgment happens once, at the definition. Change it there and every screen built on it follows, including the ones you build next year.
- **Design to code, on your stack**: Most design-to-code tools emit for their own runtime, so what you get only works while you keep paying for the tool that made it. Others never emit product code at all and hand your engineers a specification to reinterpret. Ark CX ships standard components into your codebase, on your framework, deployed by your pipeline.
- **Works with what you already run**: Your core, your origination, your CMS and your app may come from four different vendors. Ark CX sits across all of them, so the experience holds together whether or not the systems underneath ever agree. Swap a vendor later and the experience stays where it is.
- **Connected to the systems that decide**: This is the part a design tool cannot do. Digizoo builds regulated integrations for a living, so a journey reaches the systems that make the decision instead of stopping at the screen in front of them.
- **Built for you, not shared**: You are not one tenant inside a system serving other banks, so your experience is not a theme on a shared skeleton. You own the asset and set its direction. We keep it running and keep it current, so owning it does not mean standing up a team to hold it together.
- **More than one brand, kept apart**: Run a second brand, a white label or an acquisition and you normally maintain a second set of everything. Here the brands share the system and keep their own token sets, so each one looks and behaves like itself while your team maintains one set of components. Adding the next brand is a set of values, not another build.

## Three ways to get a consistent customer experience.

Design system tooling documents the interface and stops there. A platform brings its own system, and you get it by moving your bank onto the platform. Ark CX is the third way.

|   | Design system tooling | A platform that brings its own | Ark CX |
| --- | --- | --- | --- |
| One definition across every channel | Yes | Yes | Yes |
| Ships production components, not a specification | No | Yes | Yes |
| Connects to your core, identity and decisioning | No | Yes | Yes |
| No in-house team needed to keep it running | No | Yes | Yes |
| No core migration to get started | Yes | No | Yes |
| Works across the platforms you already run | No | No | Yes |
| Yours alone, not shared with other banks | No | No | Yes |
| The code runs on your own stack | No | No | Yes |

## How we work

Ark CX is delivered as a service. We build the capability with your team instead of handing over a system for you to staff.


1. **Define it with you**: We start with your brand and the surfaces you already run, and turn them into one definition your teams agree on.
2. **Ship it into production**: The definition becomes components in your own codebase, connected to the systems behind them whichever vendors those are. We prove it on one part of the experience before it goes everywhere.
3. **Keep it current**: As your products, policy and brand change, the system changes with them. New brands, channels and products join the same system rather than starting again.

## FAQ

**Some platforms come with their own design system. Why not take that?**

If you are moving your whole bank onto one platform, that is a real option and often a good one. It costs you a migration, and the system you get is shared with every other bank on it. Ark CX suits you if you are not replatforming, or if you want the experience to be yours rather than a theme on somebody else's system.


**We run more than one brand. Does that work?**

Yes. Each brand carries its own token set on the same system, so they look and behave like separate brands to your customers while your team maintains one set of components. A white label, an acquired brand or a broker-facing site can each stay distinct without a second build.


**Will it work with the vendors we already use?**

Yes, and that is the point. Your core, origination, CMS and app can each come from a different vendor. Ark CX sits across them, so replacing one of them later does not cost you the experience.


**How does Ark CX relate to Ark?**

Ark is the banking foundation and the integration underneath. Ark CX is the design system on top of it, covering everything your customers meet. You can run Ark CX on the core you already have.


**Is this a design system tool?**

No. Tools describe an interface and stop there. Ark CX takes the design through to code, ships it into production on your own stack, and connects it to your core, identity and decisioning, which is the part that decides whether a journey works.


**AI tools generate screens from designs now. Why do we need this?**

Generating a screen is cheap, and getting cheaper. Deciding what the screen should be, holding that decision across every channel, and connecting it to a regulated back end is the work. That is what Ark CX governs.


**Who owns it?**

You do. The system is bespoke to you, the IP is yours, and you set its direction. We run it and keep it current as a service, so owning it does not mean hiring a team to maintain it.

## Want your brand on every screen?

Talk to the Digizoo team through the contact form: https://www.digizoo.com.au/#contact