Design system engineering
Tokens, primitives, and documentation your team will actually use. Built on your stack, tested in CI, versioned like the product it serves.
Read the CMS case study →Dmitrii Klein — Creative Front-End Engineer
Design systems, performance rescues, and accessibility work for product teams who are tired of shipping slow. Fourteen years, forty-one launches, zero abandoned handovers.
You will hear back within 4 business hours. A real reply from a real person, or a referral to someone better suited. Average first response across the last 90 days: 1h 47m.
41
Products shipped
0.9s
Median LCP delivered
100%
WCAG AA on handover
14 yrs
Doing only this
01 // What I do
Three things, done properly
No sprawling agency menu. If your problem is not on this list I will tell you so in the first reply and point you somewhere useful.
Performance rescue
A two-week teardown of what is making your app slow, followed by the fixes. Measured against real field data, not a lab score you screenshot once.
Read the Neon Ledger case study →Accessibility remediation
Audit, fix, and a regression suite so it stays fixed. Keyboard, screen reader, and cognitive load — not just colour contrast.
Read the Orbital case study →02 // How it goes
Four phases, no mystery
The panel above tracks the phase you are reading. Scroll on.
PHASE 01 — DISCOVER
Find the real problem first
A week of analytics, session replays, support tickets and four user interviews. Most teams arrive certain they need a redesign; roughly half of them actually need three fixes and a decision.
Deliverable: a written findings memo and a ranked problem list.
PHASE 02 — ARCHITECT
Draw the system before building it
Component contracts, token scales, state diagrams, and the accessibility requirements each piece must satisfy. Everything is agreed on paper while changing it is still cheap.
Deliverable: an interactive spec and a dated milestone plan.
PHASE 03 — BUILD
Ship in slices, weekly
A working deploy every Friday from week one. Performance and accessibility budgets run in CI, so a regression fails the build rather than reaching your users and being discovered a quarter later.
Deliverable: a staging URL you can poke at, updated weekly.
PHASE 04 — SHIP
Hand over so it outlives me
Documentation, a recorded architecture walkthrough, and a pairing week with your team. Thirty days of no-cost bug support after launch. You own every line of it.
Deliverable: production launch and a handover pack.
03 // Selected work
Three case studies
Each one covers the brief, the constraint that made it hard, what shipped, and the numbers afterwards. See all case studies.
A fintech dashboard that took 6.2 seconds to become usable. Now it takes 0.8.
A logistics console that failed 61 WCAG checks and locked out its own dispatchers.
Four product teams, four different buttons. One design system later, none.
04 // What clients say
Reviews
Collected after handover, published verbatim. Ask for references and I will connect you directly with any of them.
★★★★★
Our dashboard went from the thing customers complained about to the thing they mention in sales calls. Dmitrii found four render-blocking scripts we had all stopped seeing.
Marta OyelaranVP Engineering, Neon Ledger
★★★★★
The audit alone was worth the fee. Two of our dispatchers use screen readers and had been quietly working around the console for a year. That is fixed now, and the tests keep it fixed.
Dev RamaswamyHead of Operations, Orbital Freight
★★★★★
Handover is where contractors usually vanish. We got documentation, a recorded walkthrough, and a week of pairing. Six months on, my team is still shipping with the system unaided.
Junie HalvorsenDirector of Product, Paperclip
05 // Questions
Frequently asked
How quickly will I hear back after I get in touch?
Within 4 business hours, and always inside one business day. Every enquiry gets a real reply from me — never an autoresponder. If the fit is wrong you get a referral instead of silence. See the contact page for hours and timezone.
What does a typical engagement cost?
Most projects land between $12,000 and $45,000 depending on scope. Work is quoted as a fixed price per phase after a paid discovery sprint, so there are no hourly surprises and you can stop cleanly between phases.
How long does a project take?
A design system foundation takes 4–6 weeks. A performance rescue takes 2–3 weeks. A full product front-end runs 8–14 weeks. You get a dated milestone plan before anyone writes code — see the four phases above.
Do you work with teams outside Austin?
Yes. About two-thirds of clients are remote, across North America and Europe. Austin and central Texas clients can add on-site workshops and pairing days at no travel cost.
What happens to the code after launch?
You own all of it, outright, from day one — repositories, design files, and documentation. Every engagement ends with a handover pack and 30 days of no-cost bug support. More on that in how I work.
06 // Next step
Tell me what is broken
Two paragraphs is plenty. You will have a reply, and a straight answer about whether I am the right person, within 4 business hours.