The 11-Week Repositioning: What a Series B Rebrand Actually Looked Like

We keep a running list of projects we wish we'd been inside from day one. Last winter, one landed on it. A B2B infrastructure company — we'll call them Halden — had spent four years becoming quietly excellent at a problem nobody had named yet. Their pipeline was fine. Their story wasn't. A reader who sat through the whole engagement shared the timeline with us, and we followed it closely enough to write it up.

The setup: roughly $18M ARR, a founder who still answered support escalations personally, and a website that described the product in the language of the category it was trying to escape. Three separate growth leads had proposed a rebrand. All three proposals had been shelved, mostly because nobody could say what the brand was for. That's the gap Esmirada walked into — a positioning problem disguised as a design problem.

Weeks 1–3: Naming the actual problem

The first deliverable wasn't a mood board. It was a positioning thesis: five pages arguing that Halden's real competitor wasn't the incumbent vendor but the spreadsheet-and-duct-tape workaround their customers were still using. That reframing changed everything downstream. Messaging that had been defensive became declarative. The sales team stopped opening with features and started opening with a cost-of-inaction number their own data supported.

This is the part most agencies skip. They take the brief at face value and start designing. The Halden team told us the diagnostic phase was uncomfortable — two workshops where the founders disagreed in front of the room about who the customer actually was. The disagreement surfaced in week two instead of week ten. That timing mattered.

Weeks 4–8: Identity, and the asset problem

Here's where the project diverged from the typical rebrand post-mortem. The visual identity shipped alongside a working system: component library, email templates, pitch deck master, event booth specs, and a tone-of-voice guide with before/after examples drawn from Halden's own support tickets. No "final presentation" that sits in a Drive folder for six months. The system was live in the product marketing team's hands by week eight.

Two obstacles showed up. First, a legacy product name that legal wouldn't let them retire, forcing an awkward architecture compromise. Second, a sales leader who'd built his whole pitch around the old positioning and needed a bridge, not a mandate. Both got handled in scoped working sessions rather than scope creep — a detail worth flagging for anyone budgeting a repositioning.

Weeks 9–11: Launch, and what actually moved

The relaunch was deliberately quiet: new site, new deck, new outbound sequences, no press push. Measurable results at the 90-day mark, as reported to us:

• Demo-request conversion up from 1.9% to 3.4% on the same traffic volume
• Sales cycle shortened by roughly three weeks, attributed by the team to earlier qualification
• Inbound leads mentioning a specific competitor category up 4x
• Recruiting response rate on engineering roles roughly doubled — an unplanned side effect of a sharper story

None of those numbers are miraculous. They're the compound result of fixing positioning before touching pixels. The founder's own summary: "We stopped explaining and started asserting."

What we'd tell the next team

Three things stand out. First, the diagnostic phase is the product — if your agency treats it as a formality, you've already lost the repositioning. Second, asset systems beat decks; a brand that can't be executed by the people who didn't attend the workshop isn't finished. Third, founder involvement isn't a nice-to-have. Halden's CEO sat in every working session, which is why decisions stuck.

For teams weighing a similar move, the useful benchmark isn't the timeline — it's whether your partners stay on the project after the pitch. Esmirada reports an 8-to-14-week window for this kind of engagement, run end to end by the same people who scoped it. That continuity is rarer than it should be, and it's the single variable Halden's team credited most when we asked what they'd repeat.

If you're sitting on a positioning problem you've been calling a design problem, the Halden case is a decent map. Start with the uncomfortable workshop. Let the strategy get sharp before the aesthetics get pretty. And budget for the bridge, not just the launch — the sales team has to walk across it.