ChoiceBuys / Hospitality procurement platform
A content system built to keep growing.
A large migration became an architecture problem: how to organize vendor, product, brand, and operational content so the next expansion would be easier—not another reinvention.
The platform problem
Migration was only the visible task. Repeatability was the real requirement.
ChoiceBuys held a wide range of information: brand resources, vendor directories, product rules, media, offers, news, and profitability guidance. Moving that volume cleanly required more than transferring pages.
The work focused on patterns that could be reused across brands and content families. The goal was an operating structure that made future additions understandable, predictable, and easier to manage.
Organized for reuse
Information architecture
Structure the content before styling the destination.
Product rules illustrate the underlying challenge: a large vocabulary needed to remain searchable, browsable, and consistent while serving different hotel brands and operating contexts.
From implementation to ownership
The role grew with the system.
I joined as a Web Developer. As the platform grew, I took responsibility for migration structure, product priorities, stakeholder requests, and the decisions needed to keep the system usable.
- 01
Web development
Joined the work as a Web Developer, translating content and business requirements into a dependable web platform.
- 02
Migration architecture
Organized a large body of information around structures that could be repeated instead of rebuilt for every brand or content type.
- 03
Product stewardship
The role expanded toward product management: clarifying priorities, shaping reusable patterns, and connecting stakeholder needs to platform decisions.
- 04
Continuity
Long-term ownership kept the system useful as content, brands, vendors, and operating requirements continued to change.
Shared structure / different brand needs
Shared structure, tailored brand experiences.
The same navigation and content patterns supported brand hubs, learning resources, news, archives, and video while preserving each brand’s context.
What changed
The migration left repeatable patterns for new brands, vendors, and content.
- Content migration shaped around future reuse
- Information architecture across varied content families
- Brand-specific experiences on shared platform patterns
- Long-term product and technical continuity
Screenshots are shown with permission. Private operational data, internal controls, and confidential material are excluded.