A design and engineering practice
A founder writes to us because something in the company is stuck, and every vendor they've talked to pitches a category before they've been read. So we read what's public first — your product, your site, your docs — and the first thing you hear back from us is a reply from a person, not a pitch.
One real engagement, redacted and counted rather than described. No client name, no promised dates — the two numbers below are read straight off the ledger.
[SOURCE: specimen — src/data/ledger-specimen.ts]
A company URL and one sentence about what is stuck. If there is something else you want us to read, send that too.
Everything public. Your product, your site, your documentation, your public code. We do not ask for access to anything private at this stage.
A reply from a person who read what you sent — not a routing system, and not a pitch.
If there is work, it gets scoped once we understand it. If there is not, you have lost nothing — the demo is free.
We read every request — three business days, either way.
A human reads every reply before it leaves, reviews every deliverable, and signs it. The name on the work is the name accountable for it.
This is stated plainly because it is how the work gets done, and because it is the reason we can read a company properly before the first meeting rather than after the third.
Not four packages to compare — four different places a founder can be standing, and what changes once we're in it together. Which one you're in is usually obvious once we understand the work.
You have a company and a direction and nothing built. Foundation takes it from that to something real in the world: the product decisions, the system it runs on, and the interface people actually touch.
A Foundation engagement ends with money able to move.
If the asset belongs on-chain, the rails include tokenizing it — settlement infrastructure is part of the practice, not a referral.
Something exists and it is not good enough, and you know it. Elevate is the pass that finds where the gap actually is — usually not where it looks like it is — and closes it.
We work inside your team on your cadence, as design and engineering capacity that already knows the context instead of spending a quarter acquiring it.
Everything Dana runs on — the product, the design system, the delivery discipline — integrated into your organization, customized to your environment, by the people who built it. You could build this in-house. An Install engagement is for the org that wants the full-house result from day one, with its own team running it at handoff. Starts, like everything, with a demo.
Engagements are priced per engagement, and scoped once we understand the work. We do not quote before then.
Foundation and Elevate engagements are typically sized for a small team's quarter, not an enterprise budget.
We read every request — three business days, either way.