The gap between design and engineering is where products break. We make it our discipline.
the pace is a design and technology studio. We build our own products — Parlance, Lexicon, and a growing portfolio — and we build for teams who care about getting the design-to-development handoff right.
Most studios pick a side. We live in the seam between the two, because that’s where intent gets lost, accessibility gets dropped, and good ideas drift into something nobody chose.
The name carries two meanings: a surname, and a belief — that building well is about the right pace, not the fastest one.
Why we exist, and where we’re going.
Mission
Why we exist
To close the gap between design and engineering — turning design intent into accessible, technical reality with clarity, structure, and care.
Vision
Where we’re going
A world where design and development speak one language, where accessibility is the default, and where the people building products are trusted because they’re honest — not because they claim to be flawless.
What we promise — and what we won’t.
We are problem-solvers, not perfection-sellers. We don’t promise you a flawless answer — because anyone who does is lying. We promise to solve the problem in front of us, honestly, with you, and to own the parts that are hard.
We’re rigorous about how we work, and honest about everything else. Honesty lowers the risk you feel; craft raises the quality you get. Trustworthy and excellent — most pick one.
Being human is the feature: we show our reasoning, name tradeoffs out loud, and say when something’s uncertain.
Where we stand.
For product teams who feel the gap between design and engineering, the pace is the design and technology studio that turns design intent into accessible, systematic, technical reality — because we work in the seam others ignore, and we’re honest about the work instead of selling perfection.
Category
A design & technology studio — not an agency, not a freelancer.
Who we’re for
Teams with designers and engineers, suffering handoff drift, inconsistent UI, and accessibility debt — especially regulated, multi-brand operators.
Why us
Twelve-plus years in design systems and regulated platforms; tools we built ourselves; standards we can prove, not preferences we defend.
The honest master craftsperson — who tells you the truth.
We are
We are not
How we sound.
Four principles guide every word.
Plain over clever
Clarity is the highest craft.
Honest over impressive
Name limits and tradeoffs; under-claim.
Precise over vague
Specifics, specs, numbers — “WCAG 2.2 AA,” not “accessible-ish.”
Human over corporate
A real voice, never a press release.
Do & don’t
Design and code that agree.
Synergistic, paradigm-shifting design solutions.
Here’s the tradeoff: faster to ship, harder to maintain. We’d choose maintainable.
We deliver flawless, pixel-perfect experiences, every time.
This audit found 14 issues. Three block release. Here’s the order to fix them.
Leveraging best-in-class methodologies to maximise impact.
Tone by context
| Context | Tone |
|---|---|
| Marketing | Confident, inviting. |
| Docs | Precise, neutral. |
| Errors & empty states | Calm and owning — never blame the user. |
| Proposals | Honest and specific. |
| Social | Generous and sharp. |
What we say.
Apps that move design and engineering as one.
We won’t sell you perfection. We’ll solve the problem, honestly, with craft.
Three pillars
At the gap
We work in the seam between design and engineering — where intent is lost and quality leaks.
Systems that scale
Tokens, contracts, and components built to hold up — not just to ship once.
Honest craft
Rigorous about the work, honest about everything else. Trustworthy and excellent.
Proof, not adjectives
- Parlance8 surfaces — one contract between design and code.
- Lexicon122 components, re-skinned in one pass.
- NettakerLive on the App Store.
Boilerplate
the pace is a design and technology studio working in the gap between design and engineering. We build our own products and partner with teams who care about getting the handoff right — with craft, accessibility, and honesty.
What we call things.
The brand — always lowercase, even at the start of a sentence.
Evocative single real words — Parlance, Lexicon, Auditor, Capital, Pacer. Title case, no sub-brand soup.
Our word for where a product lives — web, browser, VS Code, Xcode, Figma, MCP. Not “platforms,” not “integrations.”
How we look — from the live tokens.
Colour and type on this page resolve from the same tokens the whole site uses. Nothing here is typed in by hand, so it can never drift out of brand.
Logo
Clear space: keep at least the wordmark’s cap-height free on every side. Don’t stretch, recolour, rotate, or add effects — the mark ships in two forms, one for light surfaces and one for dark.
Colour
Each swatch is read from the running theme on load. Switch the site between light and dark and these values update themselves — the page documents the real palette, not a copy of it.
Surfaces
Ink
Accent
Semantic
Borders
Typography
Two voices, one system: the humanist sans for everything human-facing, the monospace for eyebrows, section numbers, token names, and code. Used together, the type says what we do.
The seam
Two thin rules meeting at a single rotated-square node — the gap between design and engineering, closed. We use it as a quiet divider, never as decoration.
How we think about building.
Standards over opinions
Every decision validates against real specifications — not preferences.
Shared language first
Design and development don’t naturally speak the same language. That’s the first thing to fix.
Craft over speed
Shipping right matters more than shipping fast. Precision, accessibility, maintainability.
Systems, not pages
Every component, token, and contract is built to scale — not just to ship.
The brand, applied.
Real components, real copy — the voice and the tokens in use.
Error state
We couldn’t save your changes.
The connection dropped before we finished — nothing was lost. Try again, and if it keeps happening, tell us and we’ll look into it.
Calm, owns it, points to the fix. No apology theatre, no blame.
Proposal opener
“Here’s what we’d do, what it costs, and the one thing we’d push back on before we start.”
Honest and specific from the first line.
Precise in method. Honest in promise.
Visit thepace.io