Formnest

Formnest is a web form tool for small teams: reusable templates, field validation, published forms and structured responses. It is delivered as web software at formnest.example; the operating company is not disclosed on the site.

Small-team operators create client intake forms; project owners review and assign responses. Respondents provide information; operators and project owners manage responses.

New client submits a request → operator checks required information → project owner assigns follow-up. The desired output is a reviewable structured response, for recurring collection of similar fields.

Existing alternatives include email exchanges and shared spreadsheets. Missing fields require follow-up; shared updates may separate responses from their owners.

Product proposition: published forms and field validation turn scattered requests into structured responses.

Recurring demand comes from incoming client enquiries, registrations or service requests. Stable fields, team handoffs and retained responses support repeat use.

Public pages state an English interface used through mainstream desktop and mobile browsers, and the template gallery is English-only. No regional restriction, service level or dedicated deployment is described.

Checked on 2026-09-16: formnest.example accepts sign-ups and form creation, /pricing shows two plans, and no shutdown, waitlist or beta notice appears. The web entry is the only one, so no other surface needed separate checking.

Core loop: configure fields, publish a form, receive and review responses. Templates reduce setup; notifications support follow-up; exports and permissions support handoffs.

The editor accepts field labels and help text, field types and validation rules, a template choice, and images inside a form description. Respondent input is constrained by field type; upload size limits and accepted file types are not published.

A shareable form and client responses the team can review, assign and retain, with notifications for incoming responses.

Choose an intake template → configure fields and validation → preview and publish → receive and assign responses. Respondents submit through a public link; creators process responses in the workspace.

1. 1Operator

   Choose an intake template

   Pick a scenario template on /templates, where a completed example response is shown before the copy action.

2. 2Operator

   Configure fields and validation

   Add or remove fields in /editor and set required items and format checks such as date and email; the exact scope of those checks needs separate confirmation.

3. 3Operator

   Preview and publish

   Preview the form as a respondent sees it, then publish to get a public link.

4. 4Respondent

   Submit through the public link

   Complete and submit without an account; the submission is constrained by field type.

5. 5Project owner

   Receive and assign responses

   Review structured responses in /responses and assign follow-up; a notification can be sent on each incoming response.

/templates helps choose a use case; /editor configures fields and validation; the published form accepts responses; /responses supports review and assignment. Quota or advanced-access needs expose the upgrade entry.

Public path: / → /templates → /templates/client-intake. Task path: /editor → published link → /responses. Support: /help; purchase: /pricing.

• / — homepage, states the job and links the template gallery
• /templates — gallery index, grouped by use case
• /templates/client-intake — one template page: filled example first, copy action after
• /use-cases — scenario pages explaining the job and when it applies
• /guides — explanatory articles linking to their matching template
• /editor — form editor; the quota notice here links to /pricing
• /responses — response list and assignment
• /pricing — the two plans and the checkout entry
• /help — help centre and the single email contact

An account is required to create and save a form; respondents submit through the published link without one. Team members need workspace access to see responses, and a Free workspace stops accepting new responses once the monthly cap is reached.

Field validation for dates and emails, and response-access scope, require checking.

Copying a form reuses its fields and validation; retained responses support authorized follow-up. Reuse works when the next task shares a similar structure.

The payer is the small-team owner or operator who buys a workspace; what is bought is a higher monthly response allowance and team sharing. Respondents neither pay nor need an account, and the purchasing decision-maker is not disclosed.

A per-workspace subscription, billed monthly or annually, with the workspace as the billing unit. The allowance is metered in responses per month and kept separate from seats; no standalone usage-based purchase path is published.

Two public standard plans are published, Free and Pro, and the same two names appear on the pricing page, in the editor's upgrade notice and at checkout. No enterprise tier, custom tier or per-seat quote is listed, and no earlier plan names were found in the changelog.

Pro: USD 19 per workspace per month, or USD 180 per year, quoted in USD before tax; Free is USD 0. The pricing page lists no enterprise quote, contact-sales entry or promotional price.

USD 180 ÷ 12 = USD 15 per month as an annual equivalent; the actual charge is a single payment of USD 180, not USD 15 monthly. The pricing page does not distinguish the first term from renewal.

The allowance is metered in responses per month: 100 on Free, 2,000 on Pro. The pricing page does not say whether unused responses roll over and states no seat cap; form and template counts carry no stated limit.

Both plans share the same form editing, publishing and response review, with an identical output format. Pro adds team sharing and custom branding; beyond export the pricing page itemizes nothing further, and blanks are not read as unsupported.

Published forms and structured responses

Both plans

Field validation

Both plans

Response export (CSV)

