Built for buyers choosing between packages in a catalog

When a vendor sells multiple CRM packages, the real question is which one fits the way your team actually sells.

A CRM package catalog is a shelf of SKUs. Each SKU bundles a slightly different capability set at a slightly different price. Picking the right one depends less on the headline features and more on the motion the team runs: inbound-led, outbound-led, account-centric, deal-centric, service-blend, field-blend. This page walks the Strkr catalog honestly and names which package suits which motion.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Buyers who approach a CRM package catalog usually face a familiar set of friction points. The SKU descriptions are written by marketing and emphasize different capability sets than the operator actually needs. The pricing columns look parallel on the pricing page and diverge once a real workflow lands on them. The pains below are what buyers describe when they ask us to walk the catalog from the operator side rather than the brochure side.

SKU descriptions emphasize marketing anchors

The headline features do not match the operator question.

Catalog pages tend to lead with headline features (unlimited pipelines, AI assistant, custom reports) rather than operator-shaped questions (does the forecast methodology match how we commit, does the inbox integration land threads on the account view, does the mobile work in the field). Buyers end up translating marketing text to operator reality on their own, which is slow and error prone.

The pricing columns look parallel

Pro at vendor A and Pro at vendor B are not the same shape.

Pricing pages render as grids with Starter, Growth, Pro, Enterprise columns across vendors. The grids look parallel. In practice the Growth tier at one vendor includes capability that lives on Pro at another, and the Pro tier at a third gates compliance features that the second ships on Starter. Comparing packages across vendors requires reading the fine print of each SKU rather than the column names.

Industry packages are brochure, not SKU

The "CRM for consultants" page is marketing, not a different SKU.

Many catalogs show industry packages (CRM for real estate, CRM for consultants, CRM for construction) that look like SKUs but are actually the standard SKU plus some templates and preset dashboards. The industry label is a marketing anchor, not a different package. Buyers who think they are buying a different thing are usually buying the same thing with different seed data.

The right SKU depends on motion, not size

A 20-rep inbound team needs a different package than a 20-rep field team.

Catalog shelves tend to tier by team size. The actual decision depends more on the sales motion. A 20-rep inbound-led team needs lead capture and routing; a 20-rep field team needs mobile with offline queue; a 20-rep account-centric team needs the account-first object model. Picking the SKU by seat count misses the motion fit.

Add-on math obscures the SKU comparison

The quoted SKU plus three add-ons lands at a different price.

The headline SKU price often excludes the lead capture add-on, the document add-on, the project add-on, the forecast add-on, and sometimes the AI add-on. Comparing the SKUs on the catalog is not comparing the final invoice line. The all-in math per rep per month lands anywhere from 1.3x to 2.5x the headline SKU rate depending on how many add-ons the motion needs.

Catalog maintenance decays over time

The catalog from 18 months ago has drifted from the current product.

CRM catalogs tend to accumulate SKUs over time as sales teams discover edge cases and marketing adds variants. The current state is sometimes a legacy SKU that is still orderable, a current SKU that is the recommended path, and a deprecated SKU that is quietly being wound down. Buyers who find a legacy SKU on an old blog post or review site end up with outdated expectations.

The Strkr package catalog

The SKUs Strkr sells and which motion each one fits.

Strkr intentionally keeps the catalog narrow: three primary packages, with industry variants that are template bundles rather than separate SKUs. The cards below name each package and the motion it was designed for, so the operator can map against their own team shape.

Core CRM package

The full sales workflow for a growing team.

Core bundles the sales workspace: the full object graph, the methodology-driven forecast surface, Strkr AI, the account-level inbox view, lead capture plus scheduling, documents, cohort-shaped reporting, mobile, Flows for automations, the native connector set, and the full compliance posture. The buyer this fits: a 5 to 100 seat sales team tired of climbing tier ladders and watching add-on invoices accumulate.

Suite package

Core CRM plus Marketing, Messaging, Projects, Docs modules.

The Suite package adds the Strkr Marketing module (email broadcast, drip, nurture, landing pages), Strkr Messaging (SMS and MMS through the integration layer), Projects (post-sale project tracking with the issue model), and Docs (the shared workspace for team knowledge). The intended fit is a 20 to 150 seat team running sales plus marketing plus post-sale delivery on one platform.

Enterprise package

Suite plus data residency, dedicated support, custom contracting.

The Enterprise package adds data residency controls (region selection, data processing agreements with specific terms), dedicated technical account management, custom contracting with legal review, custom SLAs, and the full compliance baseline for teams handling complex regulatory posture. The intended fit is a 100 plus seat team with security review, procurement, and vendor management processes.

