Marketing Strategy PMM

Enterprise Tier GTM — Zero to First 10 Accounts

Phase 1: Find enterprise signal in your existing base (weeks 1–2)

Query your CRM/billing system:

• Accounts with 15+ seats on $299 plan (paying $4,485+/month on per-seat pricing)
• Accounts in industries with compliance requirements (healthcare, finance, legal)
• Accounts that have contacted support about SSO, custom roles, or audit logs

This list is your enterprise pilot candidates. Target the top 10.

Phase 2: Nail the first 3 accounts (weeks 3–8)

Don't write a sales playbook yet. Sell these manually:

• Founder or Head of Product leads the call (not a hired AE)
• Goal: understand what they'd need to sign at $2K/month
• Build those 2–3 features (likely: SSO, admin controls, SLA, invoice billing)
• Close with a design partner discount (6 months at $1,200 with testimonial rights)

Phase 3: Productize the motion (weeks 9–16)

With 3 accounts live:

• Write the sales deck based on what actually closed deals
• Build a case study from your best design partner
• Define ICP: title, company size, industry, trigger event
• Hire one AE (or promote an SDR) using the playbook you just wrote

Revenue target: 3 accounts at $2K = $6K MRR in 90 days — enough to prove the tier before building a full sales org.

Why horizontal positioning stalls at $3–5M ARR

At $3M ARR, a horizontal product competes for attention against every well-funded tool in adjacent categories. Your ICP is everyone and no one. Sales cycles are longer because buyers need to understand how your general-purpose tool fits their specific context — that education burden falls entirely on you. CAC stays high, referrals don't compound within industries, and you can't build deep feature moats because you're serving 15 different use cases.

Vertical positioning unlocks growth through mechanisms horizontal positioning can't access:

• Less competition: A workflow tool for architecture firms has maybe 3 real competitors. A general workflow tool has 50.
• Higher willingness to pay: Vertical-specific software solves a more precise pain. An architecture firm pays $89/month for "workflow tool" but $250/month for "AIA phase tracking with billing integration" — same software, different frame.
• Referrals within industry: When an architecture firm recommends you to a peer firm, they're vouching for exactly the right product for that buyer. Word-of-mouth velocity in a vertical is exponentially faster than across industries.
• Clearer ICP: One vertical means one set of sales collateral, one onboarding flow, one set of case studies. Everything compounds.

The $3–5M ARR ceiling is real. Most companies that break through it either find a dominant vertical or raise significant capital to brute-force the horizontal market. At $3M ARR without institutional capital, vertical is almost always the right move.

Finding your dominant vertical

Don't guess — use your data. Run this analysis:

1. Industry concentration: What percentage of customers are in each industry? Look for clusters. If 30% of your 400 customers are in construction, professional services, or healthcare — that's signal.
2. NPS by vertical: Which industries have the highest net promoter scores? Customers who love you most are usually the ones your product fits best.
3. Expansion revenue by vertical: Which industries upgrade to higher plans, add seats, or expand usage? High expansion means the product is delivering real value.
4. Sales cycle length by vertical: Which industries close fastest? Fast closes mean less education required — the product already speaks their language.
5. Churn by vertical: Which industries stay longest? High retention = product-market fit.

Run this in your CRM or billing tool. The dominant vertical usually emerges clearly from two or three of these signals aligning.

Going vertical without abandoning other customers

The "powered by" strategy: keep the horizontal product, build vertical packaging on top.

• Create a vertical landing page: "Nucleus PM for Construction Teams" — AIA phase templates, RFI tracking, subcontractor permission model
• Build 2–3 vertical-specific features that matter for that industry (these aren't new features; they're config options, templates, and integrations you already have or can build in a sprint)
• Create 3 case studies with logos from the target industry
• Write sales collateral (one-pager, demo script) that uses the vertical's language and pain points

Existing customers in other industries keep their accounts unchanged. You're not re-platforming — you're adding a vertical front door to the same product. The CEO's fear of "leaving money on the table" is valid in theory; in practice, the vertical motion generates enough incremental revenue that the other industries become nice-to-haves, not anchors.

Building a competitive moat in a vertical

Once you've chosen a vertical, moat-building moves:

• Industry-specific integrations: Connect to the tools that vertical already uses. Architecture firms use Procore for construction management. Integration with Procore is table stakes for the vertical leader.
• Compliance and certification terminology: Healthcare needs HIPAA-aware language and audit trails. Finance needs SOC 2. Know what compliance signals matter in your vertical and build or market them.
• Language and terminology: Use the industry's vocabulary in every touchpoint. Architecture firms don't have "sprint phases" — they have SD, DD, CDs, and CA phases. Using their language signals deep understanding.
• Logos and case studies: Five known logos in a vertical are worth more than 50 logos scattered across industries. Win recognizable names even at discount to get the references.

The messaging shift and how to test before committing

Old: "Workflow tool for any team." New: "The workflow tool for architecture firms."

To test before fully committing:

• Build a vertical landing page and run paid search against it for 30 days. Budget: $2,000–3,000. Measure conversion rate vs. your horizontal page.
• A/B test your homepage headline with a vertical-specific version to any architecture or construction traffic you already get.
• Run 5 sales calls with the new vertical pitch and track objection rate vs. your current pitch.

If the vertical page converts better and sales calls close faster, commit. Rewrite the homepage, redirect the narrative. You've validated it.

Rollout sequence

1. Choose one vertical based on your data analysis. Don't split attention.
2. Win 10 logos in that vertical, even at reduced pricing for the first 5. These are your reference customers.
3. Build the playbook: document why they bought, what features they use, what objections came up. This is your vertical sales playbook.
4. Hire or retrain one sales rep specifically for the vertical. Give them the playbook and a target account list sourced from industry associations and LinkedIn.
5. Expand to a second vertical only after the first is generating predictable, repeatable pipeline. Usually 12–18 months after the initial vertical launch.