Both plans

Team sharing

Pro only

Custom branding

Pro only

Webhook delivery

Plan mapping not stated on the pricing page

Free is an ongoing free tier: no card is required to sign up and publish a form, and the allowance is 100 responses a month. No time-limited trial is offered and no automatic charge on expiry is described; the example responses on template pages are viewable without signing up.

The first charge appears under two disclosed conditions: a Free workspace reaching 100 responses in a month, or a need for team sharing and custom branding. The editor's quota notice links to /pricing, where the user confirms before checkout; the notice itself charges nothing.

The founder's public metrics page discloses USD 22,300 collected in August 2026, described as a full calendar month of subscription receipts with no statement on refund handling. Only that one month is published; no comparable prior month exists.

August 2026 is estimated at 50,400 website visits, covering global desktop and mobile web, from a traffic model. Visits count sessions that one person may repeat; they are not unique visitors, page views or search clicks.

Five dated events are on record: first public availability on 2024-06-12, a listing in a specialist tool directory on 2025-12-08, team sharing announced in the changelog on 2026-04-12, an integration guide on 2026-04-21 and the first ad copy on 2026-05-05. Order does not establish cause.

2024-06-12

First public availability; any visitor can sign up and publish a form

2025-12-08

Listed in a specialist tool directory whose page links the homepage

2026-04-12

Changelog announces team sharing: member invitations and response viewing

2026-04-21

Integration guide published, covering webhook delivery and CSV export

2026-05-05

First ad copy appears in the ad library record

Four people were recorded on 2026-09-10, spanning engineering, design and operations, from the member list on the About page. Whether contractors or part-time help are included is not stated, and no earlier headcount is available for comparison.

Starting-resource notes include intake templates and founder experience in small-team operations. Creation dates and acquisition costs have not been recorded.

The company discloses month-end MRR of USD 22,000 for August 2026 on its metrics page, defined there as subscription run rate. The page is updated monthly and provides 12 consecutive month-end values from September 2025.

Annualized run rate under this report's own rule: USD 22,000 × 12 = USD 264,000. No separate ARR figure is disclosed; this is neither revenue actually collected over the past year nor a forward commitment.

Month-end MRR moved from USD 20,100 in July 2026 to USD 22,000 in August 2026: an increase of USD 1,900, or +9.45% month over month. Both points are consecutive month-end values from the same disclosure page under one definition.

Visits rose from 36,000 in July 2026 to 50,400 in August 2026: an increase of 14,400, or +40.0% month over month. Both months come from the same traffic model, so a change derived from estimates remains an estimate.

Estimated visits and disclosed MRR both rose in August 2026, but they come from different sources and definitions: one modeled, one company-reported. Visits grew 40.0% against 9.45% for MRR, and the available records do not explain that gap. No paying-customer, subscription or retention disclosure exists to cross-check, so how much template-page traffic becomes a paid workspace cannot be determined.

Three kinds of acquisition activity are observable: organic search, where template and use-case pages take long-tail demand; owned publishing, in the changelog, guides and integration article; and inbound links from an external directory and a partner page. One two-week paid campaign ran in July 2026 and was inactive when checked. No breakdown of each channel's actual contribution exists, so this module records entries and observable evidence only.

Modeled shares for the June–August 2026 window: organic search 54%, direct 31%, referral 10%, social 3%, paid search 1%, other 1%. The window is the source's own and was not narrowed to the latest month; these are visit shares, not revenue shares.

August 2026 modeling puts visits at United States 38%, United Kingdom 14%, India 12%, Canada 6%, Australia 5% and 25% elsewhere. No comparable history is available to describe change, and visitors are not customers, so nothing follows about paid demand in each market.

The source estimates roughly 27,216 monthly organic visits for formnest.example on Google in the United States for August 2026, modeled from rank and click-through rather than measured visits or search-console clicks. A same-source monthly series is available from September 2025.

The same estimated series moved from 20,000 in July 2026 to 27,216 in August 2026: an increase of 7,216, or +36.08% month over month. The change describes that one estimate; it is not all-site visit growth and is not attributed to any particular SEO action.

Eight queries relevant to this site's acquisition were collected: two branded and six non-branded, spanning task intent, template-finding and plan-limit comparison. All were found through organic rankings; the comparison query is a candidate only and is not confirmed to bring this site any visits.

formnest

Branded navigation

formnest pricing

Branded, checking price

online intake form

Complete a task: collect client information online

client intake form template

Find a ready-made template

event registration form template

Find a ready-made template

service request form template

Find a ready-made template

free form builder for small teams

Complete a task, with a free-tier condition

form builder with response limits

