Guided demo · Proof-first lead capture

See what a proof-first website does after someone hits submit.

This is a live demo of a Cedar Ridge site built the RP way. It walks through the visitor experience, the business-owner proof view, and the weekly evidence a connected site can receive. A normal form says “thanks.” This one issues a reference after the request is recorded.

Try the visitor flow See the owner view

Recorded before acknowledged
Reference + receipt hash
Delivery evidence

demo.raymondporrello.com/thanks?ref=7284&hash8=cede7284

Message recorded

Your message was recorded before this reference number was issued.

Reference number: #7284
Receipt hash: cede7284

First reply Website contact form · Cedar Ridge office

Response window One business day

Keep the reference number as delivery evidence if you follow up.

What the visitor walks away with

A reference number, not just "thanks"

The visitor leaves with a number they can quote later. Their message was recorded before this number was issued.

A receipt hash they can keep

A short fingerprint of the recorded request — delivery evidence the visitor holds, without an account or login.

A clear next step

Who owns the first reply, the response window, and a fallback path if that window passes. No guessing whether the form worked.

The visitor experience

A normal form — with a receipt at the end

Your customers submit like they would anywhere. The difference is what they leave with: a reference number issued after their request is recorded.

With JavaScript

Submit is intercepted and you get an inline receipt — reference number and receipt hash — without leaving the page.
Without JavaScript

The same form still posts and lands on a thank-you page at /thanks?ref=… with your reference number.
If the service is unreachable

Your message is saved in this browser and retried while the page is open. Best-effort help, not guaranteed delivery.

Don’t want to submit? Preview the receipt a visitor sees.

Preview a sample receipt

Cedar Ridge — request a visit

Live demo form

This form really submits to the lead platform. It’s a demo — please don’t enter anything sensitive.

Follow the lead

One request, from submit to Weekly Proof

Here is what happens after a customer hits submit — the same path every recorded request follows. Names and numbers below are demo data.

Visitor

Jordan Reyes submits a request

A normal contact form — name, email, optional phone, and what they need help with.

Why it mattersThe visitor experience stays simple. Nothing new to learn.
The site

The site records it first

The request is written down and given a reference number before the visitor sees any confirmation.

Why it mattersRecorded before acknowledged means a request can never quietly vanish.
Visitor

Jordan gets a reference and receipt

Reference #7284 and a short receipt hash they can keep as delivery evidence.

Why it mattersFewer uncertain customers wondering "did that even go through?"
The business

The business is notified

The lead lands in your proof-of-capture ledger and an owner notification is sent.

Why it mattersThe lead lands somewhere accountable, not just an email that might be missed.
The site

Delivery evidence is tracked

Received, owner notification sent, delivered to the receiving mail server — each step timestamped.

Why it mattersNo more guessing whether the notification reached the receiving server.
The business

Re-notified if unacknowledged

If no acknowledgement is observed within the window, the lead is re-notified.

Why it mattersCatches the neglected lead before it turns into a lost opportunity.
The business

The week ends with Weekly Proof

A summary of what was recorded, delivered, acknowledged, and escalated that week.

Why it mattersThe owner gets confidence the system was watching — without logging in daily.

Two sides, one system

What your customer sees / what you see

The visitor gets a calmer, more confident experience. You get proof behind the scenes.

Your customer sees

A simple, familiar contact form
Confidence copy: recorded before acknowledged
A reference number they can quote
A thank-you receipt with a keepable hash
A clear fallback if the window passes

You see

A proof-of-capture ledger of every lead
A hash-chained receipt per lead
Delivery evidence: received → sent → delivered to server
Whether acknowledgement was observed
Automatic re-notify when none is observed

The owner experience Sample owner view

What the business sees after a lead comes in

A static, sanitized preview of the real connected-site dashboard — proof of capture, the hash-chained receipt, delivery evidence, and acknowledgement. A live workspace shows an owner only their own leads.

Proof status

Capturing and delivering.

Nothing needs your attention.

Proof of capture

TUE · JUL 1

Jordan Reyes №7284
Water heater knocking Delivered to receiving mail server
Priya Nair №7281
Furnace annual service Acknowledgement observed
Marcus Bell №7275
No AC — upstairs only Re-notified
Dana Whitfield №7270
Kitchen faucet drip Acknowledgement observed

RECEIPT №7284

Delivered to receiving mail server

Lead #7284

Form: contact
Received: Jul 1, 9:14:02 AM
Notified: Jul 1, 9:14:04 AM

SHA-256 cede7284… — hash-chained Copy

Every lead is stored with a hash-chained receipt. This is yours for lead #7284.

