The public inbound inquiry form

What it is

The inbound inquiry form is the front door to Verinode HQ. It is a single unauthenticated page where a franchise brand, trade association, buying group, or PE firm can reach out and ask Verinode to bring the HQ network-intelligence layer to their organization. Nobody needs an account, a login, or an existing Verinode relationship to use it: it is the very first touchpoint, before any group, any membership, or any data has been set up.

This is not the same thing as the Active Prospects pipeline on a signed HQ customer's own Recruiting page (see Recruiting & Growth: section overview). That page tracks a franchise network's own franchisee candidates once the network is already running on Verinode, and it is worked by that network's own recruiting team. The inbound inquiry form sits one level up: it is how an organization's leadership first reaches Verinode about becoming a network customer in the first place. If you are an individual restoration business owner looking to sign up for Verinode as an operator, this page is not for you either. It is aimed at leadership of multi-location networks, franchisors, associations, and PE-backed platforms, the audience HQ itself serves.

Where to find it

This page has no sidebar entry and does not sit under hq.verinode.ai. It is a public page, reached directly at verinode.ai/inquire. It carries the Verinode | HQ eyebrow in HQ's steel blue, so it reads as HQ's own front door even though it lives outside the authenticated product. Nothing on the page requires signing in.

What every field means

The form is one page, no multi-step flow. Fields, in order:

• Your name and Email, both required. These are the two fields marked with a small red asterisk, along with Organization name below.
• Phone (optional).
• Organization name, required. The name of the franchise brand, association, buying group, or firm, not a personal or franchisee name.
• Organization type, a dropdown with five options: Franchise brand (corporate), Trade association (e.g. RIA), Buying / dealer group, Private equity / acquirer, and Other. It defaults to Franchise brand (corporate) and always carries a value, so leaving it untouched still submits a valid selection.
• Approx. member count (optional), a number field for the network's approximate franchisee count, if known.
• Primary states (comma-separated, optional), with the placeholder example "GA, NC, FL". Whatever you type is split on commas, each piece is trimmed and upper-cased, and empty pieces are dropped, so "ga, nc, fl" becomes GA, NC, FL before it is submitted.
• What would success look like? (optional), a four-row free-text box for context: what the organization is hoping Verinode will do for its network.

Only three fields are required: Your name, Email, and Organization name. Everything else, including Organization type by virtue of its default, can be left as-is or skipped.

Submitting the form

The button reads Send inquiry. While the submission is in flight it reads Sending… and is disabled, so a second click cannot fire a duplicate request.

Before anything is written, the server checks four things and returns the first failure it finds, shown in red text above the button:

• "Your name is required." if Your name is blank.
• "A valid email is required." if Email is blank or does not contain an "@".
• "Organization name is required." if Organization name is blank.
• "Invalid organization type." if the organization type is not one of the five listed values (this can only happen if the form is driven outside the browser, since the dropdown itself can't produce an invalid value).

If the write to the database itself fails, that error is shown the same way. In every failure case the form keeps whatever you typed, so you can fix the one problem and resubmit without retyping the rest.

On success, the form is replaced entirely by a confirmation panel in HQ steel blue:

Inquiry received. Thanks, our partnership team will be in touch within two business days. In the meantime, take a look at the data-use policy.

There is no second submission from the same page load: once you see the confirmation, sending another inquiry means reloading /inquire.

How a submission becomes a pipeline row

Because the visitor has no account and no session, the write cannot go through the same authenticated path the in-product Recruiting page uses for its own group-scoped prospects. Instead, the server action behind this form writes with Verinode's service-role client, the same pattern used anywhere a public, unauthenticated form needs to reach the database safely. Nothing about that path lets the writer read the row back or see anyone else's inquiries: it is a one-way intake, not a general-purpose public API.

Every field you filled in is trimmed, the email is lowercased, and the row is stamped with an inquiry source of "website-inquiry-form", set automatically and not something a visitor can override. That source label is what tells Verinode's partnership team the lead came in through this exact form, as opposed to a referral, a conference conversation, or another channel.

The row that results lives in Verinode's own partnership pipeline, a separate table from the group-scoped prospect pipeline described in Recruiting & Growth: section overview. That distinction matters:

• This form's pipeline exists before any group or account does. It tracks organizations Verinode itself is courting as future HQ customers, and it is worked by Verinode's own partnership team, not by any franchise HQ admin. No HQ login, at any permission level, can see or act on these rows: there is no group to scope them to yet.
• The Recruiting page's pipeline (Active Prospects, on hq.verinode.ai/recruit-grow) belongs to an already-onboarded network and tracks that network's own franchisee candidates, added either by hand or, in principle, by other intake channels that network sets up for itself.

The trust-first data boundary

Beneath the form, every visit to /inquire shows the same footer, regardless of whether you've submitted anything yet:

Trust-first by design. Operator-level data stays operator-side; HQ sees aggregates and named brand-protection only. Read the data-use policy.

This is Verinode stating its core privacy commitment at the very first point of contact, before a network has even signed on. "Operator" here means the restoration businesses that will eventually run under the network as Verinode memberships (never "seats" or "licenses"): once a network is live on HQ, those franchisees keep their own operational and financial data. HQ, and by extension the network's leadership, only ever sees network-wide aggregates, rankings, and named brand-protection and compliance signals, never a single franchisee's private books. The inquiry form itself asks for nothing at the franchisee level at all, only the inquiring organization's own contact and network-level details, which is consistent with that same boundary from the very first field.

The data-use policy link is the same one repeated in the confirmation panel after a successful submission, so it's available whether you read it before or after sending your inquiry.

Best-practice example

Say a regional restoration franchisor's VP of Operations wants to explore Verinode HQ for their 22-location network. They go to verinode.ai/inquire, fill in their name and work email, the franchisor's legal name, select Franchise brand (corporate), note an approximate 22-location member count, list their primary states, and use the notes field to say they're specifically interested in franchisee benchmarking ahead of their annual convention. They submit, see "Inquiry received," and follow the data-use policy link while they wait. Two business days later, Verinode's partnership team follows up using the email address they provided, and the conversation from there moves entirely outside the product: the HQ Recruiting page and its own franchisee-level Active Prospects pipeline only come into play once that network is actually onboarded and starts tracking its own franchisee candidates.

Related reading

• Recruiting & Growth: section overview: the in-product pipeline a signed HQ network uses to track its own franchisee candidates, distinct from this page's Verinode-side partnership pipeline.
• HQ overview: how Recruiting & Growth and the rest of HQ's network-intelligence sections fit together.
• Network Health: what HQ sees in aggregate once a network is live.
• HQ Benchmarks: how the top-quartile and median figures referenced during partnership conversations are computed.
• HQ Programs: franchisor programs and standards tracked once a franchisee is onboarded.
• HQ Standards: conformance tracking for franchisees already in the network.
• HQ Report Library: where generated decks and other franchisor documents are archived.
• HQ Compliance: the compliance surfaces alongside HQ's franchisee-level tracking.
• Broadcasting to your network: how an onboarded HQ network communicates with its own franchisees, distinct from this page's pre-account intake.
• Discovery Day: the in-person deep dive that typically follows a qualified inquiry.
• Item 19 and financial performance representations: the disclosure requirement relevant once financial figures enter a recruiting conversation.

Data sources