Bids with a recorded outcome
The first goal is simply knowing; every bid should close out with a result.
A GC might submit 15 or 20 bids a month, and many simply disappear. The estimator moves on to the next bid day, the owner or GC goes quiet, and nobody asks whether the project was awarded, delayed or lost on price. That silence costs twice: missed chances to negotiate now, and no data on why you lose later.
A scoped follow-up process logs every submitted bid with its due date, decision date and contact, sends scheduled reminders to the estimator or business development lead, and drafts short check-in emails for review. Results, including the winning number when shared, are recorded so the company can see hit rate by client, project type and size.
Each submitted bid or proposal is entered once in the CRM or a shared list with value, client, decision date, contact and owner, ideally fed from the bid calendar.
Hard bids get a check-in after the expected award date; negotiated proposals get touches at three, seven and 14 days. The person who owns each bid gets the reminder.
AI drafts a short, specific email referencing the project and any open questions, which the estimator or PM edits and sends from their own account.
Every bid ends as won, lost, no-go or cancelled, with a reason and the winning number when the client is willing to share it.
Leadership reviews hit rate and loss reasons by client and project type each month, and adjusts which invitations are worth pursuing.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
The first goal is simply knowing; every bid should close out with a result.
Confirms that follow-up actually happens, and happens quickly.
Guides which invitations are worth the estimating hours.
Where follow-up most directly affects revenue.
For example, a GC reviews its last quarter and finds 52 submitted bids, 19 of which have no recorded outcome. After setting up the bid log and reminders, follow-ups reveal that six were awarded elsewhere, four are on hold waiting on financing, and two owners are still deciding and invite the team to a scope review meeting. The numbers here are illustrative and would be measured during the pilot.
We would gather the last three to six months of submitted bids, mark which have known outcomes, and estimate the follow-up time spent today. Then we set up the bid log and reminder rules on one estimator's work for a month before rolling the process out to the whole team.
Not if it is short, specific and timed to their decision date. A note asking whether the project is still on schedule, or whether any scope questions remain, is normal practice in the industry. The goal is useful contact, not a marketing drip campaign.
Not always. A well-kept shared list with reminders can work for a small team. If you also want to track relationships with owners, architects and developers over years, a CRM like HubSpot becomes worth the setup. We would decide based on volume and who does the follow-up.
Ask simply and soon after the decision. Many owners will tell you whether you were close, high, or lost on schedule. A rough reason recorded for most bids is far more useful than a detailed debrief on a handful.
Illustrative defaults for a general contractor. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Quote and estimate follow-up: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.