Delivery evidence · Jordan Reyes

Received Stored with receipt №7284 9:14:02 AM
Owner notification sent Notification accepted by provider 9:14:04 AM
Delivered to receiving mail server Receiving mail server accepted it 9:14:06 AM
No acknowledgement observed Re-notified after 15 minutes if unacknowledged Awaiting

How your leads are protected

Every lead is stored with a hash-chained receipt.
Failed notifications are retried automatically.
Unacknowledged leads are re-notified after 15 minutes.
Delivery problems appear under Needs attention.

Proof of capture · RP Marketing Group — no receipt, no claim.

Based on platform delivery and acknowledgement evidence only. Activity outside the platform remains unknown.

Proof of capture

Every lead is stored with a hash-chained receipt and a reference number — an auditable ledger, not a shared inbox.

The receipt artifact

One hash-chained receipt per lead: a SHA-256 fingerprint with the captured and notification timestamps. Proof metadata — never the message.

Delivery evidence, stated honestly

Received → owner notification sent → delivered to the receiving mail server. If no acknowledgement is observed, the lead is re-notified.

Why it’s different

A normal form vs a proof-first site

Same submit button. Very different accountability.

Aspect	Normal website form	RP proof-first site
After submit	A generic "thanks" message	A reference number issued after the request is recorded
Visitor keeps	Nothing	A reference number and receipt hash
Did it arrive?	Email notification only — hope it landed	A delivery-evidence timeline on the lead
Was it handled?	Owner hopes staff follows up	Acknowledgement observed, with re-notify if it sits
Launch confidence	No launch proof	An installation-evidence packet
Weekly rhythm	No recurring artifact	A Weekly Proof summary

Launch evidence

Proof the site was installed correctly

Every launch is verified end to end — not just visually checked — and the evidence is kept.

Installation evidence · Sample

This site was installed and verified end to end

Certificate: CR-INSTALL-0417
Origin: demo.raymondporrello.com
Status: Verified Jun 18

Allowed origin accepted Submissions from the live site are recorded.
Wrong origin rejected Requests forged from another domain are refused.
No-JS form path works A plain HTML POST still records and returns a reference.
JavaScript form path works The enhanced path shows an inline receipt with a hash.
Lead row recorded A durable row exists for each accepted request.
Delivered to receiving mail server The receiving mail server accepted the owner notification.
Owner proof available The lead is visible in your proof-of-capture ledger with its receipt and timeline.

A build isn’t “done” because it looks nice. It’s done when capture, delivery, and owner proof are verified — so a launch feels like a serious installation, not a creative project.

A weekly artifact

Weekly Proof, without logging in

A recurring summary of what the system recorded, delivered, acknowledged, and escalated that week.

Weekly Proof · Preview

Week of Jun 23–29

Leads received: 14
Delivery evidence captured: 14 / 14
Acknowledgements observed: 12
Re-notified: 2

Every lead was stored with a hash-chained receipt.
2 leads were re-notified after no acknowledgement was observed.
Median time to acknowledgement: 41 minutes.

This is a sample of the artifact a connected site can receive — not a claim that Weekly Proof is already sending. The copy stays a preview until a real first send is observed.

Questions

What this is — and what it isn’t

Proof for website leads. Not a replacement for the tools you already use.

Is this a CRM?

No. It is the proof layer for website leads: capture, delivery evidence, acknowledgement, re-notify, and Weekly Proof. Your CRM or email can still be where the relationship happens.

Is this analytics or call tracking?

No. It does not score traffic or attribute calls. It records website form requests and the evidence around each one.

Does it tell me a lead was read?

No. It shows delivery evidence — the notification was accepted by the provider and delivered to the receiving mail server — and whether acknowledgement was observed. It never claims a person read the message.

Is the owner view on this page real data?

No. Everything on this page is a sanitized sample with fictional names and numbers. A real connected site shows the owner their own leads, never anyone else’s.

For agencies

Sell the website. Let RP run the proof layer.

Launch evidence, a tenant-safe owner view, Weekly Proof, and proof-first capture — without building your own lead infrastructure.

Get the partner packet

Take it with you

Send me the demo packet

Get the sample Weekly Proof, the installation-evidence packet, and a walkthrough of how this maps to your site.

You’ve seen the whole system. Want it in your inbox?

The sample Weekly Proof
The installation-evidence packet
The sanitized owner-view walkthrough
How this would map to your site

No account, no “sign in.” A real request that reaches the same proof-first pipeline you just toured.

See your own site

Curious where your current site may be leaking leads?

We’ll do a short teardown of your contact path and show you what a proof-first version would capture.

Book a teardown