I approach go-to-market like an engineer: define the system, design the interfaces, and be willing to refactor. Reflecting on lessons from Rich Rao affirmed that a rigorous, architecture-first mindset can turn messy GTM motions into a scalable operating system for product-led growth and B2B marketing.
Rich Rao is the VP of the Small Business Group at Meta, where he manages the global revenue and operations for properties including Facebook, Instagram and WhatsApp. He also spent 10 years at Google, where he held a bunch of different go-to-market roles at the company, eventually becoming the GM for the Devices and Education verticals.
In our discussion, he explains how his engineering background influences his approach to GTM — from an architecture method to the concept of refactoring. That frame resonates deeply with how I run product management leadership at scale: start with the blueprint, then iterate deliberately instead of stacking one-off tactics.
We also wind back the clock to his earliest days at Google on the team that was building and selling Gmail for your domain. That story captures the zero to one B2B marketing muscle: when constraints are high, the “system design” of GTM matters more than any single channel.
There are a ton of early startup mental models that Rich shares from this period in the company’s history, including why they ended up ditching free trials and his biggest pricing lessons. I’ve seen the same pattern: open-ended free trials often attract the wrong segments, inflate support load, and mask weak activation. Time-boxed or usage-capped trials tied to a clear value metric perform better, reduce churn, and sharpen SaaS pricing strategy.
Here’s how I operationalize an engineering lens in GTM. First, I create an “architecture method” for distribution: define system boundaries (ICP, jobs-to-be-done), interfaces (hand-offs between marketing, sales, and product), and SLAs (lead response, onboarding, success). Second, I instrument everything to observe bottlenecks — then “refactor” GTM like code: remove dead channels, simplify packaging, and standardize the path to value. Third, I treat pricing as part of the design, not a late-stage patch: align paywalls with activation moments, use value-based metrics, and avoid feature sprawl that confuses buyers.
When we need step changes, I run scheduled refactoring sprints: prune legacy offers, consolidate SKUs, and clarify messaging to reduce cognitive load. Just as technical debt slows product delivery, GTM debt (too many plans, inconsistent positioning, orphaned channels) drags conversion and expansion. A quarterly cadence to pay down this debt keeps the system healthy.
The outcome is a repeatable motion: an engineered go-to-market system that compounds learning, supports product-market fit lessons, and scales across segments without breaking. If you lead product or growth, think like an architect, measure like an engineer, and refactor before your funnel stalls — your team, customers, and P&L will feel the difference.
Leave a Reply