Qualify before you quote: six answers, one decision

The six answers to get on the first call before you write a proposal, the question to ask for each, and the rule that decides if the proposal gets written.

Salva Sanchiz

Salva Sanchiz · Founder & CEO

/ 10 min read / Art. #39

A services proposal costs an evening. You measure, you scope, you price it, you write it up, and then you format it so it does not look careless. None of that is billed. A share of it goes to jobs that were never going to close, and you find out three weeks later when the reply never arrives.

Qualifying before you quote means getting six answers on the first call and using them to decide whether the proposal gets written at all. The six are the job, the money, the decider, the date, the alternative, and the next step. Each one has a question you can say out loud without sounding like a form. Each one has a field on the record, so the answer is still there when you sit down to write.

The decision that follows has three outcomes. Write the full proposal, send a short quote, or decline and say why. Most of what goes wrong in a small services business happens because only the first two exist.

The pattern is not new to anyone who has been doing this a while. In a thread called "Quoting jobs" on r/smallbusiness, posted on 27 July 2026, an operator described his own version in one line: "Before I spend hours measuring, pricing and putting together a proposal, I try to qualify the job first." The thread filled up with other people's informal filters. None of them wrote any of it down.

What the qualification frameworks are built for

Search for how to qualify a lead and the first page belongs to BANT and its descendants: budget, authority, need, timeline, plus a list of forty discovery questions to work through. The advice is accurate. It works in the company it was written for.

That company has sales reps, a manager who runs a pipeline review on Thursdays, and someone whose job is deciding which deals a rep is allowed to spend the week on. Qualification there is a handoff between two people. The rep gathers the answers, the manager reads them, and the answers get typed into a CRM because a second person needs to see them.

You take the call and you write the proposal the same night. Nobody reads your pipeline with you. That changes two things. The cost of a bad call lands on your own unpaid hours rather than on a forecast, and the answers have nowhere to go, because the person who would have read them is you, six days later, from memory.

The other gap on that first page is what happens after the questions. Most guides give the list and stop. By the second call the budget has become "somewhere around twenty thousand, I think", and the name of the person who has to sign is gone entirely.

The six answers

Six answers, one call. You do not need them in this order and you do not need to read them off a script. You do need all six before you decide anything.

# The answer What you are actually asking The field on the record
1 The job What they want done, in their words, in one sentence you can read back to them Requested work (long text)
2 The money A number or a band they have said out loud, not one you guessed Budget band (single select)
3 The decider Who signs, and who else has to be happy before it starts Decision maker (link to a contact) and Others involved
4 The date When they need it live, and what makes that the date Needed by (date) and Why that date (text)
5 The alternative What happens if they hire nobody, and who else they are speaking to Competing option (text)
6 The next step One named action with a date, agreed while you are still on the call Next step (text) and Next step date (date)

1. The job

"Say the outcome you want in one sentence, and I will read it back to you before we go any further."

Reading it back is the whole move. You will get it wrong the first time, they will correct you, and the corrected sentence is worth more than the twenty minutes of description that preceded it.

Put that sentence in Requested work in their words, not in yours. A client who asked for "a way to stop losing quotes in my email" has told you something a field labelled "website redesign" would have thrown away. When the proposal disagrees with what they think they asked for, this is the field that settles it.

2. The money

"Work like this usually lands between [your low] and [your high]. Does that sit inside what you had in mind?"

Then stop talking. The silence after that question does more work than anything else you say on the call.

Naming your own range first is what makes the question answerable. Asking "what's your budget?" cold puts the client in the position of guessing a number and hoping it is not embarrassing, and the safest thing for them to say is that they do not have one yet. Give them a band to react to and reacting is easy. An agency owner made the same argument in a thread on r/agency from 17 December 2025, titled "Talking About Money Is Not Rude. Avoiding It Costs You": raising money early clarifies intent and tells you whether to keep going.

The answer goes in Budget band as a single select, not as free text. A text box collects "around 10k", "10-15", "£10,000ish" and "not sure yet, maybe 10?", which is four spellings of one band and nothing you can filter on. A closed select can be counted at the end of the quarter.

3. The decider

"Besides you, who else has to be happy with this before it starts?"

That phrasing does something "are you the decision maker?" cannot. Nobody enjoys being asked whether they are important. Everybody is happy to name their business partner, their operations lead, or the spouse who signs off on anything over five thousand.

Decision maker links to an actual contact record rather than holding a name as text, so the proposal goes to a person you have already spoken to or already know you have not. Others involved holds the rest. A job with three names on it and no conversation with any of them is the most reliable predictor of a proposal that gets read once and never answered.

4. The date

"When do you need this live, and what happens on that date?"

The second half is the part that matters. "March" is a preference. "March, because the trade show is on the 14th and the stand has the URL printed on it" is a deadline, and the two behave completely differently once your calendar gets tight.

Needed by is a date field so it sorts. Why that date is a text field holding the reason, and it is the single most useful line to reread the week before you deliver.

5. The alternative

"If you do nothing about this for six months, what does that cost you?"