Startup package

Core CRM at a reduced per seat rate for funded early-stage.

The Startup package is Core CRM at a reduced per seat line for registered startups with less than 10 million dollars in funding. The package capability is identical to Core; the discount applies at the seat line. The intended fit is pre-Series B companies building their sales motion for the first time, with 1 to 20 seats scaling fast.

Nonprofit package

Core or Suite at a reduced per seat rate for registered 501(c)(3).

The Nonprofit package is Core or Suite at a reduced per seat line for registered 501(c)(3) nonprofits. The package capability is identical to the standard SKU; the discount applies at the seat line. The intended fit is nonprofits running donor relations, program management, or grant tracking workflows that map cleanly to the CRM shape.

Custom Enterprise

Scoped against specific procurement and compliance terms.

Beyond the standard Enterprise package, teams with specific procurement constraints (government contracting, large regulated industries, specific country data residency requirements, custom SLA terms) can scope a Custom Enterprise package with the Strkr procurement team. The intended fit is teams whose purchasing processes require custom terms the standard catalog does not accommodate.

Industry variants inside the catalog

Template bundles that layer on top of the SKU.

Rather than creating industry-specific SKUs, Strkr ships industry variants as template bundles that apply inside the chosen package. The template bundle configures the field catalog, picklist values, dashboards, and automations for the motion, so the operator does not start from an empty tenant. The cards below describe the common variants.

B2B SaaS variant

Pipeline stages, MRR fields, cohort reports, product usage link.

The B2B SaaS variant seeds the pipeline with stages tuned for SaaS sales (discovery, demo, trial, procurement, closed-won). MRR, ARR, contract term, and renewal date are first-class fields on the deal. Cohort dashboards for new logo and expansion. Native connector seed for Stripe, Snowflake, and the product analytics platform of choice. Variant applies inside Core or Suite.

Agency and services variant

Project link, retainer model, time-and-materials tracking.

The agency variant seeds the pipeline with services-sales stages (brief, scope, proposal, SOW, kickoff). Retainer and T-and-M fields on the deal. Project link from closed-won to the Projects module. Quote generation with the services template library. Variant applies inside Suite specifically because the Projects module carries the post-sale delivery.

Field services variant

Mobile-first config, visit scheduling, service agreement renewals.

The field services variant seeds the pipeline with field motion stages (lead, site visit, estimate, agreement, service start). Mobile-first configuration with voice capture and offline queue tuned for field reps. Service agreement renewal tracking. Scheduler surface configured for field appointment booking. Variant applies inside Core or Suite.

Life sciences variant

HIPAA-aware config, compliance audit, provider directory.

The life sciences variant seeds the tenant with HIPAA-aware default configurations (audit log retention tuned, data residency defaults, specific field encryption posture). Provider directory structure on the account record. Call reporting fields tuned for pharma rep motion. Variant applies on top of Core or Suite with the HIPAA BAA in place as standard.

Real estate variant

Property record, buyer and seller workflow, commission split.

The real estate variant seeds the tenant with property records on the account structure, buyer-side and seller-side workflow configurations, commission split tracking on the deal, and MLS integration points through the HTTP action node. Variant applies inside Core.

Nonprofit and donor variant

Donor record, giving history, grant pipeline, program tracking.

The nonprofit variant seeds the tenant with donor records on the contact structure, giving history as first-class activity, grant pipeline on the deal model, program tracking through custom objects, and board-facing dashboards. Variant applies inside the Nonprofit package specifically.

How to pick the package that fits

An operator-shaped decision framework.

The catalog cards above describe the SKUs. The cards below walk the actual decision an operator faces: which SKU for which shape of team, which variant on top, and when to call sales rather than self-serve.

Pick Core when...

The team runs sales only on one platform.

Core fits when the team runs sales on Strkr and keeps marketing, service, phone, and other adjacent motions on their existing tools (or does not have them yet). The 5 to 100 seat sales team doing inbound-led, outbound-led, or account-centric motion with a predictable pipeline shape is the primary Core buyer.

Pick Suite when...

The team wants sales plus marketing plus delivery on one platform.

Suite fits when the team runs sales plus email marketing plus post-sale delivery (project tracking or ongoing service) and wants one platform rather than three. The 20 to 150 seat team with a growth motion that spans acquisition and delivery is the primary Suite buyer. The Projects module specifically pulls teams from Jira or Asana for post-sale work.

Pick Enterprise when...

Procurement or security review needs custom terms.

