All resources

Before you add another tool

The useful purchase is the one that removes a recurring problem your team can actually describe.

Name the job.

Write down the trigger, the expected result and who maintains it. “Improve automation” is too broad. “Create the next task when this record meets these conditions” is something you can evaluate.

Check what you already have.

Consider the native Dataverse, Dynamics 365 and Power Platform tools already available to your organization. An additional module earns its place when it offers a useful configuration or maintenance advantage for your specific case.

Compare the full cost.

Look beyond the license price. Include configuration, Microsoft capacity, support, upgrades, training and the time spent maintaining the result. The proposed Switchboard license is one-time; services and Microsoft costs remain separate.

Test the actual requirement.

Use a synthetic record and define what success looks like. Check the result, the administrator experience and the information available when something goes wrong. Before purchase, confirm that the supported release covers the feature you need.

Choose the smallest useful start.

A single module can be the right fit. The collection makes sense when several included modules solve real jobs for the same organization. Planned upgrade credit is intended to make starting smaller easier; final terms will be published before sales open.

Find the module for your job