> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minoa.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Set Up Baseline Surveys for Your Team
> Build survey templates your reps can send in a minute, so business cases run on the customer numbers instead of guesses
Reps don't build surveys from scratch mid-deal. They grab what's ready, or they estimate — and an estimate is exactly the number a CFO pulls on later.
As an admin you can fix that once. Build a few templates in the **Value Intelligence** tab and anyone on your team can pull one into a deal and send it inside a minute. The answers come back attached to the right inputs, with the customer's name on them.
## What a custom survey is
Minoa's baseline survey used to be tied to the use cases inside a business case. Now you can create custom templates and send additional surveys whether or not a business case exists — useful when you're working with a new stakeholder, a new team, or you just want to level-set before anyone builds a model.
Each survey mixes two kinds of question:
1. **Numeric metrics** — real inputs from your value framework ("hours per week spent on X", "current cost of Y"). Answers feed directly into the business case.
2. **Qualitative questions** — free text, yes/no, rating sliders, single- and multi-select.
The result is a business case built on numbers the customer gave you, rather than numbers your rep guessed.
## Why templates are worth the setup
Three or four templates cover most teams. Build these and your reps will use them.
| Template | When your team sends it | What it captures |
| --------------------- | ------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Discovery baseline | After the first or second call | The 5–8 metrics that drive your most common use cases, plus 2–3 context questions |
| Pre-proposal baseline | Before the business case is presented | Inputs for the specific use cases in play, plus a stakeholder-alignment question |
| Kickoff baseline | At implementation start | The numbers you'll measure value against at renewal — captured before anything changes |
| Renewal baseline | \~90 days before renewal | Current values of the same metrics from the original business case |
| Expansion baseline | When an upsell conversation opens | Status-quo metrics for use cases the customer doesn't own yet — the seed of the expansion case |
If you only build one, build **Kickoff baseline**. It's the template that makes value realization possible later,
and it's the one that gets skipped without a template to prompt it. See [Prove Value to Existing
Customers](/pages/recipes/prove-value-to-existing-customers).
## Setting one up
Open the survey builder in the **Value Intelligence** tab and search across all your use cases, toggling on the
metrics you want answered.
Any of the five question types — free text, yes/no, rating slider, single-select, multi-select.
Drag inputs and questions into the order you want, and group them into sections if the survey runs long.
Give it a name your reps will recognize. Unnamed surveys get a default one, which nobody ever picks from a
list.
You can edit a survey after launch. Existing answers are kept for anything you don't remove.
## What your reps do
Grab the template, copy the share link, send it. That's the whole workflow.
The link works for anyone — no account, no login for the customer. Email, Slack Connect channel, wherever the conversation already lives.
## What the customer sees
* A **branded welcome** — your logo, your color, an intro you wrote.
* A clean two-column form: sections on the left, questions on the right, with the right format for each answer (currency, percentage, duration).
* They can add notes on any answer, skip what they don't know, and finish in one sitting or come back to it.
* Each respondent's progress is tracked separately, so you can send one link to five stakeholders and see who's done.
## Working with responses
Watch progress live in the **Responses** tab — who finished, who's midway, every answer as it lands.
Accept numeric responses to pull them straight into the business case, or dismiss them if you're planning to re-survey later. Nothing overwrites anything: every answer is kept as history and you decide what counts. Accepted values carry the respondent's attribution, which is what makes them hold up under scrutiny — see [Input ownership](/pages/business-case/input-ownership).
The survey creator gets an email and a Slack notification when a customer completes.
All of this works conversationally too. Ask the Minoa agent to build a survey, launch it, review the responses, or
send reminders, and it will.
## Key takeaways
* **Templates get used; blank builders don't.** Three or four cover most teams.
* **Kickoff baseline is the one that matters most**, and the one most likely to be skipped.
* **No login for the customer** — one link, works anywhere, tracked per respondent.
* **Accepting a response attributes the number to them**, which is what makes it defensible.