Switchboard SaaS Platform
Serve multiple market tiers from one configurable code base
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 96%
The Switchboard SaaS Platform uses one multi-tenant code base to serve customers ranging from small businesses to large enterprises. The company first identifies common needs, then makes advanced capabilities configurable through switches rather than creating separate products. Small customers receive an affordable, simple package, while sophisticated organizations activate richer functionality, integrations, governance, and scale. This supports efficient deployment and lets customers grow without migrating to a different platform. ExactTarget began with small retailers, developed parent-child architecture for franchises, and progressively added enterprise capabilities while preserving a shared platform. The model creates substantial scale and market reach, but it also introduces organizational tension: product priorities, professional services, support, packaging, and sales motions must remain explicitly segmented even when the underlying software is shared.
Origin
ExactTarget began with thousand-dollar annual subscriptions for restaurants and other small retailers, expanded through franchise architecture, and eventually served seven- and eight-figure enterprise customers on essentially the same platform.
Core principles
- 01Build shared capabilities once
- 02Control complexity through configuration
- 03Package simplicity for small customers
- 04Unlock sophistication for enterprise customers
- 05Let successful customers scale without switching platforms
How to run it
- 1
Find the shared workflow
Define the core job that customers perform regardless of company size. Confirm that this common need is strong enough to justify one platform.
Pro tip Describe the shared job without referencing segment-specific features.
Watch out A superficial similarity can hide fundamentally different enterprise requirements.
- 2
Start with a focused segment
Build a simple product for the initial segment and learn its workflow deeply. ExactTarget began with small businesses before moving into franchises and enterprises.
Pro tip Choose a segment that provides frequent feedback and relatively short sales cycles.
Watch out Designing for every future segment on day one can prevent the first product from shipping.
- 3
Add an architectural bridge
Introduce capabilities that solve the next segment's structural needs while preserving the common core. ExactTarget used parent-child relationships to support centralized franchise branding with local autonomy.
Pro tip Look for an intermediate segment that naturally bridges small and large customers.
Watch out Avoid custom implementations that cannot become reusable platform capabilities.
- 4
Create the switchboard
Put optional and advanced capabilities behind configuration controls. Maintain one code base while allowing packages and deployments to vary by customer sophistication.
Pro tip Define secure, tested defaults for every switch combination that sales can offer.
Watch out Uncontrolled feature flags create operational and testing complexity.
- 5
Segment the organization
Tailor packaging, sales, services, support, and product communication to each tier even though the software is shared. Assign clear ownership for tensions between segment needs.
Pro tip Measure economics and satisfaction independently for each segment.
Watch out A universal product does not imply a universal go-to-market or service model.
- 6
Enable customer pull-through
Make upgrades and added capacity natural as customers grow or employees move between organizations. Preserve familiarity and data continuity to reduce reasons to switch.
Pro tip Design pricing and onboarding so expanding customers can activate capability without reimplementation.
Watch out Complex upgrade paths erase the retention advantage of a shared platform.
In the wild
ExactTarget started with restaurants, dry cleaners, and pizza shops paying roughly a thousand dollars per year. It then developed parent-child architecture for franchise organizations and continued adding sophisticated capabilities until small businesses and seven- or eight-figure enterprise clients could use essentially the same platform.
→ The company expanded upmarket while retaining SMB reach and allowing customers such as Groupon to scale on the platform.
Common mistakes
Forking the product by segment
Separate code bases multiply development and support costs and weaken the reuse that makes SaaS scalable.
Ignoring organizational segmentation
Even with shared software, enterprise and SMB customers need different sales, service, support, and packaging models.
Turning on everything by default
Exposing enterprise complexity to small customers undermines the affordability and simplicity that attracted them.
Is it for you?
Best for
It is best for SaaS markets where customers of different sizes share a common core workflow but need different levels of sophistication.
Not ideal for
It is not ideal when segments require fundamentally incompatible architectures, workflows, security models, or buying motions.
From the transcript
“you could essentially build software once and sell and deploy it over and over again”
“every feature we ever built, you know, had a switchboard.”
“we could uh deploy the software and and package it in a really flexible way that was very simple for the small business, or we…”
From the episode
ExactTarget (acquired by Salesforce) with Scott Dorsey
Scott Dorsey