Compare plan limits; candidate query only

The corpus is grouped by the job behind each query: collecting client information (2 queries), finding a template (3) and comparing plan limits (1), with 2 branded navigation queries kept as a separate dimension. The grouping applies to this version's corpus only and does not describe the whole market.

Across the eight-query corpus, August 2026 US Google volume totals 8,370, led by the branded query formnest (2,400) and online intake form (1,900). These are single-month values rather than 12-month averages, and overlapping queries are not summed into a market size.

Single observations on US desktop Google, 2026-09-10: both branded queries rank 1; the three template queries rank 6, 7 and 9; online intake form ranks 8; the remaining two rank 12 and 18. These are one-off positions rather than averages, and exclude ads and SERP features.

Source-reported US market average CPC: online intake form USD 2.40, client intake form template USD 1.60, event registration form template USD 1.20; no value was returned for the other five queries. These are market price signals, not this site's actual spend, and cannot be multiplied by volume to estimate a budget.

Source keyword-to-page estimates total 2,710 a month across the eight ranked queries, led by formnest → / at 900, online intake form → /use-cases at 620 and client intake form template → /templates/client-intake at 480. The remaining five account for 710. All are estimates, not the full search volume arriving here.

Within the eight selected queries and their 2,710 estimated visits: branded navigation 1,050 (38.7%), template discovery 880 (32.5%), client-information collection 760 (28.0%) and plan-limit comparison 20 (0.7%); the chart splits these into six by query and sub-theme. This is a sampled-corpus, representative-page measure, not the site's overall organic mix, and no query was dropped for a missing value.

Four kinds of entry page: /templates and its individual template pages offer a form that can be copied directly; /use-cases explains the job and when it applies; /guides holds explanatory articles; and / and /pricing take branded queries. Template pages are the main organic entry type; the rest are recorded as discovered pages rather than proven entries.

/templates

Gallery index grouped by use case, linking into each template page

/templates/client-intake

One template page: filled example response first, copy action after

/use-cases

Scenario pages explaining the job, the fields needed and when it fits

/guides

Explanatory articles whose body links to the matching template

/ and /pricing

Take branded queries, stating the job and the two plans

Source page-level organic estimates for August 2026 are led by /templates at 8,165, /use-cases at 5,443 and /guides at 2,994; seven pages total 21,392. The source labels these organic traffic without saying whether they are entry visits, so they are neither added to site-wide visits nor turned into shares.

On /templates/client-intake the H1 states the job outright (Client intake form template); the page shows a completed example response, explains why each field exists and closes with a “copy this template” action into the editor. No section explains the validation rules, and the sign-up requirement appears only after the copy action.

Three pages under /templates were examined (client-intake, event-registration, service-request). They share one structure — example response, field notes, copy action — and differ in scenario name, field list and example content. Similar structure neither establishes programmatic generation nor shows that every page carries enough distinct content.

Visible links on the pages examined: /guides articles link to their matching /templates page; a template page's copy action points to /editor; the quota notice inside /editor links to /pricing; and the footer links /templates and /help site-wide. Links establish that a path exists, not that visitors follow it.

The collected corpus is dominated by requests for a ready-made form template, and template pages deliver a filled example before moving the visitor into the editor. Branded queries hold 38.7% of the corpus's estimated traffic, so the rest is mostly non-branded demand. Page-level estimates total 21,392 against a domain estimate of 27,216; the gap sits in pages not collected and says nothing about how complete the coverage is. The corpus does not describe the site's overall organic mix, and no record establishes what template pages contribute to paid conversion.

Two ad records were collected, sharing one creative: one points to /templates, the other to /pricing, and the platform marks both inactive. The creative is a static image with copy, showing a completed intake form and a “Start free” button. No spend or performance data was obtained.

Snapshot on 2026-09-16: zero ads marked active were observed within the ad library's coverage. This applies to that source at that moment, is not a total across platforms, and does not establish that all advertising has stopped.

Within a collection window of 2026-06-01 to 2026-09-16, two records remain after deduplicating by platform and ad ID; both are inactive and none is of unknown status. This is the count inside that coverage, not every ad the brand has ever run.

The platform records a start date of 2026-07-05 and an end date of 2026-07-18: 14 calendar days including both ends. A date span is not days actually delivered, and no interim snapshots exist to show continuous delivery.

Both records' original URLs carry utm parameters; with those removed they resolve to /templates and /pricing, and both endpoints were verified. /templates promises a template that can be copied straight into the editor, and /pricing shows the two plans and their monthly response allowances, with no ad-specific offer.

