skip to content

strategy · experience · engineering · release

make the hard part feel clear.

the work starts where people hesitate, get lost, or stop trusting the product, then carries the smallest honest fix across UX, iOS, web, AWS, accessibility, QA, and release.

one accountable partner from the first uncomfortable question to the production evidence.

start from your reality

you do not need to know what to ask for.

choose the state you are in. this stays in your browser, changes nothing outside this page, and points to the smallest honest place to begin.

what needs to become clear?

your smallest honest start

name the real decision.

find the constraint, choose the smallest useful next move, and get permission not to build the wrong thing.

see the Signal boundary

proof you can touch

the work is already alive.

these products ship under uxuiai.org, the product organization. they are evidence of the work, never client claims.

proof for · decide what matters

the proof starts with what the system refuses to invent.

the live Guide declines unsupported questions, names only approved products, and preserves a typed fallback.

see the Signal boundary
  • AirBridge Health

    health data moved between platforms with the sensitive path kept on the device, and shipped through App Review.

  • Cinder

    a note encrypted in the browser, readable once, with a page that names what it cannot protect you from.

  • undertext

    a dense multilingual reading system that survives text enlargement and a screen reader.

  • Holy Instant

    a grounded in-app companion with no account, and accessibility treated as part of the build.

take the thinking with you

free field notes.

no email gate, tracking pixel, or viewer account. open the source material here, or keep a copy for the room where the hard decision happens.

architecture note · June 2026 snapshot

One Core, Two Faces

a shareable look at how undertext 2.0 kept one content contract coherent across its web core, native shell, Apple Watch, and Apple TV.

PDF · 5 pages · 334 KB

the floor, not the add-on

two promises hold every decision.

private, always.

no analytics theater, hidden profiling, or data collected because it might become useful. what the host logs by default is named on the privacy boundary rather than left out of it. if something must leave the device, the person sees the boundary before it happens.

open to everyone.

screen readers, text enlargement, reduced motion, keyboard use, touch targets, and measured contrast belong in the first build, not the remediation budget.

one promise scale · eleven honest containers

choose the promise before the machinery.

start at $2K for one decision or keep moving through product, platform, and enterprise partnership. you control the scale; every rung stays an alternative, not a cumulative invoice.

sheet 00 1 working day

Signal

$2K

a straight answer on whether this is worth building at all, and what it would actually take.

  • a working session on the surface in question
  • a written diagnosis with the real constraints named
  • a scoped recommendation, including "do not build this"

where it stops

no build, no prototype, no design files. this rung buys a decision, not an artifact.

sheet 01 5 business days

Guide Blueprint

$4K

you know exactly what to build, what it costs, and what it must never say.

  • a decision-ready guide definition
  • a grounded content model with a signed claim matrix
  • a privacy and data-flow map
  • an interaction prototype
  • an implementation estimate

where it stops

no production integration, and no infrastructure purchased.

sheet 02 10 business days

Guide Prototype

$8K

the behavior is real and testable on your own approved content, before production is involved.

  • a working branded prototype on client-approved content
  • typed conversation with linked answers
  • unsupported-question handling you can try to break
  • responsive and accessibility QA on the changed surface
  • a private review URL and an acceptance script

where it stops

no production deployment, and no live model credentials.

sheet 03 15–20 business days

Living Guide Launch

$16K

it is live on one of your properties, on infrastructure you own, with the evidence to prove what it does.

  • production integration on one existing web property
  • a client-owned model and API boundary
  • streaming with a buffered recovery path
  • optional disclosed voice input, only if it passes review
  • privacy and accessibility evidence, and a 14-day stabilization window

where it stops

one property, one truth source, one deployment lane. ongoing content operations become a separate agreement.

start at any rung. if you step up within 30 days, the fee you already paid credits the next one, as long as the approved scope and source material have not materially changed.

no qualification theater · your context comes with you

bring the decision.

you do not need a brief, a budget performance, or the right vocabulary. the form already carries your selected path and promise scale. share what feels hard; a person replies in plain text, usually within one business day.

your path decide what matters

change

promise in view Signal · $2K

change
or email matt@ux-ui.ai

this opens your mail app. nothing is sent to this site, stored, tracked, or scored; you see the whole message before it leaves.