with the skill
# Research Synthesis: "What should we build next?" Survey
**Method:** In-app banner survey, single-choice question | **Responses:** 41 (about 0.5% of ~9,000 MAU)
**Fielded:** 2 weeks, on the Advanced Reports page of the desktop app | **Researcher:** [Name]
## Executive Summary
API access was the clear favorite among respondents, with 29 of 41 votes (71%). Offline mobile mode (15%), simpler onboarding (10%), and other (5%) trailed far behind. However, the sample is heavily skewed. 90% of respondents are Business-plan users, who are only 12% of the user base, and the survey ran only on a power-user page of the desktop app. The result is strong evidence that **Business users of Advanced Reports want API access**. It is weak evidence about what the whole user base wants.
## Results
| Option | Votes | Share of responses |
|---|---|---|
| API access | 29 | 70.7% |
| Offline mobile mode | 6 | 14.6% |
| Simpler onboarding | 4 | 9.8% |
| Other | 2 | 4.9% |
| **Total** | **41** | 100% |
**Respondent plan mix vs. user base**
Show the rest (59 more lines)
| Plan | Respondents | Share of respondents | Share of users |
|---|---|---|---|
| Business | 37 | 90% | 12% |
| Starter | 4 | 10% | ~88% (as the remainder; other plans, if any, aren't broken out) |
Business users responded at roughly 3% (37 of ~1,080), versus about 0.05% for everyone else (4 of ~7,900). This is an approximate comparison that assumes the 12% applies to MAU.
## Key Findings
### Finding 1: API access leads by a wide margin
**Prevalence:** 29 of 41 respondents (71%)
**Observation:** API access got about 5x the votes of the next option.
**Robustness:** The plan-by-answer cross-tab wasn't provided, but the bounds are informative. Even if all 4 Starter respondents chose API, at least 25 of 37 Business respondents (68%) did too. The lead among Business users holds either way.
**Implication:** There is real, concentrated demand for API access among Business users who use Advanced Reports.
### Finding 2: The sample can't speak for most of the user base
**Observations:**
- Business is 90% of respondents but 12% of users. Starter users (the large majority) are represented by only 4 responses, so nothing can be said about them.
- The banner appeared only on Advanced Reports in the desktop app. That excludes mobile-first users, who are the people most likely to want offline mobile mode.
- It also excludes new users who haven't reached that page, who are the people most likely to care about onboarding.
- Respondents self-selected, and 41 responses is about 0.5% of MAU.
**Interpretation:** Both runner-up options were probably structurally under-sampled, so their low vote counts shouldn't be read as low demand. API's lead may also be inflated by who saw the survey.
### Finding 3: "Other" is small but unexamined
Two respondents chose Other. No free-text responses were provided, so they should be read before the write-up is finalized, in case they point to something the options missed.
## Insights → Opportunities
| Insight | Opportunity | Impact | Effort |
|---|---|---|---|
| Business/Advanced Reports users strongly want API access | Scope an API for the Business tier. Validate use cases first | High (for Business) | [TBD with Eng] |
| Mobile and onboarding were under-sampled | Re-survey via mobile app, email, and new-user flows | Medium | Low |
| Unknown Starter preferences | Targeted Starter outreach or survey | Medium | Low |
## Segments
Only one segment is meaningfully represented: **Business-plan, desktop, Advanced Reports users**, who are API-focused. Starter, mobile-primary, and new users can't be characterized from this data.
## Recommendations
1. **Treat API access as validated demand for the Business segment, not as a company-wide priority.** Whether it's the right next build depends on how much Business revenue and retention matter relative to other segments, which this survey can't answer.
2. **Run 5–8 follow-up interviews with Business respondents who chose API.** Find out the use cases (integrations, data export, automation), what they do today, and whether it blocks renewal or expansion. If the survey collected contact info, start there.
3. **Fill the coverage gaps before deciding.** Re-run the question in the mobile app, in an email to Starter users, and in new-user flows, so all four options get a fair read.
4. **Check usage data.** Look at export volume, report scheduling, and similar workarounds as behavioral evidence for API need, and compare against mobile usage patterns.
5. **Read the 2 "Other" responses** and add any distinct themes.
## Questions for Further Research
- What do Starter users want, and does it differ from Business users?
- What would API access be used for, and who would build on it (end users or their developers)?
- Is API demand tied to revenue-relevant behavior such as upgrades, churn risk, or expansion?
- How large is the mobile-first population, and how much do they value offline mode?
- Which respondents chose which option? A plan-by-answer cross-tab is needed to confirm Finding 1.
## Methodology Notes
- **Limitations:** Very low response rate (~0.5% of MAU), self-selection, a single-choice forced ranking (no intensity or willingness-to-pay data), and fixed options that may have shaped the answers.
- **Coverage bias:** Placement on Advanced Reports in the desktop app biases toward heavy desktop Business users.
- **Not provided:** per-plan answer breakdown, free-text responses, and any qualitative quotes, so none are included here.
- **Percentages** are of 41 responses. With n=41, small differences (for example, 6 vs. 4 votes) shouldn't be treated as meaningful.
**Suggested one-line summary for the team:** "Business users of Advanced Reports clearly want API access. We don't yet know whether that holds for the rest of our users, so let's validate it and fill the gaps before committing."