Platform subscription
Core CRM, prospecting, buyer-intent review, sequences, pipeline, users, admin boundary, and included support.
Pricing and implementation
Know the pricing model before the numbers.
Pursenda pricing is presented as an evaluation model on this staging site: platform subscription, usage allowance, launch configuration, and optional services. Public dollar figures, limits, and contract terms remain owner-approved slots.
Pricing components
Four pieces should be visible before a buyer commits.
The packet calls for pricing logic, examples, optional services, terms, and an implementation checklist. This page names the pieces without inventing unapproved dollar amounts.
Usage allowance
Credits or metered actions, included quantity, reset period, rollover, alerts, hard caps, top-ups, and overage behavior.
Launch configuration
One-time guided setup for the agreed first version: motion mapping, configuration, migration, training, and launch verification.
Optional services
Custom integrations, data cleanup, advanced workflow design, reporting, or ongoing optimization quoted separately.
Feature and limit matrix
What each scoped recommendation should answer.
These rows are the buyer-facing comparison surface. The exact public values need owner approval before launch.
AreaIncluded in platformOwner-approved value needed
Users and rolesNamed users, team views, basic role boundaries.Billing unit, user limits, admin/security differences.
CRM + pipelineAccounts, contacts where supported, opportunities, stages, owners, next actions, outcomes.Object limits, field limits, report limits, support boundary.
Prospecting and signalsFocused lists, source category, freshness, confidence, reason codes.Included usage allowance, source availability, geography limits, top-up/overage behavior.
Sequences and tasksConfigured follow-up steps, human tasks, reply-aware workflow where supported.Channel support, send limits, deliverability controls, suppression requirements.
Security and adminTrust review path and current control matrix.Production access model, audit logging, certifications, DPA and subprocessor terms.
Sample total cost scenarios
Use ranges only after the owner approves them.
The structure is public; the prices are intentionally labelled as pending so finance reviewers can see what will be quoted.
First usable version
One focused sales motion, core account and opportunity objects, one pipeline, scoped import, training, and launch verification.
Owner-approved range neededGrowth team rollout
Multiple users, usage allowance, configured views, sequences, reporting, defined roles, and a controlled migration from spreadsheet or CRM export.
Owner-approved range neededConfigured extension
Optional integration, heavier data cleanup, advanced workflow, or ongoing optimization after the first version is stable.
Separate scope neededImplementation checklist
The launch scope should be explicit.
A scoped recommendation should separate supported configuration from custom work before price or timing is promised.
- Motion mappingBuyers, account types, stages, signals, handoffs, next actions, and outcome definitions.
- Supported configurationObjects, fields, views, roles, sequences, rules, dashboards, and agreed integrations that the product supports.
- Scoped migrationInventory, mapping, cleanup rules, test import, exception list, owner approval, and cutover boundary.
- TrainingTeam walkthrough, role-specific views, operating definitions, and owner handoff.
- Launch verificationReports, permissions, sequence behavior, export route, and open issues checked before wider use.
- Out-of-scope custom workCustom development, nonstandard integrations, heavy data cleanup, and advanced automation quoted separately.
Terms and cancellation gates
Commercial terms are not hidden. They are pending approval.
Before public launch, the owners must approve the billing period, renewal behavior, cancellation effective date, export window, support response terms, taxes, discounts, and overage/top-up rules.
Contract basics
Month-to-month or annual terms, renewal rules, payment timing, taxes, and discount policy need owner approval.
Cancellation
Notice period, effective date, data export window, deletion timing, and post-cancellation access need legal and operations approval.
Usage controls
Included usage, resets, alerts, hard caps, top-ups, overages, rollover, and administrator controls need approved wording.
ROI framing
Business-case assets should use editable assumptions and scenarios, not guaranteed outcomes.
Pricing FAQ
Questions finance and operators will ask.
How is pricing calculated?
A scoped recommendation should combine platform subscription, usage allowance, launch configuration, and optional services. Dollar figures and limits are pending owner approval.
How long does implementation take?
No public implementation-time promise is approved. The timeline should be quoted after motion mapping, migration review, integration review, and user availability are known.
Can you migrate our existing data?
Scoped migration can include inventory, mapping, cleanup rules, a test import, exceptions, and owner approval. Heavy cleanup or unusual systems are optional services.
Can we export our data?
Export and portability are required trust topics. Exact formats, timing, and post-cancellation access need owner/legal approval before launch.
What happens if we cancel?
Cancellation terms, export window, deletion timing, and billing effects are owner/legal gates and must be approved before the commercial product launches.
Are there usage caps or overages?
If usage credits or metered actions are used, the page should show included quantity, reset, rollover, alerts, hard caps, top-up price, overage behavior, and administrator controls.
What changes cost?
User count, usage volume, data condition, migration size, integration depth, workflow complexity, training needs, and custom work can change the total scope.
Next step
Get the recommendation before the commitment.
Bring your current sales process, data source, team shape, and the systems that must stay connected.