Hit rate on pursuits submitted
Better go/no-go decisions should raise the share of submissions that win, even if total submissions fall.
For most civil and structural firms, the proposal is really a qualifications package. Municipal, county and CDOT clients select on experience, team and approach, then negotiate fee. So each RFQ means pulling relevant project sheets, updating resumes, writing an approach narrative and filling an SF330 or agency form. Senior engineers do much of it at night.
A better workflow starts with a quick, structured go/no-go decision, then assembles a first draft from a maintained library of project descriptions, resumes and approach language. The pursuit lead tailors the approach and team, and a principal approves before submission. The library improves with every pursuit instead of being rebuilt.
A short scoring form covers client relationship, past performance with that agency, team availability, competition and fit. The principal decides quickly, and the record helps refine pursuit strategy over time.
Project sheets, resumes, photos, references and approach paragraphs live in one place, tagged by service, client type and agency, with an owner responsible for keeping each current.
For each pursuit, the system pulls the most relevant projects and resumes, fills required agency forms, and drafts an approach outline from past winning language for the pursuit lead to rewrite.
The pursuit lead writes the client-specific approach and confirms the team. A principal reviews and approves the package. Nothing is submitted without that approval.
When selected, the fee proposal draws on actual hours by task and labor category from similar completed projects in Vantagepoint, Ajera or Unanet, giving the PM a grounded starting point for negotiation.
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.
Better go/no-go decisions should raise the share of submissions that win, even if total submissions fall.
Pursuit time is overhead. Reducing it per package protects utilization for the people who also deliver projects.
Shows whether fees priced from history hold up once the project is delivered.
For example, a 45-person civil firm sees a county RFQ for drainage improvements. The go/no-go form takes ten minutes and the principal approves pursuit based on past work for the county. The draft pulls four relevant stormwater projects and current resumes, and fills the required forms. The pursuit lead spends her time on the approach section instead of formatting. The package is ready three days before the deadline. This example is illustrative, not a reported result.
In the first 30 days we would review your last year of pursuits, wins and losses, estimate hours spent on each, and audit the state of resumes and project sheets. Then we would agree a go/no-go form and pick the pursuit type for a pilot library.
Generic approach language is risky whether a person or a tool writes it, because selection committees look for understanding of their specific project. The draft gives a starting structure and relevant past language. The pursuit lead must still write about the site, the agency's concerns and the team's plan. That part should not be automated.
Yes, as a records task. Subconsultant details, certifications and past participation can be kept in the library and pulled into forms. The commitments themselves are decisions for the pursuit lead and principal. We would check each agency's current forms rather than assume a standard layout.
Maybe. If you submit a few proposals a year, a tidy folder of current resumes and project sheets, plus a go/no-go checklist, may be enough. Automation pays back when pursuit volume is steady and the same people keep rebuilding the same content. We would say so in the diagnostic.
Illustrative defaults for an engineering firm. 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.
Proposal and quote automation: 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.