Enterprise fits when the team is 100 plus seats, has a procurement process that requires DPA review, needs data residency controls, wants dedicated TAM, or needs custom SLA terms. The compliance baseline is the same across packages; Enterprise adds the contracting and support surface, not the capability.

Pick Startup when...

The team is pre-Series B and growing fast.

Startup pricing fits early-stage companies with less than 10 million dollars in funding, 1 to 20 seats, and a sales motion still being built. The package capability is identical to Core. The discount applies at the seat line. Teams that cross the funding threshold migrate to Core without a reconfiguration.

Pick Nonprofit when...

The organization is a registered 501(c)(3).

Nonprofit pricing fits registered 501(c)(3) organizations running donor relations, program management, or grant workflows. Core and Suite are both available at the discounted rate. The nonprofit variant template bundle configures the tenant for donor and grant workflows out of the gate.

Call sales when...

Custom procurement, large seat count, or regulated industry.

The sales conversation is useful when the team is 100 plus seats, has specific procurement constraints beyond the standard DPA, operates in a regulated industry with specific compliance requirements, or wants to compare multi-year commitment math. Self-serve purchase stays available for 1 to 100 seat teams on Core or Suite.

Head-to-head

Strkr catalog versus the typical CRM catalog shape.

Below is the comparison of how the Strkr catalog is structured versus how a typical CRM catalog is structured. The point is to make the catalog navigation easier, not to pick on any specific vendor.

Feature Strkr Typical CRM catalog
Number of primary SKUs 3 primary (Core, Suite, Enterprise) plus Startup and Nonprofit 4 to 6 tier ladder (Free, Starter, Growth, Pro, Enterprise, Unlimited)
Capability variance across tiers Compliance and capability consistent; Suite adds modules Capability gated per tier, substantial variance
Industry packages Template bundles applied on top of the SKU Separate industry pages, usually same SKU with seed data
Add-on modules Marketing, Messaging, Projects, Docs bundled in Suite Lead capture, docs, projects, forecast often as per-seat add-ons
AI metering Plan credit pool with no per-conversation meter below cap Credit meter or add-on tier
SSO and SCIM Every paid tier Often Enterprise only
HIPAA BAA availability Every tier Enterprise or not available
Startup discount program Available for pre-10M funded startups Varies by vendor
Nonprofit discount program Available for registered 501(c)(3) Varies by vendor
Self-serve seat count ceiling 1 to 100 seats self-serve on Core or Suite Varies; often sales-touch required at 10 to 25 seats
How teams use Strkr

How teams actually navigated the catalog before buying.

The common pattern: buyers walked the catalog, identified the motion their team actually runs, picked the SKU that matched that motion, and layered the appropriate variant on top. The playbooks below are live customer motions through the catalog.

B2B SaaS, 42 reps

Started on Core with the SaaS variant; added Marketing module at month 9.

A 42-rep B2B SaaS team started on the Core package with the SaaS variant template bundle. The pipeline stages, MRR fields, and cohort dashboards were seeded from the variant. The team ran Strkr for sales for 9 months, kept HubSpot Marketing Hub for marketing. At month 9 they decided to move marketing onto Strkr for the sales-marketing unification and upgraded to Suite. The upgrade was a billing change rather than a reconfiguration, which the team specifically chose Strkr for over a vendor whose Marketing module required a different SKU.

Services firm, 28 account managers

Picked Suite directly for the Projects module and the services variant.