Within this two-record pool, /templates and /pricing each carry one distinct ad ID. The count reflects the size of the collected sample only: it says nothing about which page converts better and is not a count of visits to either page.

The creative addresses small teams that collect client information repeatedly: it opens on a completed form, names the trouble of chasing missing details, promises a form published in ten minutes, offers that example as its own proof and closes on “Start free”. No discount or price appears, and the promise is the advertiser's claim, unverified here.

The site footer links two accounts: a brand account posting product updates and a founder account posting build notes. The two identities are recorded separately, and no evidence was found of a commercial arrangement with any third-party creator.

Snapshot on 2026-09-10: the brand account displays 2,400 followers, shown by the platform as an approximation. The founder account's count is not added to it, and followers are neither active users nor paying customers.

Six posts containing a product link were found and four were read: they are short demonstrations of new templates and of field validation, with the product appearing as an interface screenshot plus a link to /templates. The search covered linked posts only, not spoken or unlinked mentions.

One official launch record was obtained: the changelog announced team sharing on 2026-04-12, describing member invitations and response-viewing access. No founder or third-party post on a developer community was found, so there is no discussion sample to read.

Across 24 deduplicated reviews, nine mention less setup time, five that a template can be reused as is, four that responses sit in one place for handoff and three that required-field validation reduces missing answers. Each is tied to its original review and the job the reviewer described; individual reports are not a population rate.

Four records: two describe difficulty importing historical client data in bulk from an old spreadsheet, one that the response-access scope of a public link is hard to confirm, and one that a published form stops accepting responses at the free cap with no advance warning. These are user reports; none was reproduced here.

Three representative requests bearing on this report's conclusions were checked: bulk import is still marked unsupported in the help centre; team viewer access has been supported since the 2026-04-12 changelog; and an advance warning before the quota cap is mentioned nowhere, leaving no matching evidence. A request is not willingness to pay.

Bulk import of historical client data

Still limited: explicitly marked unsupported in the help centre (checked 2026-09-10)

Team viewer access to responses

Supported per the vendor: 2026-04-12 changelog, Pro plan only

Advance warning near the monthly cap

No matching evidence: absent from both the pricing page and the help centre

Two records show users organizing historical client data into a CSV and entering it form by form as a workaround for bulk import; one keeps the original shared spreadsheet as a backup alongside it. No record shows a user switching to another product or abandoning this one.

One review platform displays an overall rating of 4.6 out of 5 as of 2026-09-10. It comes from that platform alone, is not averaged across rating scales and is not recalculated from the reviews read here.

The same platform shows 38 ratings, over the same period and definition as the 4.6 out of 5 score. A rating count is neither a number of people nor a number of written reviews.

Show a complete result before the start action, helping users understand what to prepare and what they will receive before starting their own task.

Applicability: there is a clear deliverable that can be shown anonymized, and at least one recurring use case. The action is to build one page for that case, put a complete example before the start action, then observe whether visitors can say what they need to prepare. Services whose results are highly bespoke, with no representative example to show, are out of scope. This is a suggested action, not something this product is recorded as having done.

The question: after seeing the example, can new users explain the required inputs and expected result, then start creating a form?

Choose one common intake template; prepare field guidance, a completed preview and an anonymized response. Place the example before the copy action, so users can go directly from preview to template reuse. Ask target users to create a form; record misunderstandings, task starts and where they get stuck.

1. 1Content

   Prepare one showable example

   Choose one common intake template and prepare field guidance, a completed preview and an anonymized response. The deliverable is those three pieces, and it is part of the core loop.

2. 2Frontend

   Put the example before the copy action

   Reorder the page so users go straight from the example to copying the template. The deliverable is the revised page, and it depends on the previous step.

3. 3Product

   Ask target users to try it and record

   Ask target users to create a form and record misunderstandings, task starts and where they get stuck. The deliverable is the observation notes: a supporting step, but the one that decides whether to continue.

Reuse an existing template where possible. Prepare examples you have permission to display, page changes and observation notes. Update examples when fields or workflows change; assess effort against the actual scope.

Two verified related products: Wirekit, an interface tool upstream, whose organized business data could prefill form fields; and Mailloom, an email tool downstream, where consented contact responses could feed later email journeys. Both would require field mapping and authorized access, and no ready-made connector was verified; a relationship is neither a company partnership nor an existing integration.

Wirekit — upstream

Connects data to internal workflows; its organized fields could prefill a form. The handoff was recorded on 2026-06-10 and needs field mapping and authorized access.

Mailloom — downstream

Builds customer email journeys; responses from contacts who consented to follow-up could feed it. The handoff was recorded on 2026-07-02 and needs unsubscribe handling.