VU Custom is growing fast, and acquisitions are a key lever. But the business runs on a sprawl of platforms: four of its own today, plus roughly fifteen more inside YR ID, effectively one per customer. The work is twofold. Collapse all of it into a single platform, VU OS, and define what that product becomes next: dynamic personalization, self-service, a world-class experience.
Where things stand. VU OS is the destination, but VU still runs four products day to day: the legacy Silhouette and Admin tools, a customer-specific Bauer portal, and VU OS itself. YR ID adds roughly fifteen more, having built essentially one platform per customer over the years. The acquisition is the first of likely several. So this is a growing company with a widening platform sprawl, and a single place it has to drive everything toward: one team, one dream, one platform.
Strip away the deal noise and the central product challenge is consolidation. VU runs four platforms of its own, and YR ID brings roughly fifteen more, one per customer. Collapsing all of it into a single VU OS is the work everything else depends on. "One team, one dream, one platform" is not a slogan here, it is the entire product mandate.
VU is expanding, and buying logos is a key lever, with more deals likely. But every acquisition widens the sprawl before it narrows it. Growth and consolidation pull in opposite directions, and product is the function that resolves the tension. The faster the team can unify and migrate, the more the acquisition strategy actually compounds.
This is not only a cleanup job. Leadership wants to define where the product goes: dynamic personalization and customization, true self-service, and a world-class experience on top of one platform. That forward-looking mandate, protected from near-term client deliveries, is the most exciting part, and the place they are most explicitly asking for help.
Onboarding runs about 6 months (down from 12), and roughly 62 of those days are pure resource-gathering: colors, dropzones, fonts, catalog. Colin already sees the fix. Ingest a brand's Shopify catalog, auto-suggest dropzones, infer the assets. This is the highest-leverage metric in the business and it is squarely an AI and agentic-workflow problem.
Endgame: a small brand implements itself, live on day one, distributed through the Shopify app store. Today there are two salespeople and the company is turning away business because onboarding cannot scale. Self-service is the unlock for the long tail, and it is downstream of getting opportunity 01 right.
The protected-roadmap mandate makes this a clean greenfield brief: pre-customized, taste-aware experiences across a brand's whole product suite. Strategic, generative work, and the kind of build that does not exist anywhere in their space yet. It is the natural north star for what the unified product should become.
Migration is the moment of maximum churn risk, and with consolidation running on two fronts plus future acquisitions, it happens again and again. A better-orchestrated, more positive migration experience (the BrüMate lesson, below) protects the customer base and becomes a reusable asset for the next one.
Before anything unifies, someone has to map it: what each of VU's four products does that VU OS must absorb, what YR ID's ~15 customer builds depend on, and what genuinely carries forward versus gets retired. That mapping is unscoped today, it gates the entire consolidation, and it recurs with every future acquisition.
About 70 combined heads (employees plus contractors), carrying real waste and thin on high-caliber engineering. Only about 6 people sit on VU OS. Ben was brought in to support Warren (CTO) with Rackspace folks and velocity is improving, but ambition is currently outrunning the team that has to ship it.
YR ID's enterprise accounts are prestige but underpriced, sitting on aging tech that has been maintained rather than advanced. Re-pricing and re-platforming at the same time, while keeping marquee names like Ralph Lauren and EssilorLuxottica happy, is a narrow path to walk.
Strong product-market fit, strong demand, strong references. But two reps and an onboarding process that forces them to decline business means growth is capped by services capacity, not market appetite. Fix onboarding and the constraint largely dissolves, which is why opportunities 01 and 02 are the whole game.
This is end-to-end. What comes out of the software feeds embroidery and laser machines, so it has to be right and look great straight onto the floor. Self-service cannot mean loose. The threshold for letting a brand configure itself is unusually high here.
Their migration ran long, and once live, some orders had issues. Any self-service or migration push has to design for correctness first and delight second. Getting someone live faster only helps if what they ship is right.
A focused discovery sprint is the lowest-risk way to turn the platform sprawl and the road ahead into a clear, sequenced plan, before committing significant build time. Two parts, a few weeks, one concrete output.
The sprint, in two parts
A prioritized, build-ready plan: the consolidation roadmap, the highest-leverage product bets to pursue first (starting with the onboarding time-to-value problem), and a clear recommendation on sequencing. Something the team can act on the week it lands.
Next step
If that is useful, the next step is a short conversation to scope the focus, timeline and terms together. Four to six weeks is roughly the right size for the ground to cover, and we can tighten it to exactly what you need.