Foundation
Companies at inception — no brand, no product, no team.
Brand system, design system, landing page, deployment, copy.
~6 weeks, fixed scope.
Most design and development studios use AI to go faster. Gradient is structured differently: the studio is AI — every practitioner is an agent directed by trained judgment — and context about your brand, your product, and your decisions compounds across the entire engagement rather than resetting at each project boundary.
PHASE 0 — ENTITY HANDSHAKE
Gradient establishes its presence inside the client's environment as a separate entity with its own workspace.
PHASE 1 — CONTEXT ACQUISITION
The agents read what already exists — repos, decisions, in-progress work, language — before any human conversation.
PHASE 2 — SELF-SITUATION
The brand, engineering, and strategy agents resolve into a shared understanding. No briefing chain.
PHASE 3 — THE BEFORE-BRIEF
The first deliverable is a document. What was read, what is understood, what was noticed, what is needed.
PHASE 4 — ENGAGEMENT
Work happens in Gradient's workspace. Reviewed against Gradient's standard. Delivered to the client.
∇ — THE FIRST DELIVERABLE
This is how every Gradient engagement begins: a document that arrives before the first meeting. Not a questionnaire. Not a template to fill in. A document produced by Gradient — describing what the studio read about your situation, what it understood, and what it noticed that you may not have named yet.
This is how the studio works on its own projects. It is the method, not the marketing. When an external engagement begins, the Before-Brief is the first thing the client receives — and the first test of whether the studio actually knew what it claimed.
A complete record of what Gradient accessed before the first meeting — public presence, existing brand, product state, competitive positioning. Every source cited. Every confidence level marked.
The studio's read of your stated goal, your underlying objective, your timeline pressure, and your constraints. The first test: if the understanding is wrong, you correct it before a single hour of work begins.
One to three observations that the brief you would have written might not have included. Not recommendations — observations. What the external read surfaces that internal proximity obscures.
The Before-Brief closes with exactly one question. The most important thing Gradient could not determine from external reading. The answer upgrades everything that follows.
∇ — ENGAGEMENT MODELS
Companies at inception — no brand, no product, no team.
Brand system, design system, landing page, deployment, copy.
~6 weeks, fixed scope.
Companies with a working product whose design has drifted from the thesis.
Audit, repositioning, design system reconciliation, one shipped campaign or surface.
~3 months, defined scope.
Product companies that need an embedded design and engineering partner.
Ongoing capacity within Gradient's standard, monthly priorities, continuous shipping.
3-month minimum, subscription.
∇ — REFERENCE
Gradient was built using Gradient. The brand system, the design tokens, the landing pages, the component library, the copy, the CI/CD pipeline — all six were produced by the studio's own agents, directed by trained judgment, for Dana's own ventures.
We built the studio by using the studio to build the studio.
That sentence is the pitch, the proof, and the operating principle. The reference portfolio is Dana. The living proof is the session log.
Gradient takes on a small number of engagements each year.
If this is interesting, write to us.