with the skill
## Research Synthesis: What Should We Build Next?
**Method:** In-app survey | **Responses:** 41
**Duration:** 2 weeks | **Placement:** Banner on the desktop app’s Advanced Reports page
### Executive Summary
API access was the clear preference **among respondents**, receiving 29 of 41 votes (71%). However, this survey primarily captures the views of Business-plan users who visited Advanced Reports and chose to respond—not the overall user base. Business users account for 90% of responses but only 12% of all users. Treat the result as a strong signal to investigate API access for this audience, rather than a company-wide mandate to prioritize it.
### Results
| Requested feature | Votes | Share of responses |
|---|---:|---:|
| API access | 29 | 71% |
| Offline mobile mode | 6 | 15% |
| Simpler onboarding | 4 | 10% |
| Other | 2 | 5% |
*Percentages are rounded.*
### Key Findings
Show the rest (44 more lines)
#### 1. API access led by a substantial margin
**Observation:** API access received 29 votes, compared with 12 votes for all other options combined.
**Interpretation:** There is a clear preference for API access within the responding group. The survey does not tell us which API capabilities respondents need, what problems they would solve, or how frequently they would use them.
**Implication:** Prioritize API discovery before committing to a build or defining scope.
#### 2. Business users are heavily overrepresented
**Observation:** 37 of 41 respondents (90%) were on Business, compared with 12% of the overall user base. Only four respondents were on Starter.
**Interpretation:** The results are much more informative about the responding Business-heavy audience than about users overall. Without a plan-by-choice breakdown, we cannot establish how preferences differ between plans.
**Implication:** If the roadmap goal is to serve Business customers, this is a useful directional signal. If the goal is broad adoption or Starter-user value, additional evidence is needed.
#### 3. Survey placement limits what we can conclude
**Observation:** The survey appeared only on the desktop Advanced Reports page. The 41 responses equal roughly 0.46% of the approximately 9,000 monthly active users.
**Interpretation:** Users who do not visit that page—including mobile-focused users and people struggling to get started—may be poorly represented. This could understate demand for offline mobile mode or simpler onboarding, although the size and direction of that effect are unknown.
**Implication:** Low vote counts for those options should not be treated as evidence that those needs are unimportant.
### Insights → Opportunities
| Insight | Opportunity | Potential impact | Effort |
|---|---|---|---|
| API access dominates this sample | Interview API voters to identify workflows, required capabilities, and current workarounds | Potentially high for this audience; unvalidated | Low–Medium for discovery |
| Responses are concentrated in Business | Compare preferences by plan and recruit more Starter users | Better confidence in roadmap fit | Low–Medium |
| Recruitment excluded other product contexts | Gather feedback in mobile and onboarding contexts | Better visibility into underrepresented needs | Medium |
### Recommendations
1. **Start focused API discovery.** Follow up with API voters to understand their use cases, pain severity, expected usage, and minimum useful scope.
2. **Validate beyond Advanced Reports before making a broad roadmap commitment.** Recruit across plans and product surfaces, particularly mobile users and new users.
3. **Cross-check demand against behavior and business goals.** Review relevant support requests, sales feedback, onboarding drop-off, and mobile usage where available. Evaluate reach, customer value, and build cost—not vote totals alone.
4. **Inspect the two “Other” responses**, if free-text details were collected.
### Questions for Further Research
- What tasks would API access enable, and what do users do today instead?
- How do feature preferences differ by plan and usage pattern?
- Are onboarding difficulties preventing users from reaching Advanced Reports?
- How important is offline access to mobile users?
- Which option best supports the team’s current strategic goal?
### Methodology Notes
This was a self-selected, single-choice survey—not a representative sample of the user base. Banner impressions and eligible page visitors were not provided, so **the survey response rate cannot be calculated**; responses as a share of monthly active users are not a response rate. The forced-choice question measures relative preference among the listed options, not absolute need, willingness to pay, or likely adoption. No qualitative comments or participant quotes were provided.