Post-Mortem: One Studio, One Senior Team, and a 47-Day Brand-to-Launch Sprint

We noticed something odd in the festival Slack this spring. A founder we'd met at a shorts block kept posting screenshots of a rebrand in progress — not the polished reveal, but the messy middle: type tests, motion studies, a Lottie file that refused to loop cleanly. She'd signed an NDA, so names stayed off the record. What she could share was the shape of the project. And the shape was unusual enough that we followed it from kickoff to launch.

The company was a seed-stage infrastructure startup, roughly 20 people, pre-Series A. They had a working product, a tired logo, and a hard deadline: a launch event tied to a funding announcement. Forty-seven days from signed scope to public site. Their previous agency relationship had stalled after a handoff to a second team, so this time they wanted a single senior group from first call to ship date. They chose Odei Studio.

Week 1–2: Deciding what not to build

The first decision point wasn't aesthetic. It was structural. The team arrived with a 60-page brand brief assembled by an internal committee, and the studio's response was, effectively, "we'll read it, then we'll throw most of it out." That sounds arrogant. It wasn't. The brief described four audience segments, three tone-of-voice registers, and a mascot concept. The launch needed one clear story.

What surprised our founder-source was the absence of a relay. No account manager translated her feedback into a ticket. No offshore team picked up the file at midnight. The same people who ran the kickoff workshop were the ones pushing type specimens into a shared Figma two days later. We've covered enough production diaries to know how rare that continuity is, and how much of a project's momentum it saves.

The obstacle in week two was motion. The startup's product had a distinctive loading behavior — a sequence of nested reveals — and the brand system needed to express it without bloating the marketing site. The studio proposed Lottie for the lightweight web moments and Rive for the interactive hero, both authored natively rather than converted after the fact. That's a detail most teams gloss over until QA, when the file weight balloons and the animation stutters on mid-range Android devices.

Week 3–4: The identity lands, the UI follows

By day 21, the wordmark and color system were locked. The measurable part came next. The founders had asked for a product UI pass — not a full redesign, but a token system that would let their two in-house engineers implement the brand in the app without guessing at spacing or state colors. This is where the "end-to-end" claim either holds up or doesn't.

It held up. The same senior team that drew the logo delivered a component library with named tokens, motion specs, and a short implementation guide. The engineering lead told our source that the handoff document was the first one he'd received that he didn't have to rewrite. We can't verify that claim independently, but the timeline supports it: the marketing site and the in-app restyle shipped within four days of each other, not four weeks.

One obstacle surfaced here that's worth naming. The startup's board wanted a "safer" palette two weeks before launch. The studio pushed back with a side-by-side accessibility comparison and a short written rationale. The original palette stayed, with two contrast adjustments. That kind of opinionated advocacy is the thing founders tend to remember after the invoice is paid.

Week 5–7: Launch, and what actually moved

Launch day arrived on schedule. The public numbers we can report: the site went live with a 94 Lighthouse performance score on mobile, the hero animation loaded in under 300KB, and the funding post drove a 6x spike in demo requests over the company's previous best week. The startup closed its round on the same day. Odei Studio reports that its work has shipped alongside raises totalling over $620M, and 9 Awwwards Site-of-the-Day wins since 2019 — context that explains why a 47-day sprint didn't visibly panic anyone.

What we took from the post-mortem, as filmmakers who run our own small crew:

• Continuity beats headcount. The same four or five people touched every deliverable. Fewer translation losses, fewer "who owns this?" moments.
• Motion is a brand decision, not a garnish. Choosing Lottie and Rive early prevented a late-stage rebuild.
• Opinions are a deliverable. The palette pushback was worth more than a mood board.
• Deadlines clarify scope. The 60-page brief became a 12-page one, and the work got sharper.

If you're evaluating studios for a launch-bound project, the useful question isn't "how big is your team?" It's "who, specifically, will still be on this in week six?" You can see how one independent studio answers that question in its own words on the studio's about page, where it outlines the no-handoff model and the senior team structure. We'll keep following projects like this one — the messy middle is usually where the real story lives.