The firm
A name rooted in strength and shaped by possibility.
Angulith brings together two roots: angulus, the Latin word for “angle” or “corner,” and lithos, the Greek word for “stone” or “rock.” Together they evoke an angular stone — a cornerstone.
A cornerstone establishes the position and direction of everything built around it. That idea captures the role we seek to play: a trusted technology partner that helps businesses establish solid foundations and turn ambition into working solutions.
The angle represents precision, thoughtful architecture, and the ability to approach challenges from a fresh perspective. The stone represents strength, dependability, and enduring value. Together they express our approach to technology: purposeful design supported by sound engineering.
That meaning carries through the work. Software gives ideas form. Cloud creates room to grow. Cybersecurity protects what matters. AI opens new possibilities. Each strengthens the foundation on which our clients move forward.
We work with mid-market operators in regulated or operationally dense industries — insurance, clinics, logistics, financial operations. They already have vendors. They need a partner who will sit in the constraint and still recognize the system a year later.
We are remote across North America. Engagements typically run two to four quarters to reach a system you can operate, then a thinner retain for the work after launch. We do not sell a transformation program. We sell a foundation you can hold accountable.
How we work
Frame, build, run, defend
Process is how we stay honest about what a finished foundation includes.
01
Frame
We start with constraints, not a vision deck. Who decides, what cannot move, what “done” means in production — not in a staging demo — and what the first slice is allowed to leave unfinished. If we cannot name those, we do not staff the work.
02
Build
A thin slice that is real. Interfaces written down. The people who will inherit the repository are in the reviews from the first month. We prefer an honest first production path to a complete design that has never been promoted.
03
Run
The same team stays with the system. Observability, rollback, and the dull work that makes the next change cheap are part of the engagement, not a later phase with a later vendor. If we cannot operate it, we have not finished building it.
04
Defend
The threat model sits beside the architecture. Identity, tenancy, and secrets are designed with the product. The incident path is walked once before anyone needs it. Security is not a binder we deliver at the end.
People
The bench you will actually meet
The people who set the work stay with it.
Mara Ellison
Partner, Delivery
Sets the engagement and stays with it. Previously led platform delivery at two multi-product companies that had outgrown their first architecture. Mara is still on the account after launch — not a new face at the review.
Kenji Sato
Principal, Platforms
Owns the path to production — environments, promotion, and the dashboards people actually trust. Kenji has spent a decade making releases boring on purpose. If a special-case pipeline is required, he will make someone write down why.
Imani Cole
Principal, Security
Threat models, identity, tenancy, and the incident path. Imani will not sign off on a control that only exists in a policy PDF. She sits on the same tickets as the feature work and is willing to be on the bridge when something fails.