Most custom software development Austin firms offer a software discovery call before any work starts. The name sounds formal. In practice, it is a conversation with two halves. In the first half, you describe the problem. In the second half, someone tells you what it will take to fix it.
Lately I keep running into owners who want the first half and have no interest in the second. They will spend real time explaining what is broken. When the conversation turns to what the fix requires, they are done. They assume the second half is the sales pitch.
On a good discovery call, it is not. The second half is a plain answer to the question you came in with: this is what is needed to resolve your problem. Sometimes that answer is custom software. Sometimes it is a different tool, a smaller fix, or no new software at all.
This post walks through what happens on a software discovery call, what you should expect from both halves, and how to tell a working session from a sales call in disguise.
A software discovery call is a working conversation in two halves. In the first half, you describe the problem in your own words and walk through one real example of it going wrong. In the second half, the firm tells you what is needed to resolve it: the questions the fix must answer, the size of the work, the risks, and the options, including ones that need no new software.
The call starts with what is bothering you, in your language. Leads land in the CRM wrong. Client intake runs through four people and two inboxes. Month-end takes a week because three spreadsheets have to agree. A good discovery call does not ask you to translate any of that into technical terms. That is the other side’s job.
The most useful question on the call is some version of “walk me through one.” One lead, one order, one client request. Where does it start? Who touches it? Where does it get typed in twice? Following a single item through the business shows more than any feature list. It is where the real problem usually surfaces, and it is often not the one you called about.
Next comes what the problem costs you. Not a formula. The hours your team spends on cleanup. The customers who waited too long. The one person who knows how everything works and cannot take a week off. Owners tend to undercount this part, because the cost has been spread across the week for so long it feels normal.
Most owners have tried something before the call. A new subscription. A spreadsheet that got smarter over time. A family member with an AI tool in the cloud. None of that is wasted. It tells the other side what has failed, what partly works, and how much change your team will tolerate.
Before anyone talks about a solution, the call should pin down what done looks like. Leads land clean with no manual cleanup. Quotes go out the same day. You can be out of the office for a week and nothing stalls. If “fixed” is fuzzy, every estimate after the call will be fuzzy too.
This is the second half, and it is the part owners skip. Here you should get a direct read on the questions the fix has to answer, how big the work is, what could go wrong, and what the options are, including options that do not involve custom software.
For a messy lead flow, that might mean deciding where each lead comes from, what counts as a duplicate, who owns a lead two people have touched, and what happens when a web form changes. None of those questions are hard on their own. Answering all of them before building anything is the work.
Skip this half and you leave with the same problem you brought in, minus an hour.
Step 1: Pick one problem.
Bring the one costing you the most this month, not the full list. One problem explored well beats ten problems named.
Step 2: Pick one example to walk through.
Choose a recent lead, order, or request that went wrong. Know roughly where it started and where it broke.
Step 3: Write down what you have tried.
Tools, subscriptions, spreadsheets, people. Include what partly worked. Partial fixes say a lot about where the real constraint is.
Step 4: Decide what fixed looks like.
One or two sentences. “Leads land clean.” “I can take a week off.” That sentence becomes the yardstick for everything that follows.
Step 5: Plan to stay for the second half.
Block the full time. The answer to “what will it take” is the reason you booked the call. Hear it, even if you decide not to act on it.
Not every problem needs a discovery call with a software firm. If the fix lives inside one tool you already pay for, a settings change or the vendor’s support team may be enough. If you have someone technical in-house with time to own it, start there. Plenty of owners start exactly there, and that is a reasonable instinct.
Outside help makes sense when the problem crosses more than one system, when it depends on one person who knows how everything works, when a fix has already been tried and did not hold, or when getting it wrong costs you a customer, a compliance problem, or a week of your own time. That is also when a discovery call earns its hour, because the second half tells you what you are dealing with before any money is spent.
Systalent’s model is direct senior technical involvement on every engagement. Discovery, architecture, code review, and client-facing decisions stay with the senior technical partner start to finish. That starts on the first call. The person asking about your lead flow is the person accountable for how it gets built.
The goal of the call is the answer: what is needed to resolve your problem. If that answer is custom software development, the next step is scoping it. If you need engineering capacity your team does not have, a dedicated development team may fit better. If a build is already underway and stalling, the conversation turns to software project recovery. If the answer is a settings change in a tool you already own, you will hear that too.
The problem does not change when you stop listening. Leads keep landing wrong, the cleanup keeps eating hours, and the person holding it together keeps holding it together. Hearing what the fix takes does not commit you to anything. It replaces a guess with a plan you can evaluate, whoever ends up doing the work.
If you are an Austin or Round Rock business owner weighing custom software, and you have a problem you have explained more than once, bring it to a working session and stay for the second half. Book a discovery call.
What should I bring to a software discovery call?
One problem, one recent example of it going wrong, a list of what you have tried, and a sentence on what fixed looks like. Screenshots of the tools involved help. You do not need a technical spec.
Will I get a proposal at the end of the call?
Usually not on the call itself. You should leave with a clear picture of what the fix requires and what the options are. A written scope or proposal follows if you decide to move forward.
What if the answer is that I do not need custom software?
Then that is the answer. A good discovery call should tell you when an existing tool, a configuration change, or a smaller fix will solve the problem. Building software you do not need is the most expensive mistake on the table.
Do I need someone technical on the call?
No. The call is built for the person who feels the problem, usually the owner or whoever runs the process day to day. If you have a technical person, bring them for the second half, when the conversation turns to what the build requires.
Billy Knott is the founder and technical lead of Systalent USA, a custom software development company founded in 2003 and based in Austin and Round Rock, Texas. With enterprise technology experience at IBM, Dell, General Motors, the State of Texas, and Q2, Billy works directly with every client to combine senior technical leadership with the engineering team, across custom software development, dedicated development teams, and software project recovery. Learn more about Systalent or connect with Billy on LinkedIn.
Systalent USA is featured among the Best Software Development Companies on DesignRush.