Today I’m launching the Design Foundation Sprint: a four-week, fixed-price engagement from Raft Design that gives funded startups a real brand and product foundation, built and led directly by me, before you’re ready to hire a full-time design leader. It comes in two scopes, Core and Full System, both fixed price, both done in a month.
I’ve watched the same thing happen to five different startups over the past fifteen years, under five different sets of circumstances. A company raises money. Engineering starts shipping. And somewhere in that acceleration, the product, the brand, and the site quietly stop keeping up with the company the founders are actually becoming.
Nobody plans for this gap. It’s not a mistake. It’s just what happens when the fastest-moving part of a company outruns the slowest-moving part, and design is almost always the slowest-moving part, because it’s the one function that doesn’t scale by adding more engineers.
I started noticing the pattern long before I had language for it. Before Adobe, before Walmart, I ran the creative work behind a run of startups: Health Catalyst, which went on to IPO on Nasdaq. Cloud Cruiser, acquired by HPE. OrderDynamics, acquired by Tecsys. Leadspace, still shipping today. Protagonist, still running the exact design I built for them a decade ago, while they’ve grown into a client list that now includes Microsoft and the U.S. government. I didn’t build any of those outcomes. But watching early design decisions hold up, or not, across a decade taught me something a single project never could: the work that survives isn’t the work built to impress at launch. It’s the work built to move with the company as it changes.
That’s the whole thesis behind Raft, and it’s the whole thesis behind the Design Foundation Sprint.
Why now, specifically
AI changed the actual water underneath this problem, not just the tools sitting on top of it. Engineering teams can now ship product surface area at a pace that would have taken a team three times the size five years ago. That’s not a hypothetical, it’s just what a funded startup’s roadmap looks like right now. Design hasn’t gotten three times faster in the same way, and the gap that used to open slowly, over a year or two, now opens in a matter of months.
I don’t think the answer is throwing more AI at the brand and product side to match engineering’s pace. I think the answer is judgment, applied with real speed, at the exact moment a company needs it most: after the round closes, before there’s budget or conviction to hire a full-time design leader.
Why brand and product, not one or the other
Most of the sprint-shop competitors I researched before building this pick one lane. A brand studio ships an identity and hands you a PDF. A product studio ships screens with no coherent identity behind them. Neither solves the actual problem, because you can’t design a product interface that expresses a brand that doesn’t exist yet, and you can’t finish a brand system without knowing what it needs to hold together across a real product surface.
So the Design Foundation Sprint runs brand first, then product, in that order, on purpose. Four weeks: define the direction, build the brand system, design the product surface on top of it, then systemize the whole thing into something your engineering team can actually build from without you translating for them.
Why the system matters more than the deliverables
Every sprint like this used to end the same way: a Figma file and a PDF, handed off, slowly drifting out of date the moment the company kept moving without you. I structure the output differently. Brand rules, design tokens, components, templates, and a DESIGN.md file that your team, and your AI tools, can both keep working from after I’m gone. Claude, Cursor, Figma Make, whatever you’re already using. The system is the asset. The tools will keep changing under it, and that’s fine, because the system doesn’t depend on any one of them.
This is also, honestly, my answer to the question I get most often: why not just use AI to do this myself? You can, for the parts that don’t require judgment. AI accelerates good decisions and bad ones equally. The value I bring isn’t the AI. It’s twenty years of knowing which decision is actually right for your specific business, then using AI to build it faster than a traditional studio ever could.
If your team already has a system in place and the gap isn’t “we need one,” it’s “ours doesn’t work for our AI tools yet,” that’s a different, narrower engagement than the sprint. I built that one too: https://raftdesign.studio/design-system/
What a month can actually do
I’ll be direct about the limits. Four weeks doesn’t replace a design leader. It doesn’t map every edge case in a mature product. What it does do: give you a real brand system, five to ten core product screens built on top of it, and a foundation solid enough that whoever you hire next, in six months or two years, inherits something coherent instead of something they have to unwind first.
That’s the actual promise. Not “everything, forever.” Just the specific, bounded thing a funded startup needs in the specific window before it’s ready to hire the thing I used to be, twenty years ago, before any of this had a name.
If you’re in that window right now, reply to this and tell me where the gap actually is. And if you know a founder who’s in it, this is the piece to forward them:
https://raftdesign.studio/design-foundation/
Originally published in Upstream on Substack.
