Skip to content
mokk

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 protect that promise in the shared story. Add an enterprise layer for security, control and rollout support on its own pages and sales materials. Agree with leadership on tripwires in small-team metrics that would pause changes to shared surfaces.

Updated · 3 min read

Why interviewers ask it

Moving upmarket is where many companies damage the business that got them there. The interviewer wants a plan that respects leadership’s direction and still protects current revenue with numbers you can watch.

This question leans on strategic thinking. The rubric says a Strong answer on strategic thinking defines measurable outcomes and adjusts when results fall short.

How to structure your answer

  1. Ask your best small customers. Find out what they value and what change would make them leave.
  2. Keep the core promise. Decide which line stays true for both audiences, since enterprise buyers often want the same ease of adoption.
  3. Add a second layer. Security, admin controls and rollout support, placed on dedicated pages and in sales material.
  4. Separate the surfaces. The homepage and self-serve flow stay aimed at small teams until data says otherwise.
  5. Agree on tripwires. Name the signup, conversion or churn changes that would pause the shift.

What a strong answer sounds like

The story is made up. Borrow the order of the moves and bring your own facts.

“I’d begin by asking which parts of our story small customers would hate to lose. Say we make project software and seventy percent of revenue comes from teams under fifty seats. When I interview ten of them, they tell me it’s fast to set up and nobody needs training. That’s the promise to protect. Enterprise buyers care about it too, since adoption is their biggest headache, so I’d keep the core line and add a second layer for security, admin controls and rollout support. The homepage and self-serve flow stay aimed at small teams. Enterprise gets its own page, deck and proof. I’d also ask leadership to agree on tripwires before we start, for example a drop of more than ten percent in self-serve signups or a rise in small-team churn. If one trips, we pause changes to shared surfaces and look at what caused it.”

What a weak answer sounds like

“I would create enterprise messaging focused on security, scale and compliance and add it to the website. I would also keep some SMB content so we don’t lose existing customers. Sales would use the new materials for larger deals.”

The weak answer bolts enterprise language on and hopes small customers stay. Say what they value, keep it visible in the shared story, and set a threshold that tells you when the shift is hurting them.

Follow-ups to expect

  • Would you run one brand voice or two?
  • What if leadership won’t accept a pause?
  • How do you decide which features go in which plan?
  • What tells you the upmarket move is working?

Start with the follow-up you would least like to hear. The follow-up questions guide covers how to handle it.

More questions in this category

Frequently asked questions

Should enterprise and SMB share a homepage?
The homepage usually stays with whoever drives most of your pipeline today. Give enterprise buyers a dedicated path that’s one click away.
What if enterprise needs contradict what small customers value?
Say which group you’d favor and why, using revenue and growth data. Then describe how you’d protect the other group, for example through separate plans.

Practice it

Try this question in a live session.

Say your answer aloud and get scored on five competencies, with feedback that quotes what you said. A question costs 1 credit.