01 / START HEREIN PILOT
No-install inspect
Read the public form journey, visible confirmation, endpoint, status, timing, and failure signals.
Operator-assisted · no credentialsPATHQUILL / FOUNDER PILOT
Let us test one client enquiry form for you.
We are inviting five web and marketing agencies to hand us one authorised client form. We run the operator-assisted inspection and return a clear report showing what happened, where the handoff became uncertain, and what to check next.
Free for 30 days · one form · no credit card · no passwords · no site changes
NO INSTALL plugin-freeNO PASSWORDS public journey onlyNO LEAD CONTENT body discarded
Future CRM integration: a small one-time setup with one supported CRM of your choice, separate from this no-install pilot.
FOUNDER PILOT / SAMPLEEVIDENCE-FIRST
One authorised URLNormal browser behaviour · one controlled run
01
ObservedPage loaded, form found, endpoint and response recorded
02
ReportedValidation, spam, send-error, or confirmation state captured when visible
03
UnknownPrivate SMTP, inbox, CRM, and mailbox placement stay clearly labelled
YOUR TAKEAWAYA useful next action, not “thank you”
THE CONCIERGE PROMISE
Less setup. More useful truth.
There is no plugin to install, no client mailbox password to share, and no promise that a green form response means a human received the lead. The pilot gives an agency a fast, bounded read of the live browser journey and a clear handoff for anything the browser cannot see.
THE PATH FORWARD
Start with an inspect. Earn proof. Add continuity later.
Every stage builds on the last without asking an agency to hand over passwords or real lead contents on day one.
02 / PROVE ITIN PILOT
Verified handoff
Where authorised, match the synthetic token through the authenticated webhook or approved token-only forwarding route.
Point-in-time delivery evidence03 / KEEP WATCHNEXT PHASE
Continuity signal
With explicit consent, compare count-only CRM or form events against a baseline and flag unusual quiet periods.
No mailbox scraping · no lead bodiesTHE HANDOFF YOU CAN RESELL
A branded report that says what happened—and what it does not prove.
Each report is designed to be shared with a client or attached to an agency support workflow. Failed runs can draft a support ticket with safe run metadata instead of copying lead content.
CLIENT-READYPathquill-branded, print-ready evidence with the date, form journey, outcome, limitations, and recommended next action.
CONFIDENCE LABELSObserved · Reported · Delivery-proven · Inferred · Unknown. The label never outruns the evidence.
FIRST LANESGravity Forms and Contact Form 7 first, then webhook/Zapier/Make adapters; HubSpot before Pipedrive as named CRM lanes.
FORM TYPESQuote requests are in scope now. Booking events such as Calendly come later through their own provider webhook.
30-DAY PILOT SCORECARD
We measure what the agency does with the report.
A page view is not validation. The useful signals are forwarding, comprehension, resolution, and a request to receive the same evidence again.
01 / FORWARDEDDid the agency send the report to its client, as-is or after clarification?
02 / UNDERSTOODCould the client understand the last confirmed stage and next owner?
03 / RESOLVEDDid it produce a useful log check, receiver check, or support action?
04 / WORTH PAYINGWould the agency run it again or include it in a care package?
THREE SMALL STEPS
From authorised URL to a report you can use.
Share one URL
Send the public form page and confirm that you are allowed to test that client journey. No credentials or visitor data.
We run the inspection
Pathquill follows the browser-visible path, records the endpoint, status, timing, and failure signals, then discards the body.
Receive the handoff
You get a concise report showing the failing stage, the evidence behind it, and the next question that needs the client’s own systems.
WHAT THE REPORT SEPARATES
Observed. Reported. Inferred. Unknown.
That distinction is the point. A browser can tell us that a request left, that a server answered, and sometimes what the form plugin told the visitor. It cannot honestly invent a private SMTP error or claim the client read the message.
OBSERVEDPage, form, endpoint, HTTP code, timing, and visible response.
REPORTEDValidation, spam, or send status exposed by the form layer.
INFERREDWhere the handoff likely became uncertain, with the reason stated.
UNKNOWNSMTP, inbox, CRM, and placement details requiring client-side evidence.
SAFETY BOUNDARY
Authorised sites only.
The operator confirms the target is theirs to test. The pilot does not log into sites, alter forms, send real lead data, or turn an unsupported JavaScript/CAPTCHA flow into a false pass.
Read the security boundary ↗WHO IT IS FOR
One high-value client journey. A calm answer before the next lead arrives.
The first pilot is deliberately operator-assisted: useful for a web or marketing agency that wants to check a critical enquiry path without wiring up a new monitoring stack.
- One authorised form or page to inspect
- One minimised evidence report
- One honest boundary around what the browser cannot prove