← Back to Signal
Customer Discovery PlanDraft

Customer Discovery Plan: Users want workflow templates to reduce time-to-value from a blank canvas

Last updated 2026-05-11

Draft — review content and approve to promote this artifact.

Problem Statement

FlowPilot users across solo, SMB, mid-market, and startup segments experience friction when starting from a blank canvas, slowing their time-to-value and reducing confidence in the product. Multiple users have explicitly called out the absence of a template library as a barrier to adoption and recommendation, particularly for common use cases like sales ops and customer onboarding. The lack of templates has become a competitive disadvantage, with users directly comparing FlowPilot unfavorably to competitors offering 100+ templates.

Evidence Summary

18 feedback items span four segments: SMB (6 items), Mid-market (8 items), Startup (3 items), and Solo/Freelancer (1 item). Two items are rated MEDIUM severity, one from a Startup and one from a Mid-market user, both explicitly stating templates would make getting started easier. The remaining 16 are LOW severity but show a consistent, unprompted pattern. Recurring themes include: (1) blank-canvas paralysis, SMB users asking 'I don't know where to start'; (2) competitive comparison, two Mid-market and one Solo user citing a competitor with 100+ templates; (3) specific use-case requests, sales ops templates mentioned by two SMB/Mid-market users, customer onboarding by three Mid-market/SMB users; and (4) recommendation blockers, one SMB user explicitly stating templates are 'the one thing keeping me from recommending this to others.'

Priority Rationale

The signal scores 65/100 with medium confidence, reflecting a broad but not yet deeply validated pain point. Despite predominantly LOW-severity individual items, the volume and cross-segment consistency, spanning SMB, mid-market, startup, and freelancer, indicate systemic friction rather than isolated preference. The competitive framing across multiple items elevates urgency, as the absence of templates is actively influencing purchase consideration and word-of-mouth referrals. Prioritizing discovery now will determine whether a focused set of 5–10 templates can materially move activation and recommendation metrics before committing to a full template library build.

Acceptance Criteria

  • At least 5 of 7 interviewed users can articulate a specific workflow use case they would have used a template for in their first week with FlowPilot
  • At least 3 distinct high-demand template categories are identified and ranked by frequency of mention across interview sessions
  • Interviewed users confirm that access to 5–10 starter templates would have meaningfully reduced their time to first successful workflow (not just 'nice to have')
  • At least one SMB or mid-market user who cited templates as a recommendation blocker can confirm a template library would change their referral behavior
  • Discovery interviews surface whether users want community-contributed templates, PM-curated templates, or both, providing a directional build decision

Hypothesis

If FlowPilot provides a curated library of 5–10 pre-built templates covering high-frequency use cases such as sales ops and customer onboarding, then new users across SMB and mid-market segments will reach their first successful workflow faster, and existing users who cited templates as a recommendation blocker will become more likely to refer the product, because the evidence shows blank-canvas friction and competitive comparisons are the primary stated barriers, not feature gaps elsewhere in the product.

Target Accounts

  • ·SMB customers who submitted feedback explicitly asking for a template gallery or stating templates are a recommendation barrier, highest signal density and direct advocacy impact
  • ·Mid-market customers who compared FlowPilot unfavorably to competitors citing 100+ templates, represent competitive displacement risk and have articulated specific use-case needs (sales ops, onboarding)
  • ·Startup users who indicated templates would make getting started easier, represent the new-user activation scenario and can speak to first-week experience friction
  • ·Recently churned or at-risk accounts where sales ops or onboarding automation was an identified use case, can validate whether absence of templates contributed to failure to activate or expand

Discovery Questions

  1. Walk me through the last time you created a new workflow in FlowPilot from scratch, where did you get stuck or slow down, and what did you do to unblock yourself?
  2. When you mentioned [templates / getting started / a competitor's library], what specifically were you imagining using, a finished workflow you could activate immediately, or a starting point you'd customize?
  3. Which workflows do you find yourself rebuilding or copying most often, and what would it mean for your team if those were available as one-click templates?
  4. You mentioned a competitor with 100+ templates, have you actually used those templates, and if so, what made them useful or not useful in practice?
  5. If FlowPilot launched a template gallery tomorrow with 10 templates, which single use case would you need covered first for it to be worth your attention?
  6. You said templates are 'the one thing keeping you from recommending FlowPilot', can you help me understand what recommendation scenario you have in mind, and what specifically changes for you if templates exist?
  7. How do you currently onboard a new team member or client onto a FlowPilot workflow, and where does the absence of templates show up as a problem in that process?

Open Questions

  1. Is the core problem blank-canvas overwhelm (onboarding UX), lack of inspiration (template discovery), or pure time savings for repeat use cases, and does the answer differ by segment?
  2. What is the minimum viable number and type of templates needed to shift competitive perception and unlock recommendations, given users mentioned 'even 5–10 would help'?
  3. Do users want fully functional plug-and-play templates or customizable starting points, and how much configuration tolerance exists before templates lose their value?