/ No. 04
2023
Simplifying several products into one after an acquisition
Turning three acquired tools into one Real Time Agent product, with a single brand, story and sales pitch, before scaling acquisition.
/ No. 04
2023
Simplifying several products into one after an acquisition
Turning three acquired tools into one Real Time Agent product, with a single brand, story and sales pitch, before scaling acquisition.
/ No. 04
2023
Simplifying several products into one after an acquisition
Turning three acquired tools into one Real Time Agent product, with a single brand, story and sales pitch, before scaling acquisition.
Details
Organisation
Domain Group (CoStar)
Sector
Proptech
Engagement
In-house
Role
Product marketing manager
Team
Product, Legal and Sales, with design, content, web and paid marketing
Work
Brand architecture, go-to-market strategy, sales enablement, product positioning, cross-functional governance
01
The situation
Real Time Agent is a digital transaction product used by real estate agents. It was acquired by Domain Group in 2019 as part of Domain’s broader SaaS marketplace strategy.
When I joined Domain, Real Time Agent was not operating as a single, coherent product. It was a collection of three separate tools, each with its own name, visual identity, website and positioning. One of those products had itself been acquired shortly before the Domain acquisition. None of the three were integrated into the Domain Agent Solutions portfolio or brand system.
This fragmentation created practical friction. To work around it, the sales team had already begun informally bundling the three tools together during conversations. Product and engineering soon recognised that merging them made complete sense from an infrastructure, technology stack and user experience standpoint.
The problem was that while Sales was bundling on the fly and Product was integrating the backend, there was no shared parent brand, no single explanation of value, and no clear market-facing architecture. Marketing had to step in to lead this transition from a customer-experience and brand perspective, turning an internal integration into a coherent commercial proposition.
01
The situation
Real Time Agent is a digital transaction product used by real estate agents. It was acquired by Domain Group in 2019 as part of Domain’s broader SaaS marketplace strategy.
When I joined Domain, Real Time Agent was not operating as a single, coherent product. It was a collection of three separate tools, each with its own name, visual identity, website and positioning. One of those products had itself been acquired shortly before the Domain acquisition. None of the three were integrated into the Domain Agent Solutions portfolio or brand system.
This fragmentation created practical friction. To work around it, the sales team had already begun informally bundling the three tools together during conversations. Product and engineering soon recognised that merging them made complete sense from an infrastructure, technology stack and user experience standpoint.
The problem was that while Sales was bundling on the fly and Product was integrating the backend, there was no shared parent brand, no single explanation of value, and no clear market-facing architecture. Marketing had to step in to lead this transition from a customer-experience and brand perspective, turning an internal integration into a coherent commercial proposition.
01
The situation
Real Time Agent is a digital transaction product used by real estate agents. It was acquired by Domain Group in 2019 as part of Domain’s broader SaaS marketplace strategy.
When I joined Domain, Real Time Agent was not operating as a single, coherent product. It was a collection of three separate tools, each with its own name, visual identity, website and positioning. One of those products had itself been acquired shortly before the Domain acquisition. None of the three were integrated into the Domain Agent Solutions portfolio or brand system.
This fragmentation created practical friction. To work around it, the sales team had already begun informally bundling the three tools together during conversations. Product and engineering soon recognised that merging them made complete sense from an infrastructure, technology stack and user experience standpoint.
The problem was that while Sales was bundling on the fly and Product was integrating the backend, there was no shared parent brand, no single explanation of value, and no clear market-facing architecture. Marketing had to step in to lead this transition from a customer-experience and brand perspective, turning an internal integration into a coherent commercial proposition.
02
The brief
Before changing anything externally, we mapped where the friction was actually occurring:
What existed | The practical impact |
|---|---|
Three overlapping tools | Buyers had to work too hard to grasp what was being sold |
Separate sites and visuals | Fragmented attention and diluted authority |
No single anchor product | Sales pitches varied depending on who was speaking |
Minimal Domain design link | A subtle, persistent leak in trust |
The decision was straightforward: sort out the market-facing structure before scaling marketing activity. Until the product structure made sense to an outside buyer, no amount of promotion would compensate.
02
The brief
Before changing anything externally, we mapped where the friction was actually occurring:
What existed | The practical impact |
|---|---|
Three overlapping tools | Buyers had to work too hard to grasp what was being sold |
Separate sites and visuals | Fragmented attention and diluted authority |
No single anchor product | Sales pitches varied depending on who was speaking |
Minimal Domain design link | A subtle, persistent leak in trust |
The decision was straightforward: sort out the market-facing structure before scaling marketing activity. Until the product structure made sense to an outside buyer, no amount of promotion would compensate.
02
The brief
Before changing anything externally, we mapped where the friction was actually occurring:
What existed | The practical impact |
|---|---|
Three overlapping tools | Buyers had to work too hard to grasp what was being sold |
Separate sites and visuals | Fragmented attention and diluted authority |
No single anchor product | Sales pitches varied depending on who was speaking |
Minimal Domain design link | A subtle, persistent leak in trust |
The decision was straightforward: sort out the market-facing structure before scaling marketing activity. Until the product structure made sense to an outside buyer, no amount of promotion would compensate.
03
What I did
A simple hierarchy
Working alongside Product, we translated the combined capability into a clear brand hierarchy:
Domain
Agent Solutions
Real Time Agent
Bidding
Digital Contracts
Digital Agreements
This achieved three things immediately. It collapsed three separate pitches into one explanation. It recast the former standalone apps as step-by-step features within a single workflow. And it anchored Real Time Agent directly to the credibility of the Domain parent brand.
How alignment was reached
This was a collaborative exercise to ensure the external story matched internal reality. The structure was worked through with the teams who had to live with the outcome:
Team | What was resolved |
|---|---|
Product | Agreeing feature versus product definitions, workflow operations and roadmap scope |
Legal | Sorting out naming rights, brand boundaries and compliant claims |
Sales | Testing whether the new structure reflected real buying conversations and objection handling |
Nothing progressed until all three functions were aligned.
Cleaning house
With the framework locked, we removed the legacy clutter across customer touchpoints.
Sub-brands were retired and brought cleanly under the Domain design system. We decommissioned the individual micro-sites and established a single Real Time Agent destination, built to explain the end-to-end workflow in plain language, support basic SEO and introduce consistent lead capture.
Teaching the pitch
Before increasing external acquisition spend, we turned inward.
We ran live enablement sessions with Sales and Marketing, established a single agreed narrative with supporting assets, and retired legacy decks. The aim was strict consistency: everyone needed to describe the product in the exact same way before asking customers to understand it.
Scaling up
Only after consolidation and enablement were complete did we turn the tap on.
Launched Real Time Agent’s first always-on paid acquisition campaigns.
Aligned paid, organic and mid-funnel activity around one workflow story.
Introduced webinars and masterclasses to reinforce the process narrative.
My role
As Marketing Lead for Real Time Agent and Agent Solutions, I partnered closely with Product to lead the consolidation from a brand, messaging and customer-facing perspective. I owned the brand hierarchy and product narrative, worked directly with Product and Legal to agree on naming and claims, and directed execution across design, content, web and paid marketing. I also led the internal sales enablement effort to ensure the unified story was fully adopted before scaling acquisition spend.
03
What I did
A simple hierarchy
Working alongside Product, we translated the combined capability into a clear brand hierarchy:
Domain
Agent Solutions
Real Time Agent
Bidding
Digital Contracts
Digital Agreements
This achieved three things immediately. It collapsed three separate pitches into one explanation. It recast the former standalone apps as step-by-step features within a single workflow. And it anchored Real Time Agent directly to the credibility of the Domain parent brand.
How alignment was reached
This was a collaborative exercise to ensure the external story matched internal reality. The structure was worked through with the teams who had to live with the outcome:
Team | What was resolved |
|---|---|
Product | Agreeing feature versus product definitions, workflow operations and roadmap scope |
Legal | Sorting out naming rights, brand boundaries and compliant claims |
Sales | Testing whether the new structure reflected real buying conversations and objection handling |
Nothing progressed until all three functions were aligned.
Cleaning house
With the framework locked, we removed the legacy clutter across customer touchpoints.
Sub-brands were retired and brought cleanly under the Domain design system. We decommissioned the individual micro-sites and established a single Real Time Agent destination, built to explain the end-to-end workflow in plain language, support basic SEO and introduce consistent lead capture.
Teaching the pitch
Before increasing external acquisition spend, we turned inward.
We ran live enablement sessions with Sales and Marketing, established a single agreed narrative with supporting assets, and retired legacy decks. The aim was strict consistency: everyone needed to describe the product in the exact same way before asking customers to understand it.
Scaling up
Only after consolidation and enablement were complete did we turn the tap on.
Launched Real Time Agent’s first always-on paid acquisition campaigns.
Aligned paid, organic and mid-funnel activity around one workflow story.
Introduced webinars and masterclasses to reinforce the process narrative.
My role
As Marketing Lead for Real Time Agent and Agent Solutions, I partnered closely with Product to lead the consolidation from a brand, messaging and customer-facing perspective. I owned the brand hierarchy and product narrative, worked directly with Product and Legal to agree on naming and claims, and directed execution across design, content, web and paid marketing. I also led the internal sales enablement effort to ensure the unified story was fully adopted before scaling acquisition spend.
03
What I did
A simple hierarchy
Working alongside Product, we translated the combined capability into a clear brand hierarchy:
Domain
Agent Solutions
Real Time Agent
Bidding
Digital Contracts
Digital Agreements
This achieved three things immediately. It collapsed three separate pitches into one explanation. It recast the former standalone apps as step-by-step features within a single workflow. And it anchored Real Time Agent directly to the credibility of the Domain parent brand.
How alignment was reached
This was a collaborative exercise to ensure the external story matched internal reality. The structure was worked through with the teams who had to live with the outcome:
Team | What was resolved |
|---|---|
Product | Agreeing feature versus product definitions, workflow operations and roadmap scope |
Legal | Sorting out naming rights, brand boundaries and compliant claims |
Sales | Testing whether the new structure reflected real buying conversations and objection handling |
Nothing progressed until all three functions were aligned.
Cleaning house
With the framework locked, we removed the legacy clutter across customer touchpoints.
Sub-brands were retired and brought cleanly under the Domain design system. We decommissioned the individual micro-sites and established a single Real Time Agent destination, built to explain the end-to-end workflow in plain language, support basic SEO and introduce consistent lead capture.
Teaching the pitch
Before increasing external acquisition spend, we turned inward.
We ran live enablement sessions with Sales and Marketing, established a single agreed narrative with supporting assets, and retired legacy decks. The aim was strict consistency: everyone needed to describe the product in the exact same way before asking customers to understand it.
Scaling up
Only after consolidation and enablement were complete did we turn the tap on.
Launched Real Time Agent’s first always-on paid acquisition campaigns.
Aligned paid, organic and mid-funnel activity around one workflow story.
Introduced webinars and masterclasses to reinforce the process narrative.
My role
As Marketing Lead for Real Time Agent and Agent Solutions, I partnered closely with Product to lead the consolidation from a brand, messaging and customer-facing perspective. I owned the brand hierarchy and product narrative, worked directly with Product and Legal to agree on naming and claims, and directed execution across design, content, web and paid marketing. I also led the internal sales enablement effort to ensure the unified story was fully adopted before scaling acquisition spend.
06
What happened next
We judged success by deal clarity and funnel efficiency rather than top-of-funnel noise.
Signal | What it suggested |
|---|---|
Improved MQL → SQL conversion | Buyers better understood what they were enquiring about |
Demand concentrated through one entry point | Reduced entry fragmentation |
Fewer sales clarification questions | The core story was doing its job |
Secondary indicators, like organic engagement alongside paid activity and steady webinar attendance, served as confirmation that the product was now easier to evaluate and buy.
06
What happened next
We judged success by deal clarity and funnel efficiency rather than top-of-funnel noise.
Signal | What it suggested |
|---|---|
Improved MQL → SQL conversion | Buyers better understood what they were enquiring about |
Demand concentrated through one entry point | Reduced entry fragmentation |
Fewer sales clarification questions | The core story was doing its job |
Secondary indicators, like organic engagement alongside paid activity and steady webinar attendance, served as confirmation that the product was now easier to evaluate and buy.
06
What happened next
We judged success by deal clarity and funnel efficiency rather than top-of-funnel noise.
Signal | What it suggested |
|---|---|
Improved MQL → SQL conversion | Buyers better understood what they were enquiring about |
Demand concentrated through one entry point | Reduced entry fragmentation |
Fewer sales clarification questions | The core story was doing its job |
Secondary indicators, like organic engagement alongside paid activity and steady webinar attendance, served as confirmation that the product was now easier to evaluate and buy.
07
What I learnt from this project
Post-acquisition products often stall when technical consolidation isn’t matched by market-facing clarity. This case demonstrates how aligning brand hierarchy and narrative with underlying product integration creates the prerequisite foundation for effective demand generation.
07
What I learnt from this project
Post-acquisition products often stall when technical consolidation isn’t matched by market-facing clarity. This case demonstrates how aligning brand hierarchy and narrative with underlying product integration creates the prerequisite foundation for effective demand generation.
07
What I learnt from this project
Post-acquisition products often stall when technical consolidation isn’t matched by market-facing clarity. This case demonstrates how aligning brand hierarchy and narrative with underlying product integration creates the prerequisite foundation for effective demand generation.
In their words
“Brandon has made remarkable strides in driving improvements to our Product Marketing and Brand Marketing for our key products. In doing so, he's raised the bar across our Marketing function and demonstrated Marketing leadership in these areas.”