FormForge ICP Alignment - Review

This packet rebuilds FormForge ICP research from first principles. It is a non-canonical working artifact. The intended post-approval canonical outputs are research/icp.md, research/icp-search-log.md, and optional research/.progress.yaml entries for secondary product surfaces if approved.

No canonical research, spec, or task file has been written in this stage.

Repo Evidence

• research/concept-brief.md defines FormForge as an AI-assisted form builder for public forms: describe the needed form, review generated fields, edit visually, publish a public link, receive submissions, and review/export responses.
• research/concept-brief.md frames the broad beneficiary hypothesis as "individuals and small teams," but explicitly says this is not yet an ICP selection.
• src/server/ai/generate-form.ts shows the implemented AI wedge: prompt to structured form definition with title, description, field types, validation, options, and conditional logic hints.
• src/app/page.tsx presents the product as natural-language form creation plus drag-and-drop editing and response analytics.
• tasks/todo.md and README.md show an older/broader surface with billing, collaboration/API experiments, file uploads, analytics, Turnstile, versioning, themes, and i18n-related work. The concept brief warns not to rebuild that old app feature-for-feature before ICP validation.

Product Boundary Used For This Redo

1. A form creator describes a form.
2. AI drafts a usable form structure.
3. The creator edits it visually.
4. The creator publishes a public link.
5. Respondents submit.
6. The creator reviews or exports responses.

Deferred or unproven surfaces include full CRM ownership, contract/payment flows, client portals, durable integrations, quote-estimator engines, event check-in, volunteer schedule management, HR compliance workflows, and enterprise procurement.

Forms are not a standalone job. A form is an input boundary between someone who needs information and someone who has it. Demand becomes economically meaningful when the submitted information moves a paid or operational workflow forward.

The key selection question is therefore not "who needs forms?" Almost everyone does. The useful question is: "Which user repeatedly needs a new or modified public data-collection flow, suffers when setup or response handling is slow, can adopt self-serve software, and already has a reason to pay for better intake?"

From that frame, FormForge should prefer segments where:

• The form creator and budget owner are close to the work.
• Form setup is frequent or variable enough that AI drafting matters.
• The submitted information directly affects revenue, delivery quality, or avoidable labor.
• Respondents are external enough that the form must look professional and be easy to complete.
• The first useful workflow can survive with a link, response dashboard, export, file upload, notifications, and basic logic.
• The segment is not blocked from early adoption by HIPAA/FERPA/HR compliance, enterprise procurement, deep integrations, or specialized workflow infrastructure.

FormForge is not a marketplace. It is primarily B2B SaaS with product-led/self-serve adoption and some prosumer/solo-operator usage.

Material Sides

• Customer/buyer side: the person or small team creating forms and reviewing responses.
• User side: often the same as the buyer in solo and small-team segments; sometimes an ops/admin teammate uses the tool after the owner chooses it.
• Respondent side: clients, leads, attendees, volunteers, applicants, or customers who complete the form. Respondents do not pay FormForge, but their experience changes customer value because poor completion, confusion, or missing details damage the creator's workflow.

Excluded side: respondents are not ICP candidates because they are not the customer side for this product. Their needs are captured as value drivers and risks inside each buyer/customer ICP.

Business Model Classification

• Primary: B2B SaaS (PLG/self-serve).
• Secondary: B2C/prosumer edge for solo consultants, coaches, creators, and operators.
• Not classified as marketplace/platform, B2B2C, open-core, or API/developer-first for the initial ICP.

Evidence includes the concept brief and self-serve product loop, competitor self-serve pricing/free-trial patterns, and the fact that Typeform and Jotform have added AI form creation, making generic AI generation less differentiated.

Minimum broad-query requirement met: 12+ query strategies before final candidate prioritization.

Why this is the strongest first-principles fit

