Proof of capability
A decade of building design systems, accessible products, and the tooling that keeps design and engineering in step.
Designed, built,
and translated across
Ecosystem
Design tooling, health, and finance — four product families over a shared foundation. The map lays out where each product sits, what it’s built on, and what it works with.
A structured map of the studio. the pace is the origin. Four product families sit in lanes — design tooling (Parlance and its surfaces, Lexicon, Theme Creator, Tailwind Translator), health and fitness (Pacer and Pacer Coach), finance (Nettaker and Capital), and studio consulting. The Lexicon design system and the studio’s shared standards form the foundation beneath them. Every product is listed, grouped by family, in the directory below.
Every product, by family
Design tooling
The connected suite — one shared design system, one set of standards.
ParlanceBetaThe contract layer between design and code, verified to W3C standards.Built on LexiconAuditorIn developmentParlance as a native browser — the same engine, a new surface.Part of Parlance
LexiconBetaThe design system every tool here is built on — 122 components.The shared foundation
Theme CreatorLiveRe-skin the entire Lexicon library to a theme in one pass.Built on Lexicon
Tailwind TranslatorLiveTurn Figma variables into Tailwind classes and rem values.Maps to LexiconHealth & fitness
Consumer apps for training, nutrition, and coaching.
Finance
Tools for tracking money — take-home pay and accounts.
Studio
Consulting that draws on the same expertise.
Selected work
A few of the harder problems — the shape of each one, what got built, and why the approach differs. Every demonstration is drawn from the real system, not a stock mockup.
01 — Design-to-development contracts
Component specs scatter across six tools and agree on nothing. Tokens vanish somewhere between the Figma file and the pull request.
Parlance is a formal contract layer — components, tokens, and interactions verified against W3C standards — so design and engineering work from one source both sides can check.
Why it’s different — Standards over opinions. Every contract validates against real specifications, not a senior designer’s preference.
02 — Multi-brand design systems
Every brand ends up with its own library. Every re-skin is a manual slog, and two themes drift apart the moment they diverge.
Lexicon is a 122-component system with a Theme Creator that re-skins the whole library in one pass — 60+ variable values across light and dark, each checked to WCAG AA.
Why it’s different — Deterministic, not generative. One definition, every output: Figma, CSS, and Tailwind stay in lockstep.
03 — A product, designed as a pair
Athletes track in one app; coaches plan in another. The two never quite line up, so the plan and the day drift apart.
Pacer for the athlete and Pacer Coach for the trainer — two surfaces on one synced system, so the plan a coach sets lands exactly where the athlete logs meals and training.
Why it’s different — Designed as a pair from a shared foundation — not two apps stitched together after launch.
04 — Shipped and live
Gross-to-take-home is a black box. Comparing an offer, a raise, or a contract honestly means untangling tax you can’t see.
Nettaker turns any gross figure into the number that actually lands in your account — income tax and contributions resolved in seconds.
Why it’s different — One job, done precisely. Clear enough to compare two offers before the meeting ends.
Services
Fixed-scope reviews, embedded consultation, or end-to-end product work — scoped, priced, and delivered by the person doing the work. Open any service to compare.
Review & audit
Fixed-scope, delivered as a document you can act on.
Embedded & ongoing
Senior thinking inside your team, week by week.
Build & operations
End-to-end product work and the systems behind it.
Method
One senior practitioner, one throughline — from understanding the problem to handing over a system a team can own.
Map the product, the team, and exactly where design and code fall out of step.
Agree the shared language — the tokens, components, and standards both sides can verify against.
Turn decisions into a system: token architecture, component contracts, and documentation.
Design and build the real thing — accessible, production-ready, with no handoff gap.
Check every decision against real specifications — WCAG, W3C, and the contract itself.
Hand it over so it lasts: docs, rituals, and a team that can carry it without me.
Founder-led
the pace is Jonathan Pace — a design systems architect with more than a decade across iGaming, fintech, SaaS, e-commerce, and telecommunications. Founder-led isn’t a limitation here; it’s the reason the work stays coherent.
No account managers, no agency layers. You talk to the person doing the work.
The person who scopes the work designs it, builds it, and hands it over.
Not slideware — a connected set of original products, tested in production.
Design-to-code and accessibility as a specialism, not an add-on.
A design system, an accessibility strategy, or a product that has to make something complicated feel simple — I’d like to hear about it.
