right now, one inquiry

9:04 pm

someone may have just hit send. only they know it happened.

On most websites, what happens in the next two seconds isn't written down anywhere — so the only person who knows they contacted you is them, and the next form is still one click away. I build the kind that writes it down first, so you can check. Keep scrolling: one inquiry, two websites.

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 wrote it down.

One of them wrote the inquiry down before it tried to email anyone. The other didn't.

Branch A — the site you have now

  1. +0s

    The form submits

    Your customer gets a thank-you page and closes the tab.

  2. next

    Handed off to email

    Nothing was written down before that.

  3. then

    Filtered, quietly

    No bounce, no error, no log.

  4. next try

    They try the next name

    Someone else may answer first.

  5. next day

    A conversion may be counted

    The report can look fine while the inquiry never reaches you.

A job, a case, or a client can disappear with nothing to show the inquiry existed.

Branch B — a site I built

  1. first

    Written down first

    Saved before anything is handed to email.

  2. next

    They get a reference number

    On screen, in writing, theirs to quote back at you.

  3. then

    Notification work is queued

    The alert enters the system without claiming that anyone has seen it.

  4. your move

    You decide what happens next

    The website cannot make the reply; it keeps the customer details ready when you do.

  5. any day

    The submission stays saved

    Connected exposes the owner trail; base builds keep capture and email notification separate.

The inquiry is saved before notification, whether or not anyone replies.

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

Saved first. Notified second. On the record either way.

Every valid submission is saved before notification and gets a reference number. Connected adds the private owner trail; the base builds use email notification without that dashboard. You can test the form you already have.

Send a test lead. Watch it get caught.

Be the customer, then see a clearly labeled owner-side example built from the same live request.

lead capture - live #LR-4F2A91

name
A New Lead
source
google - cpc
query
"website design billings"
captured

  • saved leads.db db - 12ms
  • queued notify:ray sent
  • delivered ray@raymondporrello.com 1.4s

-> ray notified - sms + email

One request, one reference number, one labeled owner-side example.
Run the 60-second test

Who answers

The person who builds it is the person who answers.

No account managers, no ticket queue, no “let me check with the developer.” I’m the developer.

I’m also early, and I won’t pretend otherwise — which is why the demo exists: when you can’t point at a wall of logos yet, you’d better be able to show the thing working.

Ray Porrello — Laurel, MT
Ray Porrello — Laurel, MT
  • 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.