1. The workflow is repeated and variable. Each new client, offer, project, cohort, audit, or program can require a different intake form.
2. The value is tied to paid delivery, not abstract data collection. Missing intake data delays kickoff, creates rework, or hurts the client experience.
3. The buyer and user are close together. Owner-operators and small teams can self-serve without enterprise procurement.
4. The respondent experience matters. Their clients are external and often paying; a polished form is part of the provider's perceived professionalism.
5. The current FormForge loop can satisfy a meaningful first slice without becoming a CRM, event platform, donation processor, or HR system.
6. WTP evidence is better than generic forms because the segment already buys adjacent tools: Typeform/Paperform for polish, HoneyBook/Dubsado for client workflows, Pixelform/intake tools for intake-specific needs, and Zapier/Sheets/Notion for handoff.

Strongest caveat: FormForge should not position the initial ICP as "anyone who needs forms quickly." That puts it against free/low-cost general form builders and makes AI generation a commodity feature. The sharper problem is "client-service operators need a usable, professional intake flow fast, without manually building forms or migrating their whole workflow stack."

Scores are 1-5. Value combines pain intensity and WTP quality but keeps them separate in the rationale.

• Candidate A has lower maximum economic upside than quote/lead forms, but much better fit to FormForge's first validated loop.
• Candidate B has strong pain and WTP, but the value driver is often quote/lead workflow after submission, not form creation.
• Candidate C has clear workflow pain but episodic buying and signup-specific needs.
• Candidate D has high operational friction but weaker WTP because of discounts, free tools, and budget constraints.
• Candidate E has real form needs but trust/compliance/workflow routing requirements create early adoption friction.

Customer Profile

Buyer persona: owner-operator, founder, principal consultant, coach, agency owner, operations coordinator, or client-success/project manager inside a small service business.

Budget owner: usually the business owner or department lead. In small agencies, the ops/project lead may recommend tools, but the owner controls spend.

Geographic focus: initial focus can remain English-speaking US/Canada/UK/Australia-style service businesses because the current repo and concept are English-first and no market-specific compliance wedge is being claimed.

Business model and GTM motion: B2B SaaS PLG/self-serve with solo-operator prosumer adoption. Buyer and user are often the same person. The primary motion should be validated around self-serve discovery and evaluation behavior, not enterprise sales.

Named Account Examples To Verify Before Outbound

These are illustrative public account types, not validated prospects. Sizes are approximate public-profile ranges and should be verified before outbound or account-based work.

Named-account confidence: low to moderate. These examples help shape customer discovery targets; they are not evidence that these companies need or would buy FormForge.

User Profile(s)

• Daily users: solo provider, agency/project coordinator, coach/program operator.
• Skill level: comfortable with SaaS tools, templates, Google Workspace, Notion, and simple automations; does not want to hand-code forms or build logic trees from scratch.
• Goals: get the right client information before kickoff, avoid chasing missing files/details, look polished, customize quickly by service/client type, and export or route answers into the existing work system.
• Frustrations: blank form setup, amateur-looking Google Forms, response/branding/feature limits, heavy all-in-one client systems, and manual copy/paste into project docs or spreadsheets.

Trigger Events

1. New paid client signed or discovery call booked.
2. New service offer, package, audit, cohort, or retainer process launches.
3. Provider notices onboarding delays from missing client information or files.
4. Provider wants a more professional client-facing form than Google Forms.
5. Existing tool hits response limits, branding limits, file upload limits, or price increases.
6. Provider wants to avoid moving fully into HoneyBook/Dubsado or similar suites.
7. Provider needs a recurring progress check-in, testimonial, project feedback, or renewal questionnaire.

Current State Journey

1. The provider closes a client, schedules a discovery call, launches a program, or starts a project.
2. They decide what they need to know: goals, background, contact details, files, links, access, timeline, budget, preferences, constraints, and stakeholders.
3. They start from memory, a template, a previous form, a Google Doc, a Typeform/Jotform/Tally draft, or a client-management platform.
4. They manually create fields, labels, help text, required flags, options, file-upload requests, and conditional branches.
5. They send the link to the client.
6. The client submits incomplete answers or files across multiple channels.
7. The provider follows up through email, Slack, text, or calls.
8. The provider copies answers into a project board, CRM, Notion doc, kickoff notes, or spreadsheet.
9. The kickoff proceeds, is delayed, or starts with avoidable ambiguity.

