alignment_status: review - visual tier - 2026-06-18

FormForge Strategic Group Map - Review

This page reviews the final pending competitive-analysis framework. It renders the full non-canonical Strategic Group Map working packet and asks for approval before the parent orchestrator writes research/competitive-analysis-strategic-group-map.md.

Scope And Method

Scope

Flat research/ FormForge scope for client-service solo consultants, coaches, and small agencies doing client intake/onboarding.

FormForge's current product boundary remains the fresh-start AI-assisted form builder loop: describe, generate, edit visually, publish, receive submissions, and review/export responses.

Method

The map clusters competitors by buyer-visible packaging and adoption tradeoffs. It does not rank vendors, recommend positioning, or write canonical synthesis.

Source checks used public pages from Typeform, Jotform, Tally, Fillout, Google Forms, HoneyBook, Dubsado, IntakeQ, Paperform, forms.app, Typeform MCP, and Jotform developer docs.

Review artifactCanonical write pending approvalParent route: $competitive-analysis

Axis Selection

Axis	Why It Matters	Evidence	Confidence
Client-workflow depth	Separates generic collection from lead capture, portals, reminders, contracts, invoices, signatures, secure sharing, or vertical intake.	HoneyBook/Dubsado suite breadth; IntakeQ vertical intake workflow; general builders emphasize forms, submissions, logic, templates, and integrations.	High
Implementation footprint	Separates tools adopted for one form from suites or vertical systems that imply workflow migration or operational change.	General builders expose self-serve/free plans; HoneyBook/Dubsado sell business-management suites; IntakeQ sells vertical intake/practice modules.	High
Integration/automation maturity overlay	Handoff depth matters to the ICP, but it cuts across both general builders and suites.	Tally, Paperform, Jotform, Typeform, and suite products all expose different integration/API/workflow surfaces.	Medium-high

Required gate: Axis selection

Should the canonical intermediate use these axes?

Approve client-workflow depth and implementation footprint as the primary axes. Approve with edits noted below. Other / None of the above. Need clarification.

Strategic Group Map

Higher client workflow depth

Lower workflow depth

Lower footprint

Higher footprint

Google Forms

Tally

forms.app

Fillout

Typeform

Paperform

Jotform

HoneyBook

Dubsado

IntakeQ

Plausible gap:
Client-intake-specific workflow depth with lower suite-migration burden. Medium confidence until customer interviews validate it.

Group	Competitors	Workflow Depth	Footprint	Confidence
Free/low-friction collectors	Google Forms, Tally, forms.app, Fillout	Low to medium	Very low to low-medium	High
Polished general platforms	Typeform, Paperform, Jotform, Fillout	Medium to medium-high	Low-medium	High
Client-service suites	HoneyBook, Dubsado	High	High	High
Vertical intake workflow	IntakeQ	High	Medium-high	Medium-high
Potential whitespace	No direct incumbent proven from current evidence	Medium-high	Low-medium	Medium

Competitor Placement

Competitor	Client-Workflow Depth	Implementation Footprint	Group	Evidence	Confidence
Google Forms	Low	Very low	Free/workspace-bundled collector	Online forms and surveys with question types, customization, sharing/embed, response charts, and Sheets export. Source	High
Tally	Low-medium	Low	Generous free lightweight builder	Unlimited forms/submissions free within fair-use limits, logic, uploads, payments, redirects, and integrations. Source	High
forms.app	Low-medium	Low	Low-cost AI-enabled general builder	Free plan with unlimited responses, 30+ field types, conditional logic, AI generator, and 500+ integrations. Source	High
Fillout	Medium	Low-medium	Power general builder	Free unlimited forms/seats plus paid logic, payments, PDF generation, uploads, analytics, and business controls. Source	High
Typeform	Medium	Low-medium	Polished engagement/form platform	AI form creation, conditional logic, webhooks/integrations, response tiers, branding, analytics, Growth Flow, and enterprise. Source	High
Paperform	Medium	Low-medium	Polished operational form builder	AI creation, guided mode, logic, payments, uploads, 2,000+ integrations, webhooks, and API access. Source	High
Jotform	Medium-high	Low-medium	Broad form operations platform	Forms, apps, tables, inbox, PDF tools, Sign, Workflows, AI, HIPAA forms, payments, widgets, and integrations. Source	Medium-high
HoneyBook	High	High	Client-service suite	Lead forms, client portals, proposals/contracts, invoices, scheduling, automations, reporting, and AI. Source	High
Dubsado	High	High	Client-service suite	Lead capture forms, portals, contracts/proposals, invoices, scheduling, workflows, email/calendar, and Zapier. Source	High
IntakeQ	High	Medium-high	Vertical intake/practice management	Branded forms, attachments, e-signatures, reminders, secure sharing, export, HIPAA BAA, and practice-management tiers. Source	High

Strategic Groups

Free Or Low-Friction Collectors

Google Forms, Tally, forms.app, and parts of Fillout compete on availability, generous free tiers, low setup burden, and good-enough form capability.

