FormForge ICP Alignment

Pre-approval checkpoint for ICP discovery. This page summarizes the research frame, early evidence, candidate segments, assumptions, and proposed file changes. No canonical ICP deliverables have been written yet.

Scope resolved: flat single-product research mode. The repo has pnpm-workspace.yaml, but it only includes ., and research/ has no app subdirectories.

Primary input: research/concept-brief.md, which frames FormForge as a prototype-first AI-assisted form builder focused on describe, generate, edit, publish, collect, review, and export.

Business Model Classification

Initial classification: B2B SaaS (PLG) with possible solo-operator/prosumer adoption. Evidence: the likely buyers are small teams, consultants, agencies, nonprofits, and event operators who can self-serve; competitors commonly offer free trials/free tiers and paid upgrades; the concept defers enterprise collaboration, billing complexity, API access, and webhooks until segment demand is validated.

ICP Candidate Shortlist

Candidate A

Independent consultants, coaches, and small agencies doing client intake

Pain evidence is strongest where intake forms are tied to paid work: chasing clients, gathering assets, avoiding scope gaps, and looking professional before kickoff. WTP evidence is moderate-to-strong because these users already pay for tools like Typeform, Jotform, Dubsado/HoneyBook-style systems, Zapier, or vertical onboarding products.

Candidate B

Small event organizers and community operators

Pain is frequent around registration, attendee details, capacity, mobile completion, exports, and last-minute changes. WTP is mixed: business events have clearer budget than community events, but many users are price-sensitive and compare against free tools.

Candidate C

Nonprofits, schools, and volunteer coordinators

Pain is real around volunteer signup, donations, event registration, and spreadsheet drift. Accessibility is good, but WTP quality is weaker because budget constraints and nonprofit discounts/free alternatives are central buying criteria.

Candidate D

Small businesses using forms for leads, quotes, bookings, and follow-up

Pain appears after submission: forms collect data, then teams manually decide what to do next. WTP is plausible when lost leads are measurable, but generic "small business forms" is broad and may need a narrower vertical to be actionable.

Early Prioritization

Segment	Pain Intensity	WTP Quality	Accessibility	Current Rank
Consultants, coaches, small agencies	High	Moderate to strong	High	1
Small businesses with lead/quote/booking forms	Moderate to high	Moderate, stronger with measurable lost leads	High	2
Event and community operators	Moderate to high during event cycles	Mixed	Moderate	3
Nonprofits, schools, volunteer coordinators	High operational friction	Weak to mixed	Moderate	4

Evidence Coverage

Broad research used 12 query strategies across AI form builders, form-builder alternatives, client intake, consultants, events, nonprofits, volunteer signup, form abandonment, pricing limits, small-business workflows, and no-code/natural-language generation. Deep research has not started yet; the next phase would run 2-3 targeted searches per candidate before final scoring.

Client intake competitors and language: Intake, IntakeFlow, Dashform, Youform, Pixelform, Gavel, Softr.
Generic form-builder competitors and pricing signals: Typeform, Jotform, Tally, Fillout, Paperform, Google Forms, forms.app, Formgrid.
Behavioral signals from forums: users cite pricing limits, submission caps, disconnected response workflows, manual follow-up, spreadsheet drift, branding/professionalism, and switching only when pain is specific.
Research gap: exact market sizing and named-account examples need more targeted source work before final deliverables.

Representative Sources To Log

Intake - client intake/document collection positioning and pain language.
IntakeFlow - legal/tax/accounting intake positioning.
Dashform client onboarding - AI onboarding form generation language.
Pixelform - coach-specific WTP and pain framing.
Formgrid event registration - event registration workflow pains.
Jotform nonprofits - nonprofit forms, discounts, templates, and scale claims.
Tally Typeform alternatives - competitive pricing/features comparison.
Formgrid Typeform vs Jotform - product tradeoff and pricing comparison.
AIAP no-code workflow paper - evidence that natural-language/AI assistance helps non-experts build workflows.

Assumptions To Validate

The strongest wedge may be "faster usable intake/onboarding form" rather than generic "AI form generation."
Consultants and agencies may value speed plus professionalism, but may also need post-submission workflow sooner than the concept currently assumes.
Nonprofits and volunteer coordinators have strong pain but may be hard to monetize early because free/ad-free/discounted tools are common reference points.
Small-business lead forms need narrowing by vertical or trigger event to avoid an overly broad ICP.

Proposed File Changes After Approval

Create research/icp-search-log.md with all queries, findings, source URLs, business-model classification evidence, and scoring rationale.
Create research/icp.md with the canonical ICP framework, primary ICP, additional ICPs, cross-ICP analysis, downstream signals, and final Next Steps section.
Optionally update tasks/todo.md only if follow-up execution tasks emerge from approved findings.

Approval Question

Approve this research direction, or tell me which segment/constraint to adjust before I continue into deep ICP research and canonical artifact writing.