30 days of building has changed how I think about buy vs build.
Not from a whiteboard.
From the messy work underneath the product.
I have been in the unglamorous layer: Salesforce objects, Agentforce metadata, workflow evidence, demo-org validation, registry fields, catalog design, runtime signals, and one uncomfortable question:
What can we prove from real data, and what is just a nice UI claim?
The buy-vs-build debate is too blunt for enterprise AI.
The better question is where you should buy leverage and where you must build advantage.
My current bias is simple:
Buy the platforms.
Build the workflow advantage.
If a company runs on Salesforce, it should not rebuild CRM, identity, permissions, automation, data foundation, Flow, integrations, or Agentforce from scratch.
Those foundations should be bought because platforms compound trust, scale, connectivity, and governance.
But once you start mapping real business workflows, the platform answer stops being enough.
Your customer-success motion is not generic.
Your onboarding path, escalation rules, renewal-risk signals, entitlement logic, QBR process, support handoffs, approvals, and account-health assumptions are not generic either.
That is where many enterprises get buy vs build wrong.
They either buy the entire business process as a finished product, then spend years bending it around their reality.
Or they build too much from scratch and recreate platform capabilities they should have inherited.
The sharper move is layered.
Buy the customer platform, data foundation, and agent runtime where they give you trust, security, and workflow reach.
Then build or deeply tailor the layer that understands how your company serves, retains, expands, and protects customers.
An AI agent can summarize an account, draft a follow-up, suggest a next action, update a case, or prepare a renewal brief.
But the business value does not come from the agent completing one task.
It comes from whether the workflow becomes more reliable: whether the right risk signal, customer context, human approval, evidence, recommendation, and outcome all line up.
That is operating knowledge turned into a system: workflow map, context pack, action boundary, approval gate, evidence trail, eval loop, and improvement loop.
This is why I think the next wave of enterprise AI will not be pure buy or pure build.
It will be platform plus workflow.
The platform gives you reach.
The workflow layer gives you differentiation.
I would buy anything that is common infrastructure.
I would build or deeply tailor anything that encodes how the business wins.
For teams building on Agentforce, this distinction matters even more.
The opportunity is not to recreate Salesforce.
It is to make your business process more intelligent on top of the Salesforce foundation.
Buy the platform.
Build the advantage layer.
Measure it at the workflow outcome.
#EnterpriseAI #Agentforce #WorkflowIntelligence