A 28-AM services firm evaluated Core versus Suite and picked Suite directly because the Projects module replaced the Jira seat line for post-sale delivery. The services variant seeded the pipeline, retainer fields, and quote templates. The Jira cost (roughly 400 per month at the team's seat count) rolled into the Suite line, which made the all-in math roughly flat but consolidated two renewals into one.

Field services, 24 technicians plus sales

Picked Core with the field variant for mobile-first config.

A 24-tech field services firm picked Core with the field services variant. The variant seeded the mobile-first configuration, voice capture defaults, offline queue, visit scheduling, and service agreement renewal tracking. The team did not need Marketing module or Projects module; sales plus field motion fit cleanly in Core.

Early-stage startup, 6 reps

Started on Startup package; migrated to Core at Series B.

A 6-rep early-stage startup qualified for the Startup package (pre-10M funding, under 20 seats). The team ran on Startup for 14 months. At Series B they crossed the funding threshold and migrated to Core at the standard per seat rate. The migration was a billing change with no reconfiguration; the full capability had always been identical to Core.

Mid-market B2B, 95 reps

Started on Suite; moved to Enterprise after legal required a custom DPA.

A 95-rep mid-market B2B team started on Suite for sales plus marketing plus Projects. At month 11 their legal team required a custom DPA with specific data processing terms, data residency selection, and custom SLA language. The team moved to Enterprise for the custom contracting surface. The capability stayed the same; the contracting posture changed, and the dedicated TAM for the renewal cycle was useful during the DPA negotiation.

The CRM catalog without the SKU theater.

Start a 14-day Strkr trial on Core or Suite with the full capability turned on. Decide which package fits once the team has run the real workflow for two weeks.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What packages does Strkr sell?

The catalog is deliberately narrow. Three primary packages anchor it (Core, Suite, Enterprise) plus two program-driven discount lines (Startup for pre-10M funded companies, Nonprofit for registered 501(c)(3) organizations). Core is the sales workspace bundle for growing teams. Suite layers Marketing, Messaging, Projects, and Docs modules on top of Core for teams running sales alongside marketing campaigns and post-sale delivery on one platform. Enterprise handles the contracting surface (data residency region choices, dedicated TAM, legal-reviewed custom DPA, custom SLA terms) that 100 plus seat teams and procurement-driven organizations tend to need. Industry variants (SaaS, agency, field services, life sciences, real estate, nonprofit) are not separate SKUs; they are template bundles that configure the chosen primary package with industry-appropriate seed data, dashboards, and automations.

How do I pick the right package for my team?

The decision depends more on sales motion than on seat count. Pick Core when the team runs sales only on one platform and keeps adjacent motions (marketing, service, phone) on existing tools. Pick Suite when the team wants sales plus marketing plus post-sale delivery (project tracking, ongoing service, team knowledge) on one platform. Pick Enterprise when procurement requires custom DPA or data residency, when seat count is 100 plus with vendor management overhead, or when the compliance posture needs custom SLA terms. Pick Startup if the company is pre-Series B with less than 10M in funding. Pick Nonprofit if the organization is a registered 501(c)(3). The capability is consistent across the primary packages; the difference is which modules bundle in and which contracting surface applies.

What is the difference between industry variants and industry packages?

Industry variants are template bundles applied on top of the chosen package. A B2B SaaS team on Core gets the SaaS variant seeded (SaaS pipeline stages, MRR fields, cohort dashboards). A services firm on Suite gets the services variant seeded (services stages, retainer fields, Project template library). The variant does not change the SKU or the price; it changes the seed data and the default configuration. This is intentionally different from vendors who sell separate industry packages, where the catalog shows "CRM for X" and "CRM for Y" as separate SKUs that are usually the same underlying product with different brochure pages. Strkr's approach: one package per motion, variants for industry seed data.

Can I upgrade from Core to Suite without reconfiguration?

Yes. The upgrade from Core to Suite is a billing change that turns on the additional modules (Marketing, Messaging, Projects, Docs) inside the existing tenant. The sales object model, forecast, Strkr AI, inbox, and other Core capability stays identical. The Marketing module arrives with its own template library and admin surface; the Projects module links to deals and accounts cleanly; the Messaging surface activates through the integration layer. Teams typically do the upgrade in a 2 to 4 week window with admin setup for the new modules, rather than a full reconfiguration. Downgrading from Suite to Core also stays available; the modules deactivate and the Core workflow continues untouched.

Is there a free package or free tier?

Strkr does not run a permanently free tier. There is a 14-day free trial of the Core package that turns on the full capability (sales objects, forecast, Strkr AI, inbox, scheduler, documents, cohort reporting, mobile, Flows, integrations) so the team can run a real evaluation. After the trial the team upgrades to Core or Suite at the standard per seat line. The intent is that the trial is honest (full capability, enough time to run a real pilot) rather than a limited free tier that nobody can actually run a sales team on. For teams who want permanent reduced pricing, Startup and Nonprofit programs apply at the seat line.

How does Enterprise differ from Suite?

The capability (the actual product features for the sales day) is largely the same between Suite and Enterprise. Enterprise adds the contracting and support surface: data residency controls (region selection, specific data processing terms), dedicated technical account management, custom contracting with legal review, custom SLA terms, custom DPA negotiation, and the full compliance baseline tuned for teams with heavy regulatory posture. Buy Enterprise when procurement needs those terms specifically; buy Suite when the standard terms and standard SLA are acceptable. Both share the Strkr AI model router, the inbox integration, the forecast methodology, and the compliance baseline (HIPAA with BAA, SOC 2 Type II in progress through 2026-Q4, GDPR, CCPA, SSO, SCIM).

Also built for

Related audiences.

What is in a CRM package CRM plan comparison Pick a CRM plan CRM pricing

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing