One Platform, Two Brands
MyAgentConnection connects clients with an agent and the agent’s vendor network under its own brand—running on the infrastructure we built for C2V.
- Client
- MyAgentConnection · a subsidiary of Client2Vendor
- Industry
- Real Estate
- Engagement
- White-label architecture, branding, web & mobile apps, ongoing support
- Platforms
- Web · Android · iOS
2
Brands running on one codebase
3
Apps per brand — web, Android, iOS
1
Platform to maintain, secure and improve
What the business was living with
With C2V proven, the founder wanted to reach a different audience with a different proposition: a consumer-facing brand where clients connect with an agent and, through the agent, the agent’s trusted vendors.
The obvious path—build a second product—would have doubled engineering cost and split every future improvement across two codebases. The alternative was to make C2V’s infrastructure brand-agnostic.
What was broken
- A new brand needed its own name, look, domain and app-store presence
- The audience and messaging differed from C2V, but the underlying workflows were the same
- Two separate products would mean two backlogs, two release trains and duplicated bugs
- Data, users and configuration had to stay cleanly separated between brands
The solution
We white-labelled C2V: the referral, marketplace, transaction and chat systems became a shared core, and everything brand-specific became configuration.
Brand-Agnostic Core
The referral system, vendor marketplace, transaction management and permission-based chat run once and serve both brands.
Separate Identity & Apps
MAC has its own branding, domain, onboarding and web, Android and iOS apps—published under its own name, indistinguishable from a standalone product.
Isolated Data & Configuration
Users, vendors, transactions and settings are partitioned per brand, so each business operates independently on shared infrastructure.
One Release, Two Products
Improvements and fixes ship to both brands from a single pipeline, with brand-specific features switched on where needed.
Separating brand from behaviour without forking the code
A white-label only pays off if nothing is duplicated. We went through the existing platform and pulled every brand-dependent assumption—names, colours, copy, email templates, app identifiers, legal text, feature flags—into configuration resolved at runtime. Anything that could not be configured was refactored until it could.
Mobile was the hardest surface: two app-store identities, push notification channels and deep links, built from one codebase without a maintenance burden for the team.
What changed
MyAgentConnection launched as a fully branded product on web, Android and iOS, reaching a new audience without a second engineering team. Both brands now benefit from every improvement made to the shared core.
- A second brand and audience without a second platform to build or maintain
- Faster launch than a ground-up build, on infrastructure already proven in production
- Independent operation for each business with shared security, hosting and support
- A repeatable model for launching further brands or partner editions
Stack & integrations
- Shared multi-brand core
- Runtime brand configuration
- Web application
- Android & iOS apps
- Single CI/CD pipeline
- Cloud hosting & DevOps