What to Put on Your Contact Page So People Write Back

The Form That Answers Nothing

Someone finds you because they have a real problem and real intent. They arrive on your site wanting three answers:

1. Can this person solve my problem?
2. Have they done it for someone like me?
3. What will it cost, roughly?

Instead, they get a form:

“BOOK A DEMO” “Please enter your business email, phone number, company headcount, annual software budget, and physical billing address to speak with an inbound sales development representative.”

The funnel below is a caricature of a process that answers nothing; the timings are illustrative.

┌──────────────────────────────────────────────────────────────────────────────┐
│                   THE CONTACT GAUNTLET AND WHAT IT COSTS YOU                 │
├──────────────────────────────────────────────────────────────────────────────┤
│ 1. Visitor arrives with a real need and real intent                          │
│ 2. Hits a 'Book a demo' wall: eight fields, nothing answered                 │
│ 3. Automated calendar picker: earliest slot is six days out                  │
│ 4. Thirty-minute call with someone who is not doing the work                 │
│ 5. That person asks a colleague and waits for them                           │
│ 6. Forty-five minute demo, still no prices, promise of a custom proposal     │
│ 7. Proposal arrives two weeks later, by which point they have forgotten you  │
├──────────────────────────────────────────────────────────────────────────────┤
│ RESULT: the person who wanted to hire you has had to do your research for    │
│ you, and you have still not told them what anything costs.                   │
└──────────────────────────────────────────────────────────────────────────────┘

None of this is a scam. It is what happens when a site treats the contact page as a gate rather than a page. You are not protecting yourself from the wrong clients. You are making the right ones wait, and the wrong ones sometimes get in anyway.

1. Most People Never Fill In Your Form

Here is the part that changes how you think about this: the people who hire you are mostly not the people who contact you. Most visitors read, decide, and either get in touch quietly or pick the competitor down the road. You never learn which.

The site is therefore the part of the sales process that works while you are asleep, and the contact form is only the last step of it. If the page above the form answers nothing, the form is asking the visitor to do your selling for you.

That is also why hiding the price is not a filter. A visitor who cannot find a number has one of two reactions: they assume the worst, or they assume the worst. Either way they leave.

Forcing someone to book a call to see pricing, scope or timing is friction with no upside. Every extra step costs you people who were genuinely interested, and the only ones who push through are the ones who had already decided.

2. What to Put on the Page

A. The scope, and what it costs

This is the part most sites leave out, and it is the part that does the work. A visitor who knows the range can tell you in one sentence whether you are relevant. A visitor who does not know has to take your word for everything.

Put it in plain numbers, on the page:

• A business website of one to three pages: $1,200 to $1,900, built in about two to three and a half weeks.
• A larger site of four to seven pages: $1,550 to $2,450.
• An online store: $1,800 to $2,900, three to five weeks.
• A small automation: $900 to $1,600.

These are our own published prices — the same ranges we print on our service pages and on our estimator page — not industry averages.

Also say what is not included, because that is the question people actually have. “The quote covers design, build, your content, the launch and the handover. Photos, copywriting and a logo are yours to provide, and we can help with those separately.”

If you would rather not publish numbers, publish the estimator. Ours is at auralogic.dev/estimate: a visitor picks what they need, sees a real price range, and arrives in your inbox already knowing the number. A range is enough. The point is that they are not guessing.

B. Evidence, not praise

“Aura Logic was great to work with!” tells a visitor nothing, because every studio writes that sentence. What convinces them is a specific story:

• What was broken, and what it was costing.
• What you changed, and what you chose not to change.
• What happened afterwards, in a number.

One honest example — a slow site that became fast, a form that started working, a store that took orders — does more than six badges and a wall of logos. If you have not published one yet, the next project is the one to publish.

C. A direct line to the person who will do the work

Connect the visitor with the person who will actually build it, not a shared inbox that nobody owns. At our size this is simple: the person who does the work answers the email, and you get to talk to the person who wrote the code.

That is also a selling point. People buying a website are nervous about being handed to a stranger after the call, and you can say plainly that it will not happen.

D. What happens after they write

Say it on the page, in one line:

Send the address of the site you want to improve, two sentences about the problem, and the date you need it live. We reply within one working day with either a scope and a price, or an honest no.

That last part matters more than it looks. A studio that will tell you when you are not the right fit is a studio you can believe when it says yes. It is also what makes people write back: the visitor can see who will read the message and what will happen next.

3. What Changes

You are not going to get a magic close rate from publishing prices. What you get is fewer conversations that were never going to work, and faster ones that are.

The last row is the one most people miss: when the page answers the questions, you can see which parts of it produced the enquiry. That is how you stop guessing.

Conclusion: Respect the Reader’s Time

The advantage of publishing scope, price and proof is not a clever tactic. It is that the person reading has a real problem and a real life, and the fastest thing you can do for them is answer the questions they came with.

Put the numbers on the page. Show the work. Make it easy to reach the person who will do it, and say what happens when they do.

Give people enough to decide without you in the room, then be easy to reach.