Synthesis input: this is the strongest substitute cluster and creates a low price ceiling for generic intake.

Polished General Form Platforms

Typeform, Paperform, Jotform, and Fillout compete on richer builder capability, brand polish, logic, analytics, payments, integrations, API/webhook surfaces, templates, and AI creation.

Synthesis input: this crowded middle weakens any "AI forms plus logic" differentiation claim.

Client-Service Operating Suites

HoneyBook and Dubsado own the surrounding client workflow: lead capture, portal, contracts, invoices, scheduling, workflows, automation, and reports.

Synthesis input: suites are threats for buyers who want one system and a possible gap signal for suite-resistant buyers.

Vertical Intake And Practice Workflow

IntakeQ competes on intake as a secure vertical workflow with reminders, signatures, attachments, document sharing, export, and compliance support.

Synthesis input: specialized intake can support higher WTP when operational depth is central.

Whitespace And Crowded Zones

Crowded Zones

Generic form creation and AI-assisted first drafts.
Low-cost basic collection.
Broad operational form platforms.
Full client-service workflow suites.

Whitespace Hypotheses

Client-intake-specific workflow without suite migration.
Post-submission handoff for service work.
Agent-operable intake handoff, but only if workflow-specific because Typeform MCP and Jotform APIs already exist.

Required gate: Whitespace interpretation

Should the canonical intermediate preserve this whitespace framing?

Approve the whitespace and crowded-zone interpretation with the stated confidence limits. Approve with edits noted below. Other / None of the above. Need clarification.

Evidence Matrix

Claim	Source	Evidence Type	Inference	Confidence
Low-cost/free generic collection is crowded.	Google Forms, Tally, forms.app, Fillout	Public product/pricing evidence	Basic intake can be solved by free or low-cost alternatives.	High
The polished general-builder middle is crowded.	Typeform, Paperform, Jotform, Fillout	Competitor feature/pricing evidence	AI creation, logic, uploads, payments, integrations, analytics, and APIs/webhooks are common.	High
Client-service suites compete from above.	HoneyBook and Dubsado	Competitor packaging evidence	Buyers seeking broader client operations may choose a suite.	High
Specialized intake supports higher WTP with workflow/security depth.	IntakeQ	Vertical pricing/workflow evidence	Intake becomes more valuable when bundled with reminders, signatures, secure sharing, compliance, and workflows.	Medium-high
Main plausible gap is client-intake workflow without suite migration.	ICP pain map, HoneyBook/Dubsado suite breadth, generic-builder crowding	Approved ICP plus competitor inference	A suite-resistant segment may want more intake specificity than generic forms.	Medium
Agent-operable intake is not empty space by itself.	Typeform MCP and Jotform developer docs	Developer-platform evidence	Agent/API access needs a client-intake-specific workflow to matter.	Medium

Required gate: Evidence coverage

Is the evidence sufficient for this framework intermediate?

Sufficient for Strategic Group Map with the listed source gaps preserved. Needs more research before canonical writing. Other / None of the above. Need clarification.

Assumptions And Gaps

Assumption	Status	Confidence	What Would Change It
Client-workflow depth and implementation footprint are the right axes.	Evidence-backed by ICP and packaging.	High	Interviews showing price, design polish, compliance, or integrations dominate instead.
HoneyBook/Dubsado adoption feels like migration for some buyers.	Inferred from suite breadth and ICP alternatives.	Medium	Interviews showing target buyers prefer suite consolidation.
Jotform is closer to an operational platform than a lightweight builder.	Evidence-backed by product breadth.	Medium-high	Hands-on trials showing ICPs use only simple forms.
IntakeQ is a vertical proof point, not a primary direct competitor.	Evidence-backed by practice-management framing.	Medium-high	Discovery in regulated coaching, wellness, or therapy-adjacent segments showing direct overlap.
FormForge's potential gap is not yet validated.	Research gap.	High	Customer interviews or trials validating WTP for focused intake without suite migration.

Source gaps: no target-buyer interviews, no hands-on trials, no market-share/traffic/review-volume analysis, time-sensitive public pricing, and no direct tests of Typeform MCP, Jotform APIs, Tally webhooks, or Paperform APIs.

Proposed File Changes

Path	Action After Approval	Status Now
`research/competitive-analysis-strategic-group-map.md`	Write canonical intermediate from the approved packet.	Not written.
`research/_working/preliminary-strategic-group-map-research.md`	Archive then remove active working packet.	Review packet exists.
`alignment/strategic-group-map-formforge.html`	Archive review page and replace with confirmed page after approval.	This review page.
`research/competitive-analysis.md`	No change in this phase.	Future synthesis only.

Required gate: Proposed file changes

Approve the post-review mutation scope?

Approve writing the canonical Strategic Group Map intermediate and archiving/removing review-stage artifacts after approval. Other / None of the above. Need clarification.

Compile Responses

Answer the required gates above, or select section feedback, then compile YAML. Complete approval lets the parent orchestrator write the canonical intermediate and recalculate the next phase.