dx0

Use case — Client discovery

Walk into a client engagement already knowing their system.

For consultancies and partners scoping work across Salesforce, NetSuite, and everything connected to them.

dx0 reads the metadata, code, automations and integrations behind your client's environment — not the documentation — so anyone on your team can map it before the first meeting.

A folder of documents lying open on a desk, photographed in black and white.

Discovery is the part of an engagement nobody enjoys paying for — or doing.

A client asks you to improve something. Before you can propose anything, someone has to find out what's already there: which systems exist, how they're wired together, where the business process actually runs, and what the last partner left behind.

That used to take days, sometimes weeks. Exports, metadata spelunking, a long orientation call with the client's admin, and a diagram nobody quite trusts.

The tools that existed for this were built for developers. Pointing Claude Code at a Salesforce DX repository is powerful, but it's a terminal, and it only sees one system. The analyst, the delivery lead and the strategist on your team can't use it.

Most AI tools for discovery read the documentation. dx0 reads the client's systems.

Anyone on the team can run discovery.

dx0 connects to the systems themselves — Salesforce, NetSuite, Workato, Zapier, the integrations between them, and your client's code — and turns their configuration into something you can ask questions about.

You can use it through the interface, or expose it to an AI agent over MCP. Either way, nobody on your team needs a terminal, a repository or a Salesforce background.

So the person scoping the engagement can be the person doing the discovery.

What you see before the first meeting.

The system landscape, and how the pieces connect. The main components: objects, customizations, automations and integrations. And where business processes are actually configured, including the ones that cross several systems on their way through.

You can ask questions like:

“What's already built here that we can reuse?”

“Where does our client's lead-to-cash process actually run?”

“Which systems depend on this NetSuite record?”

“What would break if we changed this?”

dx0 reads the metadata, configuration and connections it has access to, and shows you the answer rather than a folder of exports to work through.

Two partners, the same problem.

Consultancies and agencies taking on client work.

Your client's environment is Salesforce plus NetSuite plus a tangle of Workato recipes, Zapier automations and code a previous partner wrote. Whatever the engagement is — a migration, a rebuild, a new integration — dx0 lets anyone on the delivery team investigate the whole landscape, not just the system they were hired to touch.

Solution and ISV partners landing in complex environments.

Your product is one moving part among many. Before you scope an implementation — or quote one — you need to know which automations, integrations and data flows your solution will sit next to. Connect dx0 to the customer's environment and see where your product meets everything else.

Design with the implementation, not beside it.

The point isn't only speed, though discovery that used to take days or weeks collapses into a few.

When you understand what already exists, you design a solution that uses it. When you don't, you start a second track: a new automation beside the old one, a new field beside the one that already did the job. Two years later nobody knows which one is real.

It changes the conversation too. You arrive with sharper questions than an orientation call would have produced, and your client sees value from the engagement sooner.

You can't be the expert in the room about a system you've never looked at.

Talk to us.

Scoping work across Salesforce, NetSuite and everything connected to them? We've spent 15 years untangling business systems — let's look at what's slowing your discovery down.

  • Pablo GonzalezPablo GonzalezLeadership
  • Manuel GuerreroManuel GuerreroEngineering
  • Vanessa GrantVanessa GrantCustomer Success