Skip to content
Mainland Software

What happens after you hit send on a contact form

· 2 min read · Kelly

People sit on a contact form for weeks. And I get it: contacting a software company feels like stepping onto a sales conveyor you can’t step off, probably one with a retainer at the end.

So here’s exactly what happens after you hit send, at least here and at any company worth talking to. Knowing the script makes it easier to judge whoever you contact, me included.

First: a reply, then a short conversation

You should hear back within a business day, from the person who’d do the work, not a “solutions consultant” reading from a script. The first call is twenty or thirty minutes and it is not a pitch. It can’t be: nobody honest can pitch a solution before understanding the problem.

What it is instead: questions. How does this workflow run today? Who touches it? Where does it hurt? What have you already tried? You do most of the talking. If instead they do most of the talking (about themselves, their process, their proprietary platform), you’ve learned something important early, cheaply.

What to have ready (it’s less than you think)

You don’t need requirements documents or wireframes. You need to be able to show the pain: the spreadsheet, the double entry, the thing someone does every morning. Concrete beats polished. “Watch what happens when an order comes in” is a better brief than ten pages of specifications.

If you can, know which one workflow you’d fix first. Scoped questions get real numbers instead of defensive ones. It’s the single biggest thing you control about how useful the conversation is.

Then: an answer, in writing

After that call you should get one of three responses. A short written scope with a real number and timeline: what it does, what it doesn’t, what happens when you want more. Or “you don’t need custom for this,” with the name of the off-the-shelf tool to buy instead. Or “we’re not the right fit,” ideally with a pointer to who is.

What you should never get: pressure to sign before a number exists, a vague “we’ll figure out billing as we go,” or a proposal thicker than the problem. I’ve catalogued those warning signs elsewhere. The after-contact experience is where most of them first show themselves, which is why the first conversation is so diagnostic.

The part nobody says out loud

A first call is you interviewing them, at zero cost. You can take the scope they write and think about it for a month. You can get three and compare. I’d encourage it, since quotes vary wildly and the spread teaches you more than any single number.

If you’ve been circling a form (mine or anyone’s), this is all that’s on the other side of it: some questions, a written answer, and no conveyor belt. The workflow that’s hurting will still be hurting next month.