Pain Map

Current Alternatives (User Perspective)

• Manual: email questionnaires, Google Docs/PDFs, spreadsheet checklists, prior intake forms.
• General form builders: Google Forms, Typeform, Tally, Jotform, Fillout/Paperform/forms.app and similar alternatives.
• Client-service suites and portals: HoneyBook, Dubsado, Pixelform, Dashform, Intake, Agencify, Agency Handy, Formaloo AgencyOS, Brieform.
• Automation stacks: Google Forms or Typeform to Zapier/Make to Sheets/Notion/CRM/email.

User-language themes: "I need everything in one link," "I do not want to chase clients across email," "Google Forms is fine but looks cheap," "The form is easy; the mess is what happens after submission," and "I do not want to move my CRM, invoicing, and calendar just to solve intake."

Market Sizing

• Top-down references: SBA's 2025 small business profile reports 36.2 million US small businesses and 4.88 million in Professional, Scientific, and Technical Services. BLS reports 155,800 US meeting/convention/event planners for the event candidate. Independent Sector reports about 1.9 million registered nonprofit and philanthropic organizations nationwide.
• Primary TAM proxy: US small professional-service businesses that sell services requiring client discovery/intake. Start with SBA Professional, Scientific, and Technical Services: 4.88M.
• SAM hypothesis: 5-15% of that broad pool may run repeated external client intake/onboarding with enough form variance and client-facing polish needs to consider a paid intake/form tool: roughly 240k-730k possible US accounts before subtracting industry/compliance mismatch.
• SOM discovery target: 500-2,000 early accounts in agencies/coaches/consultants/bookkeepers/creative studios would be enough to validate the wedge.
• Confidence: medium for broad TAM; low for SAM/SOM because repeated intake frequency requires customer discovery or better dataset work.

Stated Value Drivers

• Faster setup from a plain-English description.
• Less back-and-forth collecting required information.
• Professional, branded first impression.
• Client can complete the intake without an account.
• File uploads, conditional fields, and required fields capture complete answers.
• Easy CSV/Sheets export or downstream handoff.
• Avoiding response caps, branding limitations, or unintuitive builder complexity.
• Not being forced into an all-in-one platform migration.

Likely aha moment: "I described the client/project and got a good enough intake form in minutes, then edited it and sent a polished link without rebuilding from scratch."

Willingness-to-Pay Signals

• Paid alternatives: Typeform paid plans include AI form creation and response limits; HoneyBook starts with paid monthly tiers and includes lead forms, client portals, templates, contracts, invoices, and AI; Dubsado annual pricing includes lead capture forms and client workflow capabilities; Pixelform markets directly to coaches with paid form pricing and coach-specific templates.
• Budget owner/context: owner-operator or small agency lead pays from operating/software budget.
• Current spend/time-cost proxies: existing spend on client-service suites, form builders, schedulers, automation tools, or manual assistant/ops time.
• Switching-cost tolerance: moderate for form builders, low for all-in-one migration.
• Economic urgency: high when missing intake delays kickoff or creates poor first impressions; medium when only aesthetic or one-off.
• Pricing sensitivity: generic form builders face strong free-tier pressure; client-intake-specific value can tolerate more spend only if tied to saved time and better client delivery.

Customer ↔ User Dynamics

• In solo businesses, buyer, admin, and daily user are the same person.
• In small agencies, the owner may buy while an operations coordinator or project manager creates and edits forms.
• Respondents are external clients or prospective clients. Their experience affects buyer value even though they do not pay FormForge.
• The buyer expects fast setup, likely starting from a prompt or template, and needs to reuse/adapt forms across clients/offers.

Discovery & Evaluation Behavior

• Where they find solutions: Google searches for client intake form templates/tools, Typeform alternatives, Google Forms alternatives, HoneyBook/Dubsado alternatives, and service-specific intake forms; peer communities for consultants, coaches, agencies, freelancers, no-code builders, and small businesses; tool directories, template galleries, SaaS comparison posts, and competitor landing pages.
• What they compare: Google Forms vs Typeform/Tally/Jotform/Paperform; generic form builder vs client-management suite; dedicated intake/client-portal tool vs simple form plus automation stack.
• How they choose: usable form quickly, credible client-facing presentation, low respondent friction, file uploads/logic/required fields/exports, no painful caps or branding limits, and fit with existing workflow without forced migration.

