Salesforce reported $41.525 billion in total revenue for fiscal 2026, up from $37.895 billion a year earlier. Subscription and support revenue reached $39.388 billion. These numbers show how deeply Salesforce now sits inside daily business operations. They also raise a harder question: who should decide what a Salesforce project must achieve?
The Salesforce FY2026 filing shows the scale of the business. Yet each customer still has to make smaller decisions about cost, ownership, security, user needs, and project scope. Those decisions can shape whether the project delivers useful results.
Several teams often take part in the same project. Executives may focus on cost and delivery dates. Sales or service leaders care about how the system supports daily work. IT has to protect system design and integrations. Security teams may focus on data access and risk. A consulting firm sits between these groups, so choosing one is both a technical and a management decision.
Business leaders judge the project by business results
Senior sponsors usually judge Salesforce work by the reason the project was approved. A sales leader may watch forecast accuracy or conversion rates. A service leader may care about case handling and response times. Finance may focus on budget, license use, and the cost of later changes.
This creates an early source of conflict. A system can work well from a technical view and still disappoint business leaders. That often happens when the expected result was never turned into clear project measures. Choosing a Salesforce consulting partner should therefore involve more than checking certifications.
Buyers should ask how the partner turns a business goal into clear project decisions. This may include workflows, data rules, user roles, integrations, testing, and ownership after launch. These choices decide whether the system supports the result that leaders expected.
Salesforce also directs customers to consulting partners for planning and deployment work, including Agentforce projects. Its consulting partner directory explains that partners may support implementation, integration, change management, industry work, and ongoing support. That wide role makes clear ownership important from the start.
IT protects system stability while users judge daily work
IT teams are often measured on system reliability, architecture, access control, integrations, support needs, and delivery capacity. Business users judge the same system in a different way. They care about whether fields make sense, approvals slow them down, reports can be trusted, and daily tasks take too many steps.
This is why a review of Salesforce consulting firms should go beyond project size and certification counts. Buyers should ask how each firm handles disagreement between technical design and daily business needs.
A firm that accepts every user request can leave IT with too much custom work. A firm that protects technical design without understanding users can create a system that people avoid. Both outcomes can hurt the project.
The best common ground is measurable workflow performance. Teams can track completion time, user adoption, data errors, integration failures, support tickets, or reporting accuracy when those measures fit the project. Shared measures make it easier to discuss problems with evidence instead of opinion.
Security teams now have more influence over AI projects
AI has increased the number of people who may need a say before a Salesforce change goes live. Salesforce reported in May 2025 that its survey included more than 2,000 enterprise IT security leaders. Among them, 48% said their data foundation wasn't ready to support agentic AI, while 55% weren't fully confident that the right guardrails were in place.
The State of IT security findings show the problem clearly. Many teams may see value in AI while still having concerns about data quality, access, and control.
This affects how companies should compare Salesforce consulting companies. Security can't be treated as a final approval step after the system design is complete. Data access, permissions, human review, audit records, and AI use rules can shape the project from the start.
When these concerns appear late, they can force changes to the design. That can increase cost and delay the schedule. Early security input helps teams make those decisions before development goes too far.
Consulting firms can guide delivery but don't own every decision
A consulting team is usually measured on scope, quality, progress, and whether the agreed system works. The client still owns business rules, budget choices, risk limits, user needs, and many operating decisions.
Problems begin when either side assumes the other owns an open question. This can happen with data rules, testing, scope changes, user approval, or support after launch.
That is why the scope of Salesforce consulting services should be reviewed along with decision rights. A statement of work may list tasks and deliverables, but teams still need to know who can approve changes and who owns each final decision.
NIST offers a useful model for AI-related governance. Its AI Risk Management Framework says roles and communication lines for AI risk should be clearly documented. It also says executive leaders should be responsible for decisions about deployment risk.
The NIST AI RMF Core separates governance, mapping, measurement, and management work. This helps teams see that technical delivery and business accountability are different jobs. A consulting firm can give advice, but the client still has to own key business and risk decisions.
Procurement controls price but can't judge cost alone
Procurement has a clear role in a Salesforce project. It compares suppliers, reviews terms, and helps control spending. The problem appears when different proposals include different levels of work.
One firm may include more discovery, migration, testing, training, or support. Another may leave some of those tasks outside the quoted price. A lower bid may therefore mean lower cost, smaller scope, or both.
Procurement, business leaders, IT, and the project team should compare the assumptions behind each bid. They should use the same scope, delivery rules, and acceptance measures. This makes price easier to judge fairly.
Shared governance works when teams use the same scorecard
Stakeholder alignment doesn't mean every team has to value the same thing. It means the project should define which results matter, who owns each decision, and what evidence will be used when teams disagree.
An executive may care most about revenue. Security may care more about access risk. IT may focus on stability. These goals can still sit inside the same decision process when responsibilities are clear.
A shared scorecard can help. It may include the main business result, adoption, defects, budget variance, open risks, and delivery status when those measures fit the project. The scorecard should match the reason the project exists.
The best decision rule is a shared measure of success
The strongest way to reduce stakeholder conflict is to define success before choosing or directing the consulting team. Every major requirement should connect to a clear outcome, a decision owner, and evidence that shows whether the goal was met. When teams judge the project with the same agreed measures, disagreements become easier to resolve.
Frequently asked questions
What should a company check first when choosing a Salesforce consulting firm?
Start with the work that needs to be done and the result that will prove success. Certifications matter, but they don't replace relevant project experience or clear ownership. Buyers should also decide who will approve scope, system design, security, and final acceptance.
Why do Salesforce projects create conflict between business and IT teams?
The teams are often measured on different results. Business leaders may focus on revenue, service quality, or user output. IT may focus on system design, support needs, access, and integration stability. Clear project measures can help both sides’ judge decisions in the same way.
Should security teams join an AI-focused Salesforce project early?
Yes, when the project uses sensitive data, AI agents, outside models, or automated decisions that create real risk. Early security input can affect data access, review rules, testing, and monitoring. Late security changes can lead to rework and delays.
Is the cheapest Salesforce consulting proposal always the lowest-cost choice?
No. Proposals can differ in migration work, testing, integrations, training, support, and team experience. Buyers should compare what each bid includes before deciding which one costs less.
Who should own the final Salesforce implementation decision?
The business sponsor should usually own the final business decision. IT, security, users, procurement, and the consulting team should provide input in their own areas. The project should document decision rights before major disagreements appear.
For more information, visit VALiNTRY360 or
contact us at 800–360–1407 or send mail [email protected] to get more quote.
Comments
Log in or sign up to join the conversation.