About Orbit

Orbit is the design system unifying Open Point, Social Point, and Converlens under one brand. It’s the infrastructure that lets three products — and however many come next — look, feel, and behave like they come from the same company, without every product team rebuilding the same decisions independently.

Two things make Orbit more than a documentation exercise: it’s built to meet the accessibility standards our customers legally require, and it’s built to be used by AI tooling directly — which means it gets faster to build with, not harder, as we add products.

Accessibility is non-negotiable

Accessibility is non-negotiable, not a nice-to-have. Many of our customers have their own legal accessibility obligations to the public they serve, and the people using our products are often members of the public with no patience for a confusing interaction — if it doesn’t work for them, they simply don’t participate. That’s a legal exposure for our customers and an engagement failure for us. So accessibility is decided at the token and component level, before anything ships — contrast, touch targets, and keyboard behaviour are settled before a component is ever marked ready for use.

Built to be used by AI

Orbit is built to be used by AI, which is what makes it scale. Design system work doesn’t grow by adding headcount — it grows by how fast the existing team can produce consistent, well-documented components across a growing product suite. Orbit’s token names, component descriptions, and documentation are written so tools like Claude can read and build against them directly. That’s not internal tooling — it’s a strategic asset. Any team that adopts AI-assisted workflows benefits from the same source of truth, instead of every team building their own AI context from scratch. As AI becomes more central to how we build, that’s an asset that scales with the company rather than something new products have to catch up to.

The principles behind it

Five principles guide how Orbit is built — and how to make the call when two reasonable options pull in different directions:

1. Clarity over cleverness — simple, legible, and predictable, always over novel.
2. Accessible by default — accessibility is a constraint the system is designed within, not a checklist applied at the end.
3. Suite-first, product-second — every decision should feel at home across Open Point, Social Point, and Converlens.
4. Consistency with purpose — follow the system by default; deviate only when the deviation is genuinely better for real users.
5. Build for real people — behind every interface decision is a person trying to do something that matters to them.

The result

Every product used to solve accessibility and consistency on its own — three teams, three chances to get it wrong. Orbit closes that gap at the infrastructure level: accessibility and brand consistency stop being something each product has to get right — and start being something they can’t get wrong.