Send a test lead. See who gets it.
Be the customer, then see a clearly labeled owner-side example built from the same live request.
- saved leads.db db - 12ms
- queued notify:ray sent
- delivered ray@raymondporrello.com 1.4s
-> ray notified - sms + email
right now, one inquiry
9:04 pm
someone may have just hit send. only they know it happened.
Most websites treat that as the finish line — send an email, say thanks, done. Harvard sent a real inquiry to 2,241 companies and nearly a quarter never answered it at all. I build the half nobody quotes you on: who gets it, and what happens when nobody does.
No scanner — I read the site myself and write back, usually the same day on weekdays. Nationwide, from Laurel, Montana.
The two branches
same inquiry, two websites, one of them has an owner.
Both forms worked. Both emails sent. Only one of these websites has an opinion about what happens next.
Branch A — the site you have now
- +0s
The form submits
Your customer gets a thank-you page and closes the tab, certain you have it.
- next
The email sends, correctly
The part everyone tests, working exactly as designed, and rarely the part that fails.
- then
It lands at 9:04 pm
Into a shared inbox, under nineteen other things, on the night nobody is looking.
- next day
Two people see it
Each one figures the other has it.
- next try
They try the next name
Someone else answers first, and you never find out this happened.
Nothing here is broken; the inquiry just quietly becomes nobody's job.
Branch B — a site I built
- first
Written down first
Recorded and numbered before anything is handed to email.
- next
They get a reference number
On screen, in writing, theirs to quote back at you.
- then
It goes to your person
Whoever you named for that form — not whoever set the website up.
- your move
Somebody says they've got it
One tap from the notification, meaning they took it, not that they called anyone.
- no answer
Nobody does. It moves.
After the window you set, it goes to the next person on your list.
The same inquiry, on a website that knows whose job it is.
Silence is not proof that nothing happened.
I build the second website. Not because the first one looks bad — because the first one can't tell you what it did with your customer.
The record
Recorded first. Routed second. Accounted for either way.
Every valid submission is recorded and numbered before notification, then goes to the person you named for that form. Lead System adds the layer that notices when nobody takes it and moves it along. You can test the form you already have.
Who answers
The person who builds it is the person who answers.
Before this I ran marketing for a rental company with 32 locations in eight states, where a small broken process just fails 32 times. That handoff, from “someone asked” to “someone answered,” is what I rebuild now. I’m early here and say so — that’s what the demo is for.
Text me for the fastest answer
406-690-7082. A text gets answered faster than anything else here — usually the same day on weekdays.
The form buys you homework
Send your site and I go through it before we ever talk. You start the conversation with findings, not a pitch.
Built so you can leave
No contract, no exit fees, nothing held back. If you ever go, everything goes with you — the domain, the files, every lead.
The build checks itself
Every page is built ahead of time as a file, and the build refuses to finish if it produced anything else. That is the boring half of the job, and it is where most sites quietly give up.
Elsewhere
I run a second practice.
ResolvHQ is my business-intelligence practice — a separate business with its own product and promise. If you came here about data rather than websites, it’s this way.
Free look, no pitch
so — what does your site do with an inquiry?
Send it over. I'll walk the path your customer takes, find where the handoff goes vague, and write it down for you — rebuild or no rebuild. You keep the findings either way.