MKKA/ Studio
Process — Manifesto
MKKA engagements run on a four-chapter sequence — Discovery, Brand System, Motion & Product UI, Ship & Iterate. Every chapter has a fixed duration, a written deliverable list, and a published price. The median engagement is 11 weeks. The fastest path to a working brand system is 21 days. The contract is signed before week one.
§01 — The sequence
Each chapter runs back-to-back with a fixed week count and a written deliverable list. Most clients sign for all four; some start at Chapter 02 if discovery is already complete. No chapter begins without the previous chapter's deliverables being approved in writing.
A two-week audit of the product, the market, and the existing brand artifacts. We sit with the founding team, interview five to eight customers, and write a 40-page strategy document that anchors every downstream decision.
Deliverables
Client provides
Three weeks to a working identity: wordmark, type system, color, grid, photography direction, and the documentation needed to hand the system to an in-house team or a future agency. The first usable brand system ships on day 21 of the engagement.
Deliverables
Client provides
Four weeks to ship the first production UI — a Figma component library, motion principles, and ten to twenty designed and built screens. The motion language is produced in-house by our 3D and motion team; no subcontracted animation work, ever.
Deliverables
Client provides
Two weeks of QA on the live product, a public launch toolkit, and one round of post-launch iteration. The engagement ends with a written hand-off document and a 90-day standby window for ad-hoc questions.
Deliverables
Client provides
§02 — What you receive
Engagements are sold on artifacts, not on hours. The list below is the standard package; we trim or extend it in writing before the contract is signed. There is no hourly billing and no scope drift.
A 40-page strategy document in PDF and Figma; a stakeholder interview synthesis with verbatim quotes (anonymized on request); a competitive audit covering 12 to 18 companies with a side-by-side teardown of positioning, visual language, and product surface area; voice and tone principles written as rules with examples; an audience segmentation memo that names three to five jobs-to-be-done and the buyer personas behind them.
A wordmark and logo suite delivered as SVG, PDF, and PNG at the standard sizes — primary lockup, secondary lockup, monogram, favicon, and an app icon set. A type system with display, text, and monospace families, licensed for perpetual use, delivered with weights, italics, and a typesetting guide. Color tokens in JSON and Figma variables, paired with documented contrast pairs for AA and AAA. An 8pt grid and spacing scale documented as both CSS variables and Figma styles. A photography and illustration direction deck. A brand book, 80 to 120 pages, in PDF and as a living Figma file.
A motion principles document covering easing curves, durations, and choreography across micro, mid, and macro transitions. A Lottie and Rive asset library, with source files, exported at the resolutions and codecs the client's engineering team specifies. A Figma component library organized into tokens, primitives, and patterns — built with auto-layout, variants, and published as a team library. Ten to twenty designed and built screens, with engineering handoff annotations, redlines, and a recorded walkthrough for the engineering team.
A live-product QA report covering accessibility (WCAG 2.2 AA), cross-browser rendering, and load performance on the shipped screens. A launch toolkit with a press kit, social templates in Figma, and an email signature set. One full round of post-launch iteration against a written punch list. A hand-off document, 20 to 40 pages, written for the client's in-house team. A 90-day standby window during which the studio answers ad-hoc questions in writing within one business day.
§03 — Evidence
The numbers below are drawn from the studio's last 84 engagements, not from a marketing deck. They are the median outcome for a Series A–C SaaS or consumer-tech client on the four-chapter sequence.
From kickoff to a usable brand system — verified across the last 84 engagements.
From kickoff to the first production UI shipped to engineering.
Median engagement length across all four chapters combined.
Retention rate on multi-engagement clients — clients who return for a second project.
Average client rating across 63 published reviews on Clutch.
Net Promoter Score, maintained across the last two fiscal years.
§04 — Commercial model
Every engagement is sold against a written scope with a published price. There is no hourly billing. There are no change-order surprises. The rate card is sent on the scoping call.
Every contract names the chapters in scope, the deliverables per chapter, the week count, and the total fee. The fee does not change unless the client adds work in writing, in which case a fixed-price change order is signed before the new work begins.
The studio publishes its rate card on the scoping call. Rates are tiered by chapter and by team composition. The average project value across the last 84 engagements is $148,000; the median is $122,000.
Invoices are issued at 40% on signing, 40% at the midpoint of the engagement, and 20% on final delivery. Net-15 terms for clients on a purchase order. Wire, ACH, or card on file.
On final payment, the client owns the deliverables: source files, exported files, and a perpetual license to any third-party assets procured on the client's behalf. Work-for-hire is the default; alternative arrangements are written into the contract before signing.
§05 — Next step
The scoping call is a working session with one of the founders. We walk through your product, your market, and the chapters you need. You leave the call with a written scope, a week-by-week timeline, and the published rate card for your engagement. No deck, no follow-up sequence, no proposal document.