Candidate B - Small Service Lead/Quote Forms

Customer: owner/operators or small teams in local services, contractors, studios, agencies, and service businesses that qualify inbound leads or generate quote requests.

Triggers: website lead volume increases, missed follow-ups or quote delays become visible, a new ad campaign/service line/quote workflow launches, or the current website contact form lacks qualification detail.

Journey: customer fills contact/quote form; team reviews incomplete info; team manually estimates or calls for missing details; lead goes cold if response is slow; data moves into a sheet, CRM, or inbox.

Pain: lead quality, quote delay, missing scope details, no instant follow-up, manual CRM entry.

Alternatives: website contact forms, CRM web forms, Google Forms, Typeform/Jotform/Tally, quote-estimator tools, service-business CRMs, custom calculator forms.

WTP and verdict: strong when tied to valuable closed jobs, but current FormForge fit is lower because the core value often needs pricing logic, CRM, SMS/email follow-up, pipeline status, and vertical-specific qualification. Revisit as a different product surface if the project pivots toward lead qualification or quote workflows.

Candidate C - Small Event And Community Organizers

Customer: community groups, workshops, sports clubs, PTAs, churches, schools, event hosts, and small professional event teams.

Triggers: new event, workshop, roster, volunteer day, class, fundraiser, tournament, or campaign.

Journey: organizer creates registration/RSVP/signup form, shares link by email/social/text, tracks responses in a sheet/dashboard, and manually manages waitlist, no-shows, reminders, rosters, and exports.

Pain: capacity limits, no-login completion, reminders, waitlists, roster visibility, attendee edits, staff/volunteer coordination.

Alternatives: Google Forms, Eventbrite, Jotform, SignUpGenius, Signup Haven, Formgrid, Sendtable, Lome, and event-specific tools.

WTP and verdict: business events may pay, community groups prefer free/low-cost. Good problem, but likely requires event/signup-specific capabilities early.

Candidate D - Nonprofits, Schools, Volunteer Coordinators

Customer: small nonprofit teams, school/PTA admins, churches, volunteer coordinators, charity event operators.

Triggers: fundraiser, volunteer recruitment cycle, campaign, school year, donation drive, event registration, supporter survey.

Journey: create volunteer/donation/event form, share link, track submissions in sheets/CRM, send reminders, coordinate volunteers, export data, reconcile donations.

Pain: paper/spreadsheet drift, volunteer coordination, donation/event forms, supporter data handoff, reminders, low budget, integration needs.

Alternatives: Google Forms, Jotform nonprofit templates/discounts, Gravity Forms, Wufoo, Lome, SignUpGenius alternatives, donor/volunteer platforms.

WTP and verdict: operational value is real, but WTP is weak to mixed due to discounts/free expectations.

Candidate E - Internal HR/Ops Forms

Customer: small business HR/admin/ops teams needing job applications, onboarding documents, approvals, employee feedback, and internal request forms.

Triggers: hiring cycle, onboarding, policy acknowledgment, annual review, compliance need, manager request workflow, paper-process pain.

Journey: create form/PDF, send to employees/managers/candidates, track completions, route approvals/signatures, store records in HR/payroll/ATS systems or spreadsheets.

Pain: routing/approval, e-signature, compliance storage, candidate screening, recordkeeping, internal permissions.

Alternatives: Jotform HR, Typeform application forms, Google Forms, HRIS/payroll software, ATS forms, e-signature tools, Power Automate/AppSheet.

WTP and verdict: WTP exists in formal HR, but trust/compliance matters. Lower early fit unless a low-compliance internal ops segment emerges.

Shared Pains

• People need to get structured information from someone else.
• Blank-page form setup is annoying.
• Existing free tools are "good enough" for simple cases.
• Value grows when the form feeds a real workflow after submission.
• Respondent friction matters: no-login, mobile completion, clear questions, and professional presentation affect completion.
• CSV/Sheets/export and notifications are recurring minimum expectations.

