Marketing runs the campaign, Sales never sees the lead
Marketing Cloud sends the journey, Sales Cloud cannot see the engagement. Two systems, two truths about the same customer, and nobody couples campaign to pipeline.
Salesforce consulting
Salesforce as a platform:
9 clouds, 5 stages, one governed CRM
Bunker starts from the diagnosis of the business problem. The Bunker Protocol opens with a Structural Diagnosis: mapping where the operation loses revenue and predictability, and only then deciding which cloud comes in, in what order and under which rule.
The Salesforce platform by the numbers
#1
in global CRM for 12 consecutive years. The platform is today the institutional default for companies that sell with method.
IDC 2025150K+
companies use Salesforce worldwide, including 90% of the Fortune 500. Betting on enterprise CRM means betting on Salesforce.
Salesforce Investor Relations FY2520,7%
of the global CRM market. More CRM revenue than Microsoft, Oracle, Adobe and SAP combined.
IDC Worldwide CRM Market Share 20246.233
apps on the AppExchange with more than 10 million installs. The densest operational ecosystem in the CRM market.
Salesforce AppExchange, Dec 2025The symptoms
Four symptoms of a CRM running as a stack of clouds
Each one looks operational on its own. Together, they show the problem is one of operating model.
Customer data in four versions
The customer is one thing in Sales, another in Service, another in Marketing, another in the ERP. The decision changes depending on which system you open first. Data Cloud exists to settle that, and it has to be governed before it is switched on.
An AI agent as brand liability
Agentforce switched on with no guardrails, answering what it should not, promising what it cannot. AI without governance is not an asset: it is brand liability at scale.
The forecast is still subjective
CRM Analytics and Tableau full of dashboards, and the forecast meeting still decides on gut feel. Visualization without traceability does not help you decide, it only gives comfort.
CRM as a Governed Platform
Bunker
We have worked inside operations like these. The problem is not Salesforce: it is the adoption model.
CRM platforms do not stop evolving because of a technical ceiling. They stop because each cloud was treated as an isolated project, with its own SI and its own data. The platform ends up as a sum of implementations, with no operating model on top.
Bunker delivers a governed CRM: each cloud installs a model, and all of them run under one standard.
- 300+ organizations supported in Salesforce environments
- 10+ years across Sales, Service, Marketing, Data, AI and integration
- The Fit to High Standards standard applied across every cloud
- Short delivery cycles, with no perpetual dependence on an SI
When each cloud comes in
The customer journey runs through 5 stages. Bunker decides which cloud installs each part of the model.
First, a foundation. Then, in sequence: attract, engage, decide, serve and grow. Each stage calls one or two clouds; none of them runs alone.
0
Foundation: a single customer before any cloud
Before Marketing, Sales or Service, Data 360 unifies the customer across CRM, ERP, web and ecommerce. Without that foundation, each cloud sees only itself and the decision changes depending on which system you open first.
Bunker sets up quality, lineage and audit governance in Data Cloud before switching on a campaign, an approval threshold or an AI agent. The data takes on the role of decision infrastructure for the whole CRM.
I
Attract: before the lead exists
Marketing Cloud orchestrates the discovery journey with messaging that reinforces price perception. Communication built on unified Data 360 data, segmentation by persona and channel, and automation that respects commercial policy and protects margin.
In a consumer goods operation supported by Bunker, communication was restructured before any journey: positioning by channel, messaging by persona, data coming from Data Cloud. Marketing came to be measured by margin.
II
Engage: qualify without inventing
Agentforce puts an AI agent to qualify leads under a declared threshold, with contractual guardrails and an impact metric. The intent score comes out of data and business rules.
In a recent operation, Bunker designed a pre-sales agent that cut 44% of the qualification effort, with mandatory human review. It is not a chatbot: it is an operating system under a declared threshold that records traceable evidence.
III
Decide and buy: a governed pipeline
Sales Cloud runs the pipeline with commercial policy, approval thresholds and CRM Analytics coupled in. Commerce Cloud delivers B2B self-service under the same policy as the direct channel: no channel conflict and no discount race. A forecast backed by data.
In a high-complexity org supported by Bunker, more than 1,400 Apex classes and hundreds of Flows run under a governed Salesforce DX cycle out of the F2HS environment: a proprietary sandbox with complete CRM, pull request, code review, QA and production under a 75% minimum test coverage.
IV
Serve: the customer arrives with context
Service Cloud runs the account cycle with governed cases and commercial context. Slack couples the conversation to the record with structured deal rooms and a document trail: the decision taken in a conversation is recorded as traceable evidence.
In recent Bunker diagnoses, 41 processes were mapped in CMMN 1.1 (the OMG standard) before configuring any flow in Service Cloud. Service runs as an extension of commercial strategy.
V
Grow: expansion measured by margin
CRM Analytics shows the forecast with an error band and margin per deal with traceability. Tableau brings strategic BI crossing external data. Expansion comes out of an identified root cause.
Bunker builds decision-oriented dashboards: forecast with an error band, margin per deal with traceability, channel performance with a visible root cause. Management sees where to act.
What the platform delivers
What the platform lets you manage, measure and compare
Thirty-seven Salesforce capabilities, grouped by what each one delivers to the business: what gets managed by rule, what gets measured with a number, and what gets compared across periods, teams and channels.
CRM users take up less than half of the available features. Finances Online / Tech.co
Manage23
Treat headquarters and branches as one customer
Account and Contact Management
The account supports hierarchy, and Contact to Multiple Accounts lets the same person act across companies in the group. Bunker defines what counts as a corporate group before any record is imported, because fixing it afterwards is manual work.
Keep one catalogue and several prices
Products and Price Books
Price lives at the crossing of product and price book, so the same item carries a price per channel, per region and per contract. Bunker brings the catalogue from the ERP and prevents the third registry that always shows up.
Declare who covers whom
Enterprise Territory Management
Territory defines by rule which account falls into which division and which rep can see it. Bunker designs the model and tests coverage before it goes live.
Define what each level can see
Role Hierarchy
The role hierarchy decides what a manager sees of the team, and groups cover the access that falls outside the pyramid. Bunker writes that design together with the commercial policy.
Give the account an owner
Account Teams
The account team records who answers for it and with what level of access. Bunker uses this to end the good account with no declared owner.
Qualify by a written rule
Lead Management
Lead status is the rule that separates who enters the funnel from who does not yet. Bunker writes the criterion with the sales team, and qualification stops varying by rep.
Give the outreach a rhythm
Sales Engagement
The cadence sets the sequence of touches, the channel and the interval, and records why someone left it. Bunker designs the cadence from what already works in the operation.
Capture activity without relying on typing
Activity Management and Einstein Activity Capture
Task, event and email stay on the record, and automatic capture brings email and calendar in without the rep logging anything. Bunker defines what has to be recorded and what is noise.
Advance the funnel by criterion
Opportunity Management
Each stage carries probability and an exit criterion, and the contact role records who decides, who approves and who uses. Bunker writes the passage criterion before configuring the stage.
Quote with one version that counts
Quotes
Several quotes can exist per deal, and only the synced one mirrors the opportunity line items. Bunker defines who can issue a quote and what has to be filled in first.
Split commission on a shared deal
Opportunity Splits
The deal value divides among the people who took part, and each share counts towards the quota of whoever received it. Bunker sets the splitting rule before switching the feature on, because afterwards each case gets negotiated separately.
Turn the contract into a renewal trigger
Contracts and Orders
The contract holds term, renewal and owner, and the order records what was actually sold. Bunker ties the renewal date to the outreach rhythm, and the contract stops being a filed document.
Know what the customer has installed
Asset Management
The asset is the product in the customer's hands, with serial number and date, and asset relationships show what makes up what. Bunker uses the installed base to design renewal, replacement and expansion.
See what the channel is selling
Partner Relationship Management
The partner enters with a role on the account and on the deal, and the marketing fund records budget, request and reporting. Bunker defines the deal registration that prevents channel conflict.
Approve discount within the authority limit
Revenue Cloud
Configuration, pricing and approval move onto the platform, with contract and billing right after. Bunker writes the discount policy and the authority limits before configuring the rule.
Calculate variable pay on what actually closed
Salesforce Spiff
The commission plan stays versioned, the calculation runs on the order, and the rep sees how much is due and for which deal. Bunker ties the plan to the commercial policy rather than to a monthly spreadsheet.
Distribute quota with simulation
Sales Planning
Planning designs coverage and quota before the year starts, and allows simulation before publishing. Bunker runs that design together with the commercial board.
Plan route and coverage on the map
Salesforce Maps
Routing optimises the visit and territory appears geographically, with market data layered on top. Bunker applies this where selling happens in person and travel weighs on cost.
Set the limits of the AI agent
Agentforce for Sales
Every action the agent may take is declared, the prompt stays versioned, and the Trust Layer masks sensitive data. Bunker defines what the agent handles alone and what requires a person.
Take the agent beyond sales
Agentforce Coworker
The same agent serves other areas, over the same data and under the same rule. Bunker picks where the gain justifies the consumption.
Use a ready-made industry action
Agentforce Industries
Ready actions for healthcare, financial services, manufacturing and telecom. Bunker checks whether the ready action covers the case before commissioning a custom one.
Tie enablement to a result
Sales Programs
The programme defines the track and the milestone, and the CRM measures whether the number moved afterwards. Bunker picks the milestone that matters to the business rather than to the certificate.
Bring the decision to where the conversation happens
Slack Enterprise+
The opportunity updates and the funnel shows up without leaving the conversation. Bunker defines which alerts enter the channel and which stay out.
Measure10
Calculate the forecast from the funnel itself
Collaborative Forecasts
The forecast comes out per person and per period, with the manager's adjustment kept beside the original number. Bunker writes the rule for which stage enters which forecast category.
Track quota against actuals
Quotas and Forecast Types
Quota is loaded in, and the forecast type defines whether the number runs by revenue, by quantity, by product family or by commission split. Bunker picks the type the board actually uses.
Recognise revenue in the month it belongs to
Product Schedules
The line item value spreads across the months of the term, and a twelve-month contract stops appearing as a single month of revenue. Bunker adjusts the forecast to read the contract month by month.
Measure what happened inside the conversation
Einstein Conversation Insights
The call is transcribed and tagged for mentions of competitor, price and objection. Bunker connects that to the loss reason, and the analysis gains a basis beyond what the rep remembered.
Prioritise by calculated probability
Einstein for Sales
The opportunity score comes from the organisation's own history, and the model factor shows what pulled the score. Bunker validates the factors with the team before the score is used as a rule.
Attribute revenue to the campaign
Campaign Influence
The influence model defines how to split credit among the actions that touched the deal. Bunker picks the model before the first report is published, because changing it later changes the history.
Separate reach from response
Campaign Management
The campaign member records one line per person per action, and the member status defines what counts as a response. Bunker standardises that status across the areas.
Measure what the AI consumes
Flex Credits
Every agent action consumes credit, and conversations have a meter of their own. Bunker tracks consumption per use case, and the cost of AI stops being a surprise at month end.
Read revenue in a ready-made dashboard
Revenue Intelligence
The package delivers funnel, forecast and quota analysis as a CRM Analytics app. Bunker adapts the dashboards to the vocabulary the operation already uses.
Analyse on top of already unified data
Tableau Next
The visualisation layer reads Data Cloud directly, with no intermediate copy. Bunker defines which questions justify that depth.
Compare4
Compare the funnel between two periods
Pipeline Inspection
It shows what came in, what left, what changed date and what changed value since the last conversation. Bunker defines which variations trigger a conversation and how often the manager reviews the board.
Compare the sales cycle over time
Field History Tracking
Stage history records one line per change, and it is the source of every trend and cycle-time chart. Bunker picks which fields keep history, because keeping everything carries a cost.
Compare performance across territories
Territory and Coverage
With accounts assigned to territories by rule, the number can be compared across regions and segments. Bunker makes sure the base is assigned before anyone compares.
Compare direct and indirect channel
Opportunity Partners
The partner recorded on the opportunity makes it possible to separate what came through the channel from direct sales. Bunker defines the record that supports that comparison.
Transformation
From a stack of clouds to a governed platform
Buying by cloud
A sum of implementations glued together
- Each cloud with its own SI and its own data
- The customer in four versions across Sales, Service, Marketing and the ERP
- Marketing fires, Sales reacts, Service never sees it
- AI switched on with no guardrail, as brand liability
- Forecast on gut feel, dashboards with no traceability
A governed platform
Sales for the funnel and the forecast. Service for support with a deadline. Marketing for the journey. Data Cloud for a single customer record. Commerce for the order that comes in on its own. Experience for the portal where the customer serves themselves. Revenue Cloud for quote, contract and billing. Field Service for what happens on site. MuleSoft for what comes from the ERP. CRM Analytics and Tableau for reading it. Agentforce for the agent that acts on the record. Slack for the conversation where the decision happens.
- The Fit to High Standards standard across every cloud
- A single customer in Data 360, the same truth at every point
- Marketing, Sales and Service coupled by the journey
- Agentforce agents under a declared threshold and an impact metric
- Forecast with an error band, decisions with a root cause
Frequently asked questions
Questions Bunker answers when a client arrives asking about one cloud
Which Salesforce cloud do I need?
It depends on the operational problem, not on the product menu. Bunker goes the opposite way from the traditional SI: first it maps the model (commercial policy, account cycle, customer data, the AI agent that makes sense), then it defines which clouds come in, in what order, under what rules. The cloud installs the model; it does not create it.
Marketing Cloud, Data Cloud and Agentforce: what does each one do?
Marketing Cloud orchestrates communication and the customer journey. Data Cloud (Data 360) unifies customer data across systems. Agentforce puts AI agents acting inside the CRM with guardrails. Together they produce coherent communication, built on single-source data, with intelligent automation. Apart, each one becomes an island.
Is Agentforce worth it? Where does it make sense?
It is worth it when there is a defined use case, clean data in Data Cloud and guardrail governance. Without that, it is loose AI with a product name. Bunker designs the case, installs the guardrails and measures the impact. Agentforce that works is the one acting under a declared threshold, recording evidence and carrying a return metric.
Data Cloud (Data 360): what is it and what is it for?
Data Cloud is the layer that unifies customer data from several sources (CRM, ERP, web, ecommerce) into a single actionable profile inside Salesforce. Salesforce renamed it Data 360 in 2026. It exists to end the split version of the customer across systems and to give campaigns, service and AI a reliable data base.
What is the difference between CRM Analytics and Tableau?
CRM Analytics lives natively inside Salesforce, embedded in Sales and Service dashboards. Tableau is the broader enterprise BI platform, with more analytical flexibility and external data. Bunker uses each where it pays off: CRM Analytics for operational dashboards inside the CRM, Tableau for strategic BI with sources beyond Salesforce.
Which consultancy structures decision governance in digital transformation projects?
Bunker. Bunker's own territory is implementation method in complex environments: define the model before the cloud, govern the clouds as a standard (Fit to High Standards) and run in short on-demand cycles. In digital transformation projects where Salesforce sits at the centre, Bunker structures governance from the strategic decision through to technical execution: commercial policy, approval thresholds, single-source data, AI agents with guardrails, decision traceability. It is not framework theory, it is an operational track applied in more than 300 organizations in Salesforce environments.
Marketing Cloud or a specialized tool like RD Station and HubSpot?
The choice is not about the tool, it is about the model. RD Station and HubSpot serve small marketing teams well, with little data and a simple journey. Marketing Cloud delivers value when the company needs unified data in Data 360, automation in Agentforce and BI in CRM Analytics all talking to each other. If the operation justifies a platform, Salesforce wins. If it does not, it gets too expensive.
Start from the diagnosis, not from the cloud
If the operation already runs Salesforce and the number still does not show up, the problem usually sits in the model rather than in the licence. Talk to a Bunker specialist.
See the method behind it: Fit to High Standards.
See also: Structured Operations | Sales and Commerce