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.

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.

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.

An integration guide states that responses can be pushed to an external address by webhook and exported as CSV. Retry policy, rate limits and authentication are undisclosed, and no ready-made third-party connector page exists.

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 only public purchase entry is the plan confirmation button on /pricing, which leads into self-serve checkout; /help carries an email contact, but the page does not present it as a quoting or procurement route. There is no app-store or marketplace entry.

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.

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.

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.

The About page states the project is self-funded and has taken no outside investment, and no contrary evidence was found as of 2026-09-16. Bootstrapped describes the funding source only: it says nothing about profitability, cash position or runway.

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.

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.

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.