01
Design systems
One language for type, spacing, color, components. Documented, themable, built to outlast a redesign.
Practice — three strata.
Practice · 01 · Edge
Edge.
Where the system meets the person. Design, interface, brand, mobile, web — the layer readers and users actually see. We work this stratum so the rest of the system reads as one thing, not a stack of decisions other people made.
What we do here
The work, named.
Edge work is what the rest of the engagement gets judged by. A perfect backend with a confused interface is still a confused product.
02
Interface design
Web and mobile screens, drawn carefully. Wireframe → high-fidelity → engineered handoff.
03
Brand identity
Logo, marks, voice, typography, photography direction. The visual side of the practice your audience meets first.
04
Mobile development
iOS and Android. Native where it matters, cross-platform where it doesn't. Shipped to the store, not stuck in TestFlight.
Deliverables
What you get.
- 01
Design system
Figma library, tokens, component docs. The reference your engineers and future designers both use.
Figma + Markdown - 02
Shipped interface
Working code in your repo, deployed, signed. Not a prototype.
Repo + deploy - 03
Brand kit
Logo, marks, type, color, voice guide. Everything a partner agency would need.
PDF + asset bundle - 04
Field note
A public write-up of how it was made, redacted as needed. Read
Public essay
Practice · 02 · Services
Services.
Where the work happens. APIs, integrations, databases, infrastructure — the engine room. The middle stratum, doing most of the lifting on every engagement, and the one most likely to be quiet on a good day.
What we do here
The work, named.
Services work is the bulk of the engagement. It's not glamorous; it's load-bearing. We pick boring technology on purpose and we keep things observable.
01
API design
REST or GraphQL — versioned, documented, signed at the boundary. One auth surface, not three.
02
System integrations
Payment, CRM, ERP, government services, third-party APIs. Make the quiet ones quiet; make the noisy ones legible.
03
Database design
Schemas, migrations, indexes. Designed to grow without breaking; designed to roll back when growth was wrong.
04
Infrastructure
Deployment, observability, cost discipline. Boring on purpose. Signed on every change.
Deliverables
What you get.
- 01
Architecture document
How the system fits together, drawn once, kept current. The map the team owns when we leave.
Markdown + diagrams - 02
Working backend
Deployed, monitored, documented, signed.
Repo + deploy - 03
Integration map
Every external system named — who reads, who writes, what fails when.
Markdown · 1 file - 04
Runbook
What to do when things break. Written in plain English; rehearsed before we leave.
Markdown
Practice · 03 · Data
Data.
Where intelligence lives. AI agents, language model integration, analytics, pipelines. The newest stratum and usually the riskiest. We treat AI as engineering, not as magic — and we say no to it more often than we say yes.
What we do here
The work, named.
Most AI conversations end with us recommending less AI than the client expected. The ones that go ahead are scoped tightly, evaluated honestly, and built to be turned off without breaking anything.
01
AI agents
Custom agents and copilots that fit inside your existing systems. Tools, not chatbots. Audited, evaluated, replaceable.
02
LLM integration
Add language models to existing flows. The right model for the job, controlled costs, measurable wins, clear failure modes.
03
Analytics
Dashboards the business will actually use. Numbers a non-engineer can trust without phoning home.
04
Data pipelines
Move data from where it lives to where decisions get made. Reliable, observable, signed, owned by your team after we leave.
Deliverables
What you get.
- 01
AI readiness report
Where AI fits in your stack, where it doesn't, what to do first. The deliverable for the standalone "AI Readiness" engagement shape.
PDF · 1 file - 02
Working agent
Deployed, evaluated, monitored, in production. With evals you can run before every release.
Repo + deploy - 03
Evaluation framework
Tests, metrics, regression detection. Specific to your domain, not generic LLM benchmarks.
Repo + dashboard - 04
Data documentation
Schemas, pipelines, lineage. The truth, written down, signed.
Markdown + diagrams
Start here
Working in the edge stratum?
One paragraph is enough. Tell us the shape of the system; we'll reply within two business days.