Services / 004
What we make.
Strategy, brand, and engineering — under one roof, by one team.
Strategy
We learn the business, the audience, the constraints.
The first two weeks are spent closer to the business than to the work. We sit with founders, CMOs, and product leads to pull apart the positioning, the sales objections, the onboarding metrics, the three customers the team actually wants more of.
Deliverables are concrete: a positioning one-pager the team can defend in a board meeting, an information architecture that survives contact with a product roadmap, a content model engineering can build against, and a scope document that names the things we are not doing.
We say no when the brief is really three briefs, when a rebrand is being asked to fix a product problem, or when the timeline is shorter than the thinking it requires. A short strategy engagement that prevents a six-month rebuild is worth more than the hours it costs.
- Discovery
- Positioning
- Information architecture
- Content modeling
Typical: 1–3 weeks
Brand
Identity systems, type, motion language, design tokens.
Brand here means a system that survives the team that shipped it. Wordmark, type specimen, motion language, color role assignments, grid, voice — every piece built to be handed to an internal designer six months from now without a phone call.
We draw identity and design tokens in the same pass. The palette is not a mood-board attachment to the logo; it is a set of CSS variables the product team consumes directly. The motion principles are not a deck slide; they are timing curves exported into the codebase.
The output is a guidelines document shorter than the ones you have seen, plus the actual files — tokens, components, templates — used to ship the first marketing surface. Everything else inherits from there.
- Identity
- Type systems
- Motion language
- Design tokens
Typical: 3–6 weeks
Web & App
Frontend engineering, design-token-driven UI, accessibility, performance.
We engineer the marketing site, the authenticated app shell, or both, on Next.js with a strict type surface and a performance budget set before the first component is written. The same team that drew the design writes the code, so the fidelity you approved is the fidelity that ships.
The stack is deliberate. Design tokens in CSS, components vendored where possible, server components by default, motion scoped to moments rather than sprinkled everywhere. Accessibility is covered during build — focus states, keyboard parity, reduced-motion variants — not in a post-launch audit.
Each release ships behind a preview URL, a Lighthouse run, and a short written note on what changed and why. The engagement closes with a codebase the internal team can maintain and extend without an ongoing retainer, unless you want one.
- Next.js
- React
- Design systems
- Accessibility
- Performance
Typical: 4–12 weeks
3D & Motion
WebGL, R3F, scroll choreography, custom shaders.
Used sparingly. One signature moment per site, engineered to the same standard as the rest of the page — not a separate WebGL island with its own accessibility story.
We build with React Three Fiber and Lenis-driven scroll choreography, with a custom shader or two where the concept needs one. Frame-rate budgets are set per device class; we test on a real mid-range Android, not just a Mac.
Everything degrades. Reduced-motion preferences kill the animation. Low-end devices get a static poster frame. The moment reads as a taste signal on a capable device and simply does not appear on one that cannot afford it.
- WebGL
- R3F
- Shaders
- GSAP
- Lenis
Typical: scoped into the web engagement