The pattern: one vertical, done right, breaks through the $3–5M ceiling. Two verticals, done halfheartedly, keeps you stuck.

The "wrong tool for the job" positioning frame

Salesforce is one of the most successful enterprise software companies in history. You will not beat them by attacking their reputation, their reliability, or their market position. You'll beat them by making one argument clearly and repeating it until it sticks: Salesforce is built for sales teams. Your product is built for [your specific use case].

This reframes the competitive choice entirely. The prospect isn't deciding between your product and Salesforce — they're deciding whether to use a general-purpose enterprise platform for a specialized job, or to use a tool purpose-built for that job. Most people intuitively understand that specialized tools outperform generalist ones for specific tasks. They use a screwdriver for screws even when they own a Swiss Army knife.

The positioning statement: "Salesforce is the industry standard for sales pipeline management. [Your product] is purpose-built for [your use case] — which is why [your specific users] get [specific outcome] without the overhead of configuring a sales CRM to do something it wasn't designed for."

Never position as "the better Salesforce." Position as "the right tool for this specific job."

The "buy vs. build on top of" argument

Prospects at Salesforce-heavy companies often raise this: "We could just build this in Salesforce." Address it directly and early — don't wait for it to surface as an objection.

The counter-argument has two parts:

1. Build cost is always underestimated. Building a specialized workflow on Salesforce requires custom objects, Apex development or an admin with Flow expertise, ongoing maintenance, and a Salesforce admin's time. The fully-loaded cost of "building it in Salesforce" is typically 3–10x what the prospect estimates. Make this concrete: "We've seen teams spend 200+ hours building this in Salesforce and then 20+ hours/month maintaining it. At $100/hour loaded cost, that's $20,000 to build and $24,000/year to maintain. Our Enterprise plan is $18,000/year and includes everything."

2. Salesforce builds are rarely fully-functional. Custom Salesforce implementations for non-sales workflows tend to be brittle, hard for end users to navigate, and abandoned when the admin who built it leaves. Specialized tools are adopted because they're designed for the user — not for the system.

3 positioning moves for competing with a category leader

1. Own the category niche they don't serve well. Salesforce is exceptional at sales pipeline management. It's mediocre at everything else — customer success workflows, post-sales project management, implementation tracking, partner management. Identify where your users live in that "everything else" space and name the niche. "The CRM for post-sales teams" or "The customer success platform for implementation-heavy SaaS" creates a category that Salesforce visibly doesn't own.

2. Attack their complexity and cost. Salesforce's enterprise pricing and configuration complexity is a genuine liability for mid-market companies. Lean into it: "Salesforce implementations take 3–6 months and require a dedicated admin. Teams are up and running in [your product] in an afternoon." Make your setup time and total cost of ownership a feature, not a footnote.

3. Ally with the Salesforce ecosystem. Build a Salesforce integration and position it as a selling point: "Works alongside Salesforce — your sales team keeps their tool, your [specific team] gets a tool built for how they work." This defuses "we're standardizing on Salesforce" immediately. You're not asking them to replace Salesforce — you're adding a specialized layer. Integration as a feature is one of the most underused competitive moves against a dominant platform.

Handling "we're standardizing on Salesforce"

This objection comes from procurement, IT, and executives focused on portfolio rationalization. The person saying it is often not your champion — they're the buyer who owns vendor relationships. Your champion is the person who will actually use the product daily.

Separate the conversation:

• With the champion (VP Customer Success, Head of Implementations, etc.): focus on workflow fit, time savings, and user experience. Get them to feel the product's value before the procurement conversation happens. Champions who believe in the product create internal pressure to get exceptions to "standardization" policies.
• With the buyer (IT, procurement, CFO): address integration, security, and total cost of ownership. Show the Salesforce integration. Quantify the cost of forcing their team to use Salesforce for something it wasn't designed for.

The argument that lands with buyers: "We're not replacing Salesforce — we're filling a gap it doesn't cover. Forcing your [customer success / implementations / partner] team to use a sales CRM for their workflow generates real productivity cost. This is the specialized tool that closes that gap."

Proof point strategy

You need two types of case studies to compete with Salesforce:

1. Customers who use both (the most common scenario): "We use Salesforce for sales and [your product] for [use case]. Having the right tool for each job saves our team 8 hours/week." These are the most credible stories because they eliminate "but you'd be replacing Salesforce."

2. Customers who switched from Salesforce for the specific use case: these are harder to find but extremely powerful. "We tried to manage [use case] in Salesforce for two years. We switched to [your product] and cut process overhead by 40%." Include specific ROI numbers — time saved, error rate reduction, or revenue impact.

One case study with specific ROI numbers beats ten testimonials. Prioritize getting a design partner who will go on record with a number.

The sales motion

• Never trash Salesforce. Prospects who love Salesforce will disengage. Prospects who are frustrated with Salesforce will tell you — let them.
• Acknowledge Salesforce's strengths in the demo: "For sales pipeline management, Salesforce is genuinely the best. What we're solving is [your specific use case] — which Salesforce can technically do, but not the way your team actually works."
• Let the product demo carry the competitive argument. If your product is visually cleaner, faster to navigate, and obviously designed for the user's actual workflow, the comparison speaks for itself without you saying a word against Salesforce.
• Use the demo to find the moment where the prospect says "we can't do that in Salesforce." That moment is your close. Return to it at the end: "You mentioned you can't [X] in Salesforce. That's exactly what we built this for."