Context
Voiso rebranded twice during my tenure. The 2024 relaunch introduced a new brand, website, and messaging system, with every landing page rewritten. The second rebrand deepened the positioning across core product, solution, and industry pages. I owned all landing-page copy for both and worked with Design, Product, and Engineering from the earliest strategic decisions through delivery.
Voiso rebranded twice during my tenure. The 2024 relaunch introduced a new brand, website, and messaging system, with every landing page rewritten. The second rebrand deepened the positioning across core product, solution, and industry pages. I owned all landing-page copy for both and worked with Design, Product, and Engineering from the earliest strategic decisions through delivery.
The Strategy
Give each page a distinct commercial job
Every brief defined the page purpose, journey stage, target industries, buyer roles, and conversion goal. The Predictive Dialer page served prospects evaluating outbound performance. The Flow Builder page served operations and technical buyers evaluating routing, IVR, and workflow control. Those different jobs determined the questions, proof, and structure each page required.
Every brief defined the page purpose, journey stage, target industries, buyer roles, and conversion goal. The Predictive Dialer page served prospects evaluating outbound performance. The Flow Builder page served operations and technical buyers evaluating routing, IVR, and workflow control. Those different jobs determined the questions, proof, and structure each page required.
Translate positioning into product-specific arguments
The shared brand promise had to produce a clear argument for each product. Predictive Dialer prioritized live conversations, answer rates, campaign efficiency, and connectivity. Flow Builder prioritized direct customer control, unified voice and digital flows, routing reliability, and technical depth. Each brief connected product capabilities to the operating outcomes its buyers valued.
The shared brand promise had to produce a clear argument for each product. Predictive Dialer prioritized live conversations, answer rates, campaign efficiency, and connectivity. Flow Builder prioritized direct customer control, unified voice and digital flows, routing reliability, and technical depth. Each brief connected product capabilities to the operating outcomes its buyers valued.
Design the evidence and conversion path
The briefs specified message priority, claims, supporting proof, social proof, infrastructure assurances, section sequence, conversion points, FAQs, search targets, and voice rules. This gave writers, designers, product experts, and reviewers one decision record for each page.
The briefs specified message priority, claims, supporting proof, social proof, infrastructure assurances, section sequence, conversion points, FAQs, search targets, and voice rules. This gave writers, designers, product experts, and reviewers one decision record for each page.
Execution
Rewrite and launch the first site
For the 2024 relaunch, I rewrote every landing page and coordinated the copy with the new brand, architecture, and design through launch.
The Voiso homepage before and after the 2024 relaunch.
Turn the second strategy into 29 executable briefs
For the second rebrand, I created 29 briefs covering core product, solution, and industry pages. Each one specified the page purpose, audience, journey stage, message hierarchy, evidence, section-by-section structure, conversion path, voice rules, and SEO targets. The shared framework held the rebrand together while allowing each product story to follow its own buyer logic.
Two products, one briefing system: shared architecture with distinct buyer logic, evidence, and conversion paths.
Results
The first relaunch established a stronger platform for organic acquisition. During the following year, sitewide non-branded traffic rose as the rebuilt landing pages and active content program operated together.
The second rebrand produced a complete messaging architecture and 29 execution-ready briefs. Every core page had a defined business role, audience, argument, evidence plan, conversion path, voice standard, and search target. The launch occurred after my tenure, so the completed system and production handoff are the documented outcome.
The first relaunch established a stronger platform for organic acquisition. During the following year, sitewide non-branded traffic rose as the rebuilt landing pages and active content program operated together.
The second rebrand produced a complete messaging architecture and 29 execution-ready briefs. Every core page had a defined business role, audience, argument, evidence plan, conversion path, voice standard, and search target. The launch occurred after my tenure, so the completed system and production handoff are the documented outcome.
What I’d Do Differently
I would build the lexicon at the start of the first rebrand. The 2024 relaunch relied heavily on my direct review to maintain consistency across dozens of pages. Writing the system in week one would have made that consistency easier to distribute across contributors and simpler to maintain as the site expanded.
