Free tool

Custom AI agent or configure Agentforce?

Answer 5 questions about your data, systems, and control needs. Get a clear recommendation in under a minute.

Free tool · Decision guide

Which path fits your Salesforce estate?

Five questions, no email required. Your recommendation appears as soon as you finish.

0 of 5 answered

1. How complex is the data your agent needs to reason over?
2. How much of the actual workflow happens outside Salesforce?
3. How standard are the actions the agent needs to take?
4. How much control do you need over the agent's logic and IP?
5. What is your timeline to production?

Answer all 5 questions to see your recommendation.

Questions

Build vs configure, explained.

Is this quiz a guarantee?

No. It is a directional recommendation based on your answers, not a scoped proposal. A strategy call turns it into a real plan.

What if we need both build and configure?

That's the hybrid outcome, and it's common. Configure Agentforce for native Salesforce work, build custom agents for what it cannot reach, and orchestrate them together.

Why would we build custom instead of just configuring Agentforce?

When your data lives outside Salesforce, your workflow needs custom logic, or you need to own the IP outright. Configuration cannot reach past the platform's edges.

Why would we configure instead of building custom?

When your workflow and data are already native to Salesforce. Configuring reuses what you license and gets you live faster than a custom build.

How does agent-to-agent orchestration fit in?

It's how custom agents and Agentforce agents coordinate as one system instead of two disconnected tools. Most hybrid deployments need it.

Let's work smarter, not harder

Talk through your recommendation with us.

Fifteen minutes to pressure-test the result and map next steps.