Messaging and positioning
Your product has strong adoption with SMBs but leadership wants to move upmarket to enterprise. How do you evolve the positioning without alienating your existing base?
Learn what small customers would hate to lose and keep that promise at the center of the shared story. Add an enterprise layer for control, reporting, and rollout support on its own pages and in sales material.
Keep the homepage and self-serve flow aimed at the base until data says otherwise, and agree with leadership on tripwires in small-customer metrics that would pause changes to shared surfaces.
5 min read
Free 10-minute mock
Practice “Moving upmarket from SMB” free
Your first mock interview is free (10 minutes). No card needed.
The tension inside an upmarket move
Leadership has already decided the direction. So the question isn’t whether to go upmarket. It asks whether you can serve the new buyer without damaging the business that pays the bills today.
Many companies lose their base during this shift without noticing for a year. The homepage slowly fills with security badges and logos of large brands, pricing grows a contact-us tier, and small buyers quietly conclude the product is no longer for them. A good answer names that risk and puts numbers on it.
What small customers and new enterprise buyers each want
| Group | What they value | What would push them away |
|---|---|---|
| Independent restaurant owners | Setup in an afternoon, no training, fair monthly price | Sales calls, annual contracts, a site that looks built for chains |
| Multi-location restaurant groups | Consolidated reporting, permissions by location, a rollout plan | No admin controls, no named support contact |
| Sales team | Deals that close, material that holds up in procurement | Messaging that sounds small |
| Leadership | Larger contracts and a bigger market story | A slow start with no visible progress |
One overlap is easy to miss. Large buyers care about ease of setup too, since rollout across forty locations is their biggest worry. The core promise can stay the same for both groups.
Taking a restaurant payroll product upmarket
“I’d begin by asking which parts of our story small customers would hate to lose. We make payroll for restaurants, and most revenue comes from single-location owners. When I talk to ten of them, they say it’s fast to set up and nobody needs training. That’s the promise to protect. Restaurant groups care about it too, because rolling out to forty locations is their biggest headache. So I’d keep the core line, payroll your managers can run on a Friday night, and add a second layer for groups. Consolidated reporting, permissions by location, and a rollout plan with a named contact. The homepage and self-serve flow stay aimed at owners. Groups get their own page, deck, and proof. Before we start, I’d ask leadership to agree on tripwires, for example a drop of more than ten percent in self-serve signups over a month, or a rise in churn among single-location accounts. If one trips, we pause changes to shared surfaces and find the cause.”
Trade-offs to name when leadership wants enterprise
- Roadmap attention. Enterprise features pull engineering time from the base. Say which small-customer requests stay protected.
- Pricing. A new top tier can make the entry plan look cheap and limited. Keep the entry plan’s promise whole.
- Support. Large accounts expect a named contact. If that comes from the same team, response times for owners slip.
- Proof. Big logos help groups trust you and can scare owners away. Place them on the group path.
For the Exceptional end of strategic thinking, point out the lag. Small-customer churn shows up months after the cause, so tripwires need leading signals like signups and plan mix. Churn alone arrives too late to act on.
Where upmarket positioning answers lose the room
“I’d build an enterprise messaging track around security, scale, and compliance, and add it to the site and the sales deck. We’d keep some SMB content so existing customers still feel seen.”
It bolts enterprise language onto the current story and hopes the base stays. There is no research into what small customers value, no separation of surfaces, and no signal that would tell you the move is hurting. Fix it by naming the promise you would protect and the threshold that would pause you.
The opposite mistake argues against the move. Leadership has decided. Show how you would make it work, and put the risk on the table as tripwires they agreed to.
Follow-ups on the SMB to enterprise shift
| Likely follow-up | The worry behind it | Response |
|---|---|---|
| One brand voice or two? | Consistency | One voice, two levels of detail. Two voices read as two companies. |
| Leadership won’t accept a pause. | Influence | Offer a smaller response, such as reverting one page, and show the revenue at risk. |
| How do you split features between plans? | Packaging judgment | Features that matter only across many locations go in the group plan. Core payroll stays in every plan. |
| What tells you the move is working? | Success criteria | Group pipeline and win rate rising while owner signups and churn hold steady. |
More questions in this category
Frequently asked questions
- Should SMB and enterprise buyers share one homepage?
- Usually the homepage stays with whoever drives most revenue today. Give enterprise buyers a clear path one click away, and revisit once their share of pipeline grows.
- What if enterprise requirements contradict what small customers love?
- Say which group you would favor and why, using revenue and growth data. Then describe how the other group stays protected, such as separate plans or a setting that hides complexity.
Guides that help with this question
All guidesFree 10-minute mock
Practice “Moving upmarket from SMB” free
A Mokk session asks this question, follows up on your answer, and scores it on five competencies. Your first mock is 10 minutes, scored like a full interview. No card needed.
Your first mock interview is free (10 minutes). No card needed.
Practice “Moving upmarket from SMB” free
10 minutes · no card needed