Buyer / Creator
The person or small team that creates and reviews forms.
review
Stage 2 artifact review
customer-discovery
This page renders the complete non-canonical customer-discovery working packet for FormForge's approved fresh-start describe-edit-publish-submit-review loop. It asks for final artifact review before any canonical research files are written.
Alignment date: 2026-06-15
Alignment status: review
Working packet: research/_working/preliminary-customer-discovery-research.md
Archived prior page: docs/history/archive/2026-06-15/091455/alignment/customer-discovery-formforge.html
Canonical files not written: research/icp.md, research/icp-search-log.md, research/.progress.yaml
FormForge is treated as a fresh-start AI-assisted form builder prototype. The initial product loop is:
Non-goals: do not rebuild the old app feature-for-feature; do not make billing, teams, API access, webhooks, durable file storage, provider integrations, or full i18n part of the first validated loop; do not select implementation architecture, schema, or UI spec; do not write canonical research/icp.md until Stage 3 approval.
| Source | Observation | Confidence |
|---|---|---|
research/concept-brief.md | Defines the fresh-start loop and broad beneficiary hypothesis of individuals and small teams. | High |
research/concept-brief-interview.md | Records user confirmation that the broad concept and constraints were reasonable. | High |
research/_working/preliminary-icp-research.md | Prior ICP packet used only as seed context, not canonical evidence. | Medium |
README.md | Confirms the repo was desk-flipped and the new implementation should validate one core loop before deferred infrastructure. | High |
package.json | Shows a built historical app stack, but the concept brief supersedes it for fresh-start product scope. | Medium |
tasks/todo.md | Shows prior broad production surface and deferred feature pressure. Useful as cautionary context. | Medium |
| Source | Key evidence used | URL |
|---|---|---|
| Typeform pricing | Core plans include AI-powered form creation, conditional logic, integrations, and response limits; Basic starts around $29/month monthly with 100 responses/month, with Plus and Business expanding responses and users. | typeform.com/pricing |
| Jotform pricing | Jotform positions a broad form platform with 35M+ users, 20,000+ templates, 150+ integrations, drag-and-drop, AI, payments, workflows, nonprofit and education discounts. | jotform.com/pricing |
| Tally pricing | Tally offers unlimited forms and submissions for free under fair-use guidelines; paid Pro starts at $24/month and adds branding, collaboration, partial submissions, analytics, custom domains, CSS, and integrations. | tally.so/pricing |
| Fillout pricing | Fillout includes unlimited forms on all plans, CSV export, integrations, field validation, conditional hiding, resume-in-progress forms, close dates, and advanced conversion/enterprise features. | fillout.com/pricing |
| HoneyBook | Targets small service businesses, consultants, coaches, creatives, and client-service operators with lead forms, questionnaires, CRM, proposals, contracts, payments, automations, and plans starting around $29/month annual. | honeybook.com |
| Dubsado | Targets client-service entrepreneurs with lead capture, branded forms, questionnaires, proposals, contracts, client portals, workflows, invoices, and onboarding. | dubsado.com |
| Paperform | Positions as a form builder for SMBs with templates, payments, bookings, calculations, and workflow use cases. | paperform.co |
| Eventbrite / EventMobi | Event registration demand often includes ticketing, rosters, check-in, attendee apps, reminders, and event-specific workflows beyond simple forms. | eventbrite.com / eventmobi.com |
FormForge is not a marketplace. The likely model is B2B SaaS with a product-led/self-serve motion and a prosumer edge.
The person or small team that creates and reviews forms.
Often the same person in solo businesses; sometimes an assistant, coordinator, or operations teammate.
Clients, leads, attendees, volunteers, customers, applicants, or community members who fill the form. Respondents influence value through completion quality but are not the paying ICP.
Respondents are not ranked as ICP candidates because they do not buy FormForge. Their needs should be captured inside buyer value drivers, especially mobile completion, trust, clarity, and error handling.
Claim: Client-service solo operators and small service teams with repeated intake/onboarding needs have the best current combination of urgency, accessibility, repeated form variation, and willingness to pay.
Evidence: HoneyBook and Dubsado organize value around client relationships, lead capture, questionnaires, proposals, contracts, invoices, onboarding, and automation. The FormForge loop can produce value before full CRM replacement when scoped to intake/questionnaire creation plus response review/export.
Inference: This segment repeatedly needs forms that differ by service, offer, cohort, project type, or client context. The buyer is close to the work and submitted data affects paid delivery quality.
Confidence: Medium-high.
Claim: FormForge should not position only around natural-language form generation.
Evidence: Typeform includes AI-powered form creation; Jotform advertises AI, templates, integrations, payments, and workflows; Tally and Fillout compete on free/unlimited usage and advanced form functionality.
Inference: AI-assisted form creation is increasingly table stakes. FormForge needs a narrower job-specific promise.
Confidence: High.
Claim: Lead/quote qualification is credible but risks turning FormForge into CRM or quote-estimation software too early.
Evidence: Client-service suites connect lead capture with proposals, contracts, payments, workflows, and follow-up; FormForge defers CRM, billing, webhooks, and integrations.
Inference: Revenue urgency is strong, but value may be blocked by follow-up automation, status, quote logic, scheduling, or CRM handoff.
Confidence: Medium.
Claim: Event/community registration and nonprofit/volunteer coordination have real pain but weaker early-fit economics.
Evidence: Event tools emphasize registration, ticketing, attendee lists, check-in, reminders, event pages, and analytics. Jotform and Fillout offer nonprofit/education discounts, and Tally's free unlimited model creates price pressure.
Confidence: Medium.
Claim: Internal HR/ops is less aligned with a lightweight public-form first loop.
Evidence: Larger form tools sell HR, enterprise, security, and workflow use cases; FormForge defers permissions, compliance, routing, and integrations.
Confidence: Medium-low.
| Rank | Candidate | Pain urgency | Access | WTP signal | Fit with first loop | Main risk | Confidence |
|---|---|---|---|---|---|---|---|
| 1 | Client-service solo operators and small service teams doing intake/onboarding | High | High | Moderate-high | High | Some users want all-in-one CRM/contracts/payments | Medium-high |
| 2 | Small service businesses using lead/quote qualification forms | High | Medium-high | Moderate-high | Medium | Quickly becomes quote/CRM/follow-up software | Medium |
| 3 | Small event/community organizers | Medium | Medium | Mixed | Medium | Needs event-specific rosters, waitlists, reminders, tickets | Medium |
| 4 | Nonprofit/school/volunteer coordinators | Medium | Medium | Weak-mixed | Medium | Free/discount expectations and scheduling/donation needs | Medium-low |
| 5 | Small-business HR/admin/internal ops teams | Medium | Medium-low | Mixed | Low-medium | Compliance, permissions, internal routing, integrations | Medium-low |
Independent consultants, coaches, fractional operators, boutique agencies, creative studios, professional service providers, personal-service providers, and small client-service teams that need structured information before a paid engagement, cohort, project, consultation, or recurring service.
Value drivers are faster variable intake setup, better first impression, less manual follow-up, easier reuse/editing, and lower cognitive load than full CRM suites.
Risks are weak branding, thin response handling, AI output cleanup burden, and missing integrations for users who cannot accept export-only workflows.
Strong revenue urgency; revisit when FormForge can test verticalized lead intake. Risk: high-value lead forms often require quote estimation, scheduling, CRM status, reminders, or fast follow-up automation.
Clear form needs but lower fit with a generic first loop. Event users often need capacity controls, waitlists, rosters, reminders, ticketing/payments, attendee edits, and check-in.
Operational pain but weaker WTP. Free/discounted tools are common, and workflows can need scheduling, donor/volunteer CRM, waivers, accessibility, and committee approval.
Likely too compliance- and integration-sensitive for the first lightweight public-form loop.
| Claim | Evidence | Inference | Confidence | Assumption status | Decision impact |
|---|---|---|---|---|---|
| Client-service intake is the strongest early ICP | HoneyBook and Dubsado center client-service workflows around leads, forms/questionnaires, onboarding, proposals, contracts, payments, portals, and automation; FormForge concept supports form creation/review/export. | Intake is tied to paid delivery and repeated setup, but FormForge can start below all-in-one CRM scope. | Medium-high | Needs direct interviews with consultants/coaches/agencies. | Select as primary candidate for Stage 3 unless user has contrary evidence. |
| AI generation alone is not enough | Typeform includes AI-powered form creation; Jotform includes AI and broad templates/integrations; Tally/Fillout compete with generous free/feature sets. | AI is a mechanism, not sufficient differentiation. | High | Assumes buyer sees comparable AI features as substitutes. | Position around job-specific speed and outcome, not "AI form builder" alone. |
| Lead/quote forms are attractive but risky | Client-service suites connect lead capture with proposals/contracts/payments/follow-up; FormForge defers CRM, billing, webhooks, and integrations. | Quote workflows may demand features outside the first loop. | Medium | Needs vertical-specific interview evidence. | Keep as revisit/pivot candidate. |
| Events/nonprofits are not first priority | Event tools emphasize ticketing/registration/check-in; Jotform/Fillout nonprofit discounts and Tally free unlimited suggest price pressure. | Pain exists, but WTP and workflow fit are less favorable. | Medium | Needs segment interviews before rejecting entirely. | Keep as lower-priority candidates. |
| HR/internal ops is poor first fit | Larger form tools sell HR/enterprise/security/workflow use cases; FormForge defers permissions, compliance, routing, integrations. | Internal ops buyers likely need trust and workflow depth earlier. | Medium-low | Could change for very small teams with simple forms. | Do not choose as primary ICP now. |
| Conclusion | Confidence | What would raise confidence | What would lower confidence |
|---|---|---|---|
| Primary ICP should be client-service intake operators | Medium-high | Interviews showing repeated intake setup pain and acceptance of a lightweight form-first tool | Interviews showing users demand all-in-one CRM/payment/portal features before switching |
| AI is not a standalone wedge | High | More competitor pages adding AI form generation | Discovery showing a niche where FormForge's AI quality is uniquely better |
| Lead/quote is secondary | Medium | Interviews showing quote flows require CRM/estimation/follow-up | A vertical where simple AI-generated qualification forms directly improve close rate |
| Events/nonprofits are lower priority | Medium | Evidence of low WTP or event-specific blocker needs | Evidence of frequent paid use cases without ticketing/scheduling/reminders |
| HR/internal ops is lower priority | Medium-low | Evidence of compliance/integration needs | Small teams using public-ish internal forms with low trust requirements |
Only after final Stage 2 approval:
research/icp.md with a canonical ICP report naming client-service intake operators as the recommended primary ICP, plus secondary/revisit candidates.research/icp-search-log.md with query/source/evidence notes from this and prior seed research, clearly marked by date and source class.research/.progress.yaml only if the user wants parked secondary product paths. Default recommendation: do not create product paths yet.docs/history/archive/YYYY-MM-DD/HHMMSS/research/_working/preliminary-customer-discovery-research.md.| Term | Definition | Source | Category | Decision |
|---|---|---|---|---|
| Client-service intake | A form-based workflow for collecting structured information from a lead or client before qualification, onboarding, kickoff, or delivery. | customer-discovery | workflow | Approve / Edit / Reject / Flag in notes |
| Respondent side | The non-paying party who fills out a form; important to product value but not the paying ICP for FormForge. | customer-discovery | business | Approve / Edit / Reject / Flag in notes |
| Form-first wedge | A narrow entry point where FormForge delivers value through faster form creation and response review before broader CRM/workflow features are added. | customer-discovery | business | Approve / Edit / Reject / Flag in notes |
Use this after answering gates or selecting section feedback. Complete approval requires all required gates answered and no unresolved negative feedback.