Conflicts

Build/Validation Sequence Rationale

1. Validate Candidate A first because it has the best fit with FormForge's existing loop and strongest combination of pain, WTP, accessibility, and low regulatory burden.
2. Keep Candidate B as the highest-value revisit path if early discovery shows client intake is not urgent enough or if users keep asking for lead/quote workflows.
3. Keep Candidate C as a secondary path if discovery points toward registration rather than client intake.
4. Defer Candidate D unless nonprofit/volunteer discovery reveals an unusually strong budget-backed wedge.
5. Defer Candidate E until the product is ready to handle trust, routing, signatures, and compliance expectations.

Product-Line / Manifest Implications

If approved, I recommend the canonical stage either keep research/.progress.yaml absent and record secondary paths inside research/icp.md, or create research/.progress.yaml with FormForge active and deferred/revisit entries for lead-quote-forms, event-registration-signups, nonprofit-volunteer-forms, and hr-ops-forms. My recommendation is the more skill-complete option because the rejected candidates imply materially different product surfaces. It should not create product directories or run downstream work for those paths.

Source Links By Category

• Generic form builders: Typeform pricing, Typeform AI help, Jotform pricing, Tally pricing, Fillout pricing.
• Client intake/client workflow: Pixelform, Dashform client onboarding, Intake, Agencify, HoneyBook pricing, Dubsado pricing.
• Lead/quote: ScopeForm, Quotify, Quoterform, Quote Box.
• Events/community: Formgrid event registration, Signup Haven, Sendtable, Lome.
• Nonprofits/volunteer: Jotform nonprofit, Gravity Forms nonprofit, SureForms nonprofit, Donorfy forms.
• HR/internal ops: Jotform HR form builder, Typeform for HR, Typeform application forms.
• Market sizing: SBA 2025 small business count, SBA US small business profile PDF, BLS event planners, Independent Sector nonprofit sector.
• Research: AIAP no-code workflow builder paper.

Source Coverage Gaps

• No first-party customer interviews or proprietary FormForge usage logs.
• Named-account sizes for Candidate A are illustrative and need verification before outbound.
• SAM/SOM estimates are inferred from broad datasets and competitor presence, not from a dedicated market-sizing dataset.
• Pricing sensitivity is based on competitor pricing and user sentiment, not FormForge-specific willingness-to-pay tests.
• Compliance constraints for accounting, legal, health/wellness, education, and HR need deeper validation before targeting those subsegments.
• This research did not inspect G2/Capterra reviews deeply because public access and recency vary; doing so could improve user-language evidence.

Rejected Or Lower-Confidence Findings

• "Target everyone who dislikes Typeform pricing." Rejected because Tally and many alternatives already compete on free/cheap form building.
• "Target nonprofits first because they need many forms." Lower confidence because budgets and free/discount expectations weaken WTP.
• "Target event organizers first." Lower confidence because event/signup workflows require slots, waitlists, reminders, and rosters earlier than client intake.
• "Target local service quote forms first." Lower confidence as primary because the best version is likely quote-estimator/CRM-adjacent.
• "Target HR forms first." Rejected for early ICP due to compliance, routing, signatures, and recordkeeping requirements.
• "AI generation alone is the value proposition." Rejected because incumbents and startups already offer AI form creation.

research/icp.md

Write canonical ICP report with primary ICP, required parser headings, additional ICPs, cross-ICP analysis, downstream signals, and final next-step section required by the skill only after approval.

research/icp-search-log.md

Write the raw research log: query list and findings, source URLs by category, marketplace side preflight, business model classification evidence, candidate scoring rationale, evidence gaps, and confidence notes.

research/.progress.yaml Optional

If approved, add product_paths[] entries for materially different secondary surfaces with source_skill: icp, pipeline_stage: icp, status values, and evidence refs. Do not create product directories yet.

• lead-quote-forms - revisit candidate.
• event-registration-signups - deferred.
• nonprofit-volunteer-forms - deferred.
• hr-ops-forms - deferred.