Creating a business case for purchasing Wondering will demonstrate its value to the rest of your company. If you're new to this process, don’t worry—we've got you covered with this guide where we will help you simplify the process.

As you navigate through this guide, feel free to fill out our free Wondering business case template to get started building your business case for purchasing Wondering for your organization.

Implementing a new user research tool will require a change in your team’s workflow. Begin by evaluating your current workflows, team needs, challenges, and behaviors to identify the gaps that Wondering can address.

To collect this information, observe current practices, or conduct interviews or surveys with stakeholders. Key questions to explore include:

Next, you’ll want to clearly outline the vision for your research practice, as well as goals and success metrics.

Your vision represents the ultimate aim of purchasing Wondering. Ask yourself, "What do I want our research practice to look like in a year? What does success look like without constraints?" Often, this might include visions like: "We want a modern research tool that makes it easy for designers to gather insights from users easily."

Based on this vision, set specific goals such as "Each new feature or product we ship should have gone through at least two rounds of testing with real customers to de-risk the chances that we build the wrong thing, or build the thing wrong."

Define measurable objectives to track success, such as the number of studies conducted or customers engaged.

After having identified your vision, goals and success metrics, list your requirements for a new user research tool, focusing on the key features you want to see in a new tool. For example, this could include features like AI analysis. Also consider the legal, privacy and security needs of your organization.

A spreadsheet is a good way to note down the features and how different solutions stack up against your needs, detailing the pros and cons, risks, costs, and key criteria for each solution.

After evaluating the possible solutions, you should now have a good idea of why Wondering is the tool you want to go with.

The next step is providing this recommendation, along with your reasoning for it, covering an overview of the platform and its key features, cost, benefits and overall how it will fit into your team and its workflows. An example of how you can phrase this recommendation is: "We're recommending Wondering for its easy to use and intuitive. It makes it easy to build, deploy and analyze AI-powered user research studies to a global panel or real customers via link or in-product targeting that will get us actionable user insights faster than the alternatives".

Assemble a "tiger team" of stakeholders to bring this initiative to life. Include executives with budget approval, legal and security teams if needed, subject matter experts, and champions who will promote the value of investing in UX research. This team will help anticipate roadblocks, help you move forwards with a purchasing decision and facilitate tool rollout across teams. Detail who will be involved in the project and their roles. For example:

Conduct a brainstorming session with your tiger team to anticipate risks or challenges, similar to a pre-mortem exercise. Address potential risks, such as low adoption rates after purchase, by involving key champions from the design team early in the evaluation phase to ensure the tool meets their needs. Ask questions like:

It’s also a good idea to anticipate potential questions from stakeholders and prepare resources with additional information so that you can keep the process running smoothly. Make sure you understand the pricing for your plan on Wondering, details on legal and security policies, and success stories from other companies that scale their user research with the help of Wondering. It can be a good idea to provide resources such as:

It’s a good idea to bring to life how you intend for Wondering to be rolled out across your company post purchase, outlining major milestones needed for a successful transition to Wondering. Include key dates, milestones, and responsible parties.

Next, decide how you will monitor and report progress to your team. This could include creating a Slack channel for core stakeholders, scheduling bi-weekly status meetings. Over-communicate to ensure smooth adoption and address any concerns promptly.

With the information above ready, you're now ready to fill out the free Wondering business case template if you haven't already and share your business case!