Every job you quote for competes with three other outcomes: another supplier, an internal fix, and nothing at all. Nothing at all wins more often than any named competitor, and it never shows up on a pipeline board because nobody enters it.

Ask who else they are speaking to in the same breath, without any edge to it. Most people will tell you straight. Competing option holds whatever comes back, including the honest answer of "we'd probably just keep doing it in the spreadsheet", which tells you exactly what your proposal has to beat.

6. The next step

"I can have this to you by [day]. Can we put fifteen minutes in the diary for [day + 2] to go through it together?"

A call that ends with "I'll send something over" has no next step. It has a hope. The proposal lands in an inbox on a Thursday afternoon, it competes with everything else in that inbox, and the follow-up becomes your job for the next fortnight.

Agree the action and the date while you are both still on the phone. Next step holds the action and Next step date holds the day, and a saved view of every open deal sorted by Next step date is the closest thing to a working to-do list a small business gets out of a CRM.

The decision: write it, short quote, or decline

Six answers, then one decision, taken by you. No points, no weighting, no score. Count what you actually have and read off the row.

Write it

All six answers present, and the money and the decider are both real. This is the only case that earns a full proposal, with the scoping, the pricing detail, and the evening it takes.

"Real" is doing work in that sentence. A budget band the client said out loud is real. A band you inferred from the size of their office is not. A decider you have a name and a role for is real; "I'll have to run it past the team" with no names is not.

Short quote

Four or five answers present, with the money and the decider among them. Send one page: a price, a scope line, and what you need from them to start.

The short quote is the option most small businesses never use, and it is where the hours come back. One page is the right document for a job you can price in ten minutes and a client who has not yet given you enough to write anything longer. If it comes back with questions, you have earned the full version and you now have the answers you were missing.

Decline

The money or the decider is still missing after you have asked twice. Say so kindly and leave the door open.

"I do not think I am the right fit for this one right now, mostly because we have not been able to land on a budget that works for both of us. If that changes, write to me and we will pick it up."

Send it and mean it. The person on the other end has not been asked these six questions by anyone, including you, until today. Some of the people you decline come back months later with a number attached, and those ones arrive already qualified, which is the argument for saying no in a way you would be happy to read.

Then fill in one more field before you close the tab.

Lost reason, the field almost nobody keeps

Lost reason is a closed single select, filled in at the moment you decline or the moment they go quiet. Four values are enough to start: Budget, Timing, Chose someone else, and Went quiet.

One field, one click, at the only moment you will ever know the answer. A week later you will not remember, and a quarter later the whole shape of the last three months will be gone.

Read the column once a quarter. Group by value and count. A column that comes back half Budget means you are asking the money question too late in the call, or not asking it. Half Went quiet means your calls are ending without a Next step date. And when most of it says Chose someone else, your problem lives in the proposal rather than in the qualification, which is a different piece of work, but at least you now know which one to do.

That quarterly read is the same twenty-minute habit as a dormant client audit, run on a different column.

Set your own budget bands

Budget band only works as a closed list, which means somebody has to decide what the options are. Do it from your own last twenty jobs rather than from anyone else's guide.

Open the last twenty, write down what each one was worth, and cut the list into four groups with roughly even weight. A starting shape, in your own currency: under 1,000, then 1,000 to 5,000, then 5,000 to 15,000, then over 15,000, plus a fifth value of "not said" that you will use more than you expect. Those numbers are a shape to copy and nothing more. They are not market data, and a photographer, a plumber, and a brand consultancy will each end up with a completely different set.

Four or five values is the right size. Ten bands means nobody picks the same one twice and the column stops being countable, which puts you back where the text box had you.

What a CRM holds here, and what it does not

Syncek does not write proposals, send them, track opens, collect a signature, or raise the invoice at the end. None of that is on the roadmap. Your proposal lives wherever it already lives, in a document template, in proposal software, or in a spreadsheet you have used for years.

What we hold is the record and the decision that comes before the document. Requested work is a long text field. Budget band and Lost reason are single selects on lists you define once. Decision maker is a relation to a contact, one of the 20+ field types, so the link exists from both ends. Needed by, Next step date, and the rest are real date fields, which means they sort, filter, and save into a view your team opens exactly as you do.

The call does not log itself. There is no Gmail sync, no calendar sync, and no AI reading your conversations. You write the six answers onto the record while the call is still fresh, which takes about ninety seconds and is the only part of this that requires discipline.

If you want to run this on your own book, Syncek offers a 15-day free trial of the Business tier with full access and no credit card. Pricing is published on the site: Starter at $29, Pro at $49, and Business at $89 per seat per month, with 20% off on annual billing. Export to CSV or JSON anytime, including after you cancel.

Get the guide

We've prepared a guide to keep on hand while you build or audit your CRM. 16 pages, A4.

Download the six-answer qualification card (PDF)

The qualification guide is 16 A4 pages: the six answers, the question to ask for each one, the field the answer goes in, the test that separates a real answer from a placeholder, and the write / short quote / decline rule.