A clear investment to start well and keep evolving.

Who it is for

Teams that need a technical review or a scope definition before implementing.

Includes

• Workshops with the people who know the process.
• Manual review of the relevant configuration, data and integrations.
• Prioritized risks and a backlog with acceptance criteria.
• High-level architecture and a phased roadmap with estimated investment.

Your team provides

• Read access to the systems involved.
• People available for the workshops.

Not included

• Fixing or building the solution; that is agreed as the next phase.
• Third-party licenses, consumption and infrastructure.

Acceptance criterion

You receive the agreed deliverables in writing. If you continue with Nyxum, what was already delivered is not charged again in the implementation.

Who it is for

A company starting on Salesforce with a defined sales process, a business owner and prepared data.

Includes

• One Salesforce org, one country and up to 15 internal users.
• One sales pipeline and its stages.
• Configuration of accounts, contacts, leads and opportunities.
• Up to three roles and three permission sets on an agreed model.

Your team provides

• Licenses and environment available before starting.
• Clean data delivered in the agreed templates.
• A process owner and key users available to validate.
• Timely approval of stages, fields, security and criteria.

Not included

• ERP, API or custom external system integrations.
• Complex migration, bulk cleansing, attachments or multi-source history.
• CPQ, Revenue Cloud, multiple countries or multiple orgs.
• Custom code or redesign of several processes.

Acceptance criterion

The agreed sales flow runs end to end, the tests are documented and your team's owner accepts the scope.

Who it is for

A team that needs to move from scattered service to a defined flow for intake, assignment and resolution.

Includes

• One Salesforce org, one country and up to 15 internal users.
• One case process, with agreed statuses and priorities.
• Up to two service queues.
• One email intake channel through Email-to-Case.

Your team provides

• Required licenses and features available.
• Mailbox and Knowledge content prepared.
• A service owner and key agents available.
• Defined priorities and escalation.

Not included

• Telephony or CTI, a full contact center and WhatsApp.
• Field Service, advanced omnichannel and bots.
• External integrations, custom automation and complex historical migration.
• 24×7 support operations by Nyxum.

Acceptance criterion

A test case comes in, is assigned, handled and closed with traceability, and your team validates the process.

Who it is for

An organization that already has Salesforce, usable data and a bounded case with a business owner.

Includes

• One agent and one use case.
• One flow and one bounded action.
• Data already available in Salesforce.
• One agreed test channel or interface.

Your team provides

• Enablement, licenses and consumption contracted where applicable.
• Access to a test environment and to the permitted data.
• Sufficiently prepared data and an available business owner.
• Approval of the use case and the authorized actions.

Not included

• New Data Cloud configuration.
• External integrations and new APIs.
• Extensive cleansing of data or the knowledge base.
• Multiple agents, channels, cases or actions.
• Any commitment to autonomous operation in production or 24×7 coverage.
• Third-party licenses, consumption, infrastructure and services.

Acceptance criterion

Evidence of behavior against the agreed scenarios and a documented decision on the next step.

First deliverable

Portal users, processes and access model defined and approved.

What changes the effort

Scope depends on the type of users, the access model, the design and the integrations.

First deliverable

A real inventory of what is there, prioritized risks and a phased correction plan.

What changes the effort

Scope depends on technical debt, the volume of automations and data quality.

First deliverable

A production plan with permissions, oversight, metrics and exit criteria.

What changes the effort

Scope depends on the number of actions and channels, the data, security and operational needs.

First deliverable

Sources, quality, identity and activations defined for your case, with an agreement on who configures what.

What changes the effort

Scope depends on sources, data quality, identity, activations and consumption.

First deliverable

A map of the data and processes that must flow between systems, with the proposed integration architecture.

What changes the effort

Scope depends on the systems, the available APIs, the data volume and whether MuleSoft or another alternative fits the case.

First deliverable

Target process and data model agreed for the chosen cloud.

What changes the effort

Scope depends on the cloud, the processes, pricing or dispatch rules and the integrations.

First deliverable

Mapping of the current model to the industry cloud and a phased migration roadmap.

What changes the effort

Scope depends on the industry cloud, the current model, the data to migrate and the integrations.

Who it is for

Teams with a focused use of Salesforce and few change requests.

Includes

• 24 hours of combined capacity per month.

Who it is for

Teams with several departments on Salesforce and an active enhancement backlog.

Includes

• 50 hours of combined capacity per month.

Who it is for

Organizations that need architecture judgment and sustained enhancement capacity.

Includes

• 100 hours of combined capacity per month.

Who it is for

Teams that already lead their platform and need to add architecture, consulting or development.

Includes

• Salesforce architects, consultants or developers who join your team.
• Goals, deliverables and commitment agreed in writing.

Your team provides

• An owner on your side who prioritizes the work.

Not included

• Third-party licenses, consumption and infrastructure.

Who it is for

Organizations that want agents on their own systems, without being tied to a vendor.

Includes

• One flow and one bounded action on your systems, through APIs or MCP.
• Tests with success criteria defined together and human review.
• Close with evidence and a recommendation: scale, adjust or stop.

Not included

• Third-party licenses, model consumption and infrastructure.

Who it is for

Organizations that want to organize their use cases before building.

Includes

• Inventory of candidate processes, scored by value, risk and data readiness.
• Prioritized use cases, with owners and success criteria.
• A 90-day roadmap with estimated investment per phase.

Not included

• Building the use cases; agreed as a next phase.

Who it is for

Organizations that need a data foundation they can explain.

Includes

• Data model, catalog and owners per domain.
• Access, quality and retention policies your team can apply.
• Reference architecture and documented decisions.

Not included

• Third-party licenses and infrastructure.