# 5 Bottlenecks Slowing Down AEC Proposal Teams **By Dan Cumberland** · Published August 10, 2026 · Categories: AI Strategy ![Featured image for 5 Bottlenecks That Hide Inside We're Just Busy](https://cms.dancumberlandlabs.com/uploads/5_bottlenecks_that_hide_inside_were_jus_840776dc50.webp) Illustration: Dan Cumberland Labs with Gemini. > 5 structural bottlenecks drain AEC proposal capacity and look like normal busyness. Here's how to diagnose each one — and what to fix. AEC firms that feel perpetually overwhelmed aren't usually understaffed\. They're running into the same five AEC proposal bottlenecks— and calling all of them "we're just busy\." The Lean Construction Institute puts it plainly: > "If you aren't looking for them, they can hide in plain sight, masquerading as 'busyness\.'"[6](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-6) That's the misdiagnosis\. Your BD team isn't tired because you have too much work\. They're losing capacity to five structural constraints that look exactly like normal business volume— and until you can name them, you can't fix them\. Here's what's at stake\. Between 10 and 19% of incoming RFPs go unanswered at capacity\-constrained AEC firms, according to Stargazy's 2026 research[2](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-2)\. For a firm fielding seven RFPs a month at a $2M average contract value, that's significant unexplored revenue sitting on the table\. You're not too busy to respond to those\. You're blocked\. The five bottlenecks hiding inside "we're just busy": 1. SME Availability 2. Content Retrieval \(Not Content Creation\) 3. Go/No\-Go Discipline 4. The Review Cycle 5. Principal Dependency This article is a diagnostic tool, not a solutions pitch\. Each section names a bottleneck, shows what it looks like, explains why it hides so effectively, and gives you a single tell— the signal that distinguishes a structural failure from a genuine staffing problem\. But first, it's worth understanding what makes a bottleneck different from a genuine staffing problem— because the fix for each is completely different\. ## What Makes a Bottleneck Different from Being Short\-Staffed A bottleneck is a specific point where work accumulates faster than it moves through— and hiring around it doesn't clear it, it just moves the pile\. According to Accelo[9](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-9), "When firms feel perpetually 'busy,' the real problem often isn't insufficient staffing — it's invisible operational friction consuming capacity\." That's the distinction that matters\. If you hire one more proposal coordinator and the same problems appear six months later, you have a bottleneck\. If an additional person would genuinely clear the constraint at current volume, that's understaffing\. Different diagnosis\. Different fix\. The signal: does the problem scale with headcount, or with workflow? Accelo's research[9](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-9) also notes that "firms grow around the operational issues instead of actually fixing them, perpetuating inefficiency as they scale\." That's the pattern in AEC BD operations: add a person, feel temporary relief, then hit the same ceiling at higher volume\. Here's a quick way to tell the difference: ```html-table
SignalBottleneckUnderstaffing
Adding one person clears itNoYes
Problem reappears at higher volumeYesNo
Delay always appears at the same pointYesNo
Work piles up even in slower seasonsYesMaybe
``` AEC firms invest 3–5% of net revenue in marketing and BD[5](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-5)\. The question is whether it's hitting the actual constraint\. Firms with formal go/no\-go processes concentrate their pursuit time on higher\-probability work[3](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-3)\. That's a structural advantage, not a staffing advantage\. If you're deciding where to direct that investment, a solid [AI decision framework](/blog/ai-decision-framework-founders) can help you prioritize which constraint to address first before layering in new tools\. Here are the five bottlenecks AEC firms most commonly misread as being busy\. ## Bottleneck 1: SME Availability SME availability is the number one proposal bottleneck in AEC— not because technical subject matter experts \(SMEs\) are uncooperative, but because their participation in proposals is typically unscheduled, unstructured, and competing directly with billable work\. Two independent surveys confirm this\. QorusDocs' 2026 benchmark[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1) found that 64% of AEC proposal teams cite SME delays as their single most prominent challenge— the highest rate across any industry\. Stargazy's 2026 research[2](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-2) independently arrived at 48%\. Both are vendor\-sponsored surveys, but the directional agreement across separate methodologies is meaningful\. What it looks like: 49% of AEC proposal teams report responses regularly taking 6–10 days, with 74% of AEC proposals involving 11 or more contributors[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1)\. Coordination overhead \(not writing speed\) is what determines pursuit capacity\. Coordinators receive raw data from SMEs and spend hours rewriting it the night before submission\. That's not a writing problem\. It's a structure problem\. Why it hides: "Our engineers are slammed with billable work" sounds like a resourcing constraint\. And it is, partially\. But the structural root is that SME participation is undisciplined— there's no template distinguishing a 15\-minute input request from a 3\-hour documentation ask, no scheduled input blocks, no standard format for technical narratives\. **\_The tell:\_** If your proposals routinely include thin technical sections, or your coordinator is rewriting SME emails the night before submission, SME availability is your bottleneck\. If SMEs are the most\-felt bottleneck, content retrieval is the most invisible— because it looks exactly like doing your job\. ## Bottleneck 2: Content Retrieval \(Not Content Creation\) Most AEC firms don't have a content problem\. They have a retrieval problem\. The expertise is there\. It's buried in folders, old InDesign files, and proposals no one can find\. Kantiv \(formerly Joist\.ai\), an AEC proposal AI platform, named the misdiagnosis directly[5](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-5): > "The industry misdiagnoses this as a content generation problem when the actual issue is 'content retrieval\.' One marketing director stated her primary need was 'digging into old proposals' rather than creating new material\." The data is consistent even if the headline figure is vendor\-sourced\. Per Kantiv's research[5](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-5), 80% of AEC proposal content goes unused— a claim with commercial interest behind it, but corroborated by OpenAsset's[4](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-4) finding that only 36% of AEC firms maintain searchable, scalable content libraries\. And 51% of firms still write proposals from scratch "sometimes"[4](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-4)— not because they lack content, but because finding the right version takes longer than rewriting\. The coordinator time cost is significant\. Per Kantiv[5](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-5), proposal coordinators spend 25–40% of total pursuit effort on content retrieval and adaptation\. In a 60–80 hour pursuit, that's 15–32 hours searching and reworking content that already exists somewhere in the firm\. And it's not because coordinators are slow— the content genuinely isn't findable in the time available\. **\_The tell:\_** If your coordinator's first response to a new RFP is to dig through past submissions for the right project description, content retrieval is your bottleneck\. Content retrieval is invisible\. The next bottleneck is the opposite— it looks like BD momentum while actually draining proposal capacity\. ## Bottleneck 3: Go/No\-Go Discipline Firms without a formal go/no\-go process aren't doing more business development— they're spreading the same proposal capacity across more low\-probability pursuits and leaving less for the ones they can win\. Only 40% of AEC firms consistently use a formalized go/no\-go process, according to the 2025 Unanet AEC Inspire Report[3](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-3)\. The other 60% make pursuit decisions informally\. "We know this client, let's go for it\." That sounds like momentum— and for a firm at the right stage, relationship\-driven pursuit can be a genuine edge\. But when it becomes the default for every RFP regardless of probability, you're chasing pennies when you could be chasing dollars\. The win rates tell the story\. The math matters\. QorusDocs[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1) found that 44% of AEC firms cannot complete 20–29% of incoming RFPs due to capacity constraints\. Meanwhile, 71% of AEC firms report new\-client win rates of 25–49%, with only 21% exceeding 50%[2](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-2)\. Selective firms cluster in the upper range\. Undisciplined pursuit spreads coordinator time across proposals the firm is unlikely to win, which means less time for the ones they can\. The pattern compounds invisibly\. One firm discovered they had an almost guaranteed loss rate when pursuing public institutions requiring a local partner— only after analyzing their win/loss data[8](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-8)\. They had been spending proposal capacity on those pursuits for years before the data made it visible\. The go/no\-go process exists precisely to surface that kind of information before you spend the hours\. There's also a governance dimension\. When pursuit decisions are undocumented and informal, you can't learn from them\. Building an [AI governance strategy](/blog/ai-governance-strategy) for AEC BD often starts here: structuring the decision framework before adding tools on top of it\. **\_The tell:\_** If your team is simultaneously working 8–12 pursuits of widely varying probability, or if go/no\-go decisions are never documented, this is your bottleneck\. Even firms that manage go/no\-go well often have a constraint they can't see— one that shows up in the final 48 hours\. ## Bottleneck 4: The Review Cycle The proposal review crunch at submission isn't a time management failure— it's what happens when quality review is treated as the last step instead of the first\. OpenAsset's research[4](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-4) found that 87% of AEC proposals undergo 2–5 revision rounds, and 64% of teams submit on the deadline day itself\. That's not coincidence\. It's a structural pattern: review is concentrated at the end, when changes are expensive \(writing time compressed, versions multiplying, error risk elevated\), instead of at the beginning, when compliance gaps are free to fix\. ```html-table
When review typically happensWhen it should happen
Final 48 hours (writing compressed, versions multiplying)Day 1: requirements and compliance check
After the narrative is writtenWeek 1: win strategy and approach sign-off
When changes are expensiveBefore writing begins, when changes are free
``` What it looks like: everyone weighs in during the final 48 hours\. Pages get rewritten\. Versions multiply\. Compliance checks happen alongside final formatting\. The team is stressed, the document is chaotic, and quality suffers— not because people are bad at proposals, but because review was never scheduled earlier\. The structural fix is conceptually clear\. Compliance review at kickoff, when requirements are fresh\. Win\-strategy alignment before writing begins, not at submission when it's too late to change direction\. A principal sign\-off on the pursuit narrative in week one, not week three\. The last 48 hours should be for polish, not decisions\. Why it hides: "Everyone needs to weigh in" sounds like thoroughness and commitment to quality\. But thoroughness that only activates at the end isn't quality control— it's crisis management\. **\_The tell:\_** If your team's most stressful moment is the 48 hours before submission, or if you've caught a compliance issue after submission, this is your bottleneck\. The review cycle is fixable with process\. The next bottleneck isn't— it requires a different conversation entirely\. ## Bottleneck 5: Principal Dependency The fifth bottleneck is the ceiling that hiring can't raise\. When the firm's principals own go/no\-go decisions, win strategy, technical review, and often the final draft, their available hours outside billable work set the maximum number of simultaneous pursuits— full stop\. HotDog Marketing[7](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-7) observed this directly: "Marketing teams in AEC firms are either overwhelmed or nonexistent, with principals writing proposals on weekends\." In our experience with AEC BD teams, this holds across firm sizes— not because principals don't trust their coordinators, but because no system yet exists to carry their judgment without them\. Why it hides: "We need principal involvement for quality" sounds like a standards commitment\. In firms without systems, it is\. The principal's judgment is the only consistent quality control\. But that's not a people problem— it's a systems problem\. The knowledge that should live in documented standards, pursuit filters, and narrative templates is still locked in the principal's head\. The capacity ceiling is hard\. That ceiling doesn't scale with the coordinator headcount below it\. A second coordinator doesn't get more principal review hours\. It just creates more drafts waiting for the same bottleneck\. The real fix isn't removing principals from proposals\. It's building systems that extend their judgment without requiring their constant presence— captured win criteria, documented pursuit filters, technical narrative templates derived from their standards\. Building [AI culture across your firm](/blog/building-ai-culture) often starts here: capturing what your principals know so their expertise doesn't bottleneck every pursuit\. **\_The tell:\_** If the answer to "who writes the win strategy?" and "who reviews the final draft?" is consistently one or two names, principal dependency is your bottleneck\. So which one is yours? ## Diagnosing Your Bottleneck — And Where AI Actually Helps Most AEC firms have more than one of these bottlenecks— but one is the binding constraint at any given time\. Fix that one first, and the others often get easier\. Here's the thing: you can't read the label from inside the bottle\. When you're running 11\+ pursuits simultaneously, every bottleneck feels equally urgent\. But the constraint usually shows up at the point where work piles up longest— that's where the structural friction lives\. The sequence matters more than most firms realize\. Go/no\-go discipline \(Bottleneck 3\) is upstream of everything else\. Undisciplined pursuit multiplies the impact of every other bottleneck: more SME asks, more content retrieval churn, more compressed review cycles, more principal hours burned on low\-probability work\. Fix pursuit selection first\. The volume running through every other constraint drops immediately\. Once you've identified the structural constraint, [AI implementation workflows](/services/ai-implementation) have a clear role— removing friction, not manufacturing capacity: - **SME delays** → A structured prompt that converts a 15\-minute SME input into a full draft technical narrative— so the coordinator stops rewriting from email the night before submission - **Content retrieval** → AI\-powered content search that surfaces the right project description without digging through seven years of folders and old InDesign files - **Review cycle** → AI compliance pre\-checks at kickoff, not submission— catching gaps when they're cheap to fix - **Principal dependency** → AI\-captured institutional knowledge— win criteria, pursuit standards, the judgment calls principals make on every narrative— so principals spend less time on each individual pursuit The key phrase is "removing friction\." AI doesn't manufacture proposal capacity\. It gives back the hours that structural dysfunction was stealing\. After fixing the bottleneck, [measuring AI success](/blog/measuring-ai-success) becomes straightforward: fewer missed RFPs, faster timelines, higher win rates on the opportunities you actually select\. If the diagnosis feels clear but the path to fixing it doesn't, that's exactly the kind of operational analysis [Dan Cumberland Labs](https://dancumberlandlabs.com) works through with AEC firms\. The five bottlenecks look like busyness because they're embedded in busyness\. SME availability, content retrieval, go/no\-go discipline, review cycle, and principal dependency— each one consumes real hours from real people doing real work\. Naming them doesn't add capacity\. It lets you stop applying the wrong fix\. ## FAQ ### What is the most common proposal bottleneck in AEC? SME availability delays are the most commonly cited AEC proposal bottleneck— named by 48–64% of AEC proposal teams depending on the survey\. The problem isn't that technical staff won't contribute; it's that their participation is typically unscheduled and untemplated, competing directly with billable work\. QorusDocs[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1) and Stargazy[2](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-2) both confirm this independently, from separate survey populations\. ### What percentage of AEC firms have a formal go/no\-go process? Only 40% of AEC firms consistently use a formalized go/no\-go process, according to the 2025 Unanet AEC Inspire Report[3](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-3)\. The other 60% make pursuit decisions informally— which spreads proposal capacity across low\-probability RFPs and limits effective throughput on the opportunities worth winning\. ### Why do AEC proposals take so long? Coordination complexity determines response timelines more than writing speed\. 74% of AEC proposals involve 11 or more contributors[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1), and 49% of firms report that responses regularly take 6–10 days[1](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-1)\. SME delays, content retrieval, and late\-stage review crunch all compound— each adding time to a schedule that was already tight\. ### What is the average AEC proposal win rate? Approximately 40% overall\. 71% of AEC firms report new\-client win rates of 25–49%, with only 21% consistently exceeding 50%[2](/blog/blog-5-bottlenecks-that-hide-inside-we-re-just-busy#ref-2)\. Firms that apply formal go/no\-go discipline and selective pursuit strategies tend to cluster in the upper range— the advantage comes from working the right opportunities, not from submitting more of them\. ## References 1. QorusDocs, "Top AEC Proposal Management Trends from the 2026 Benchmark Report" \(2026\) — [https://www\.qorusdocs\.com/blog/top\-aec\-proposal\-management\-trends\-from\-the\-2026\-benchmark\-report](https://www.qorusdocs.com/blog/top-aec-proposal-management-trends-from-the-2026-benchmark-report) 2. Stargazy, "4 Numbers Every AEC Proposal Leader Should Know in 2026" \(2026\) — [https://stargazy\.io/resources/4\-numbers\-every\-aec\-proposal\-leader\-should\-know\-in\-2026](https://stargazy.io/resources/4-numbers-every-aec-proposal-leader-should-know-in-2026) 3. Unanet, "A Comprehensive Look at the 2025 AEC Inspire Report: Key Insights and Strategic Takeaways" \(2025\) — [https://unanet\.com/blog/a\-comprehensive\-look\-at\-the\-2025\-aec\-inspire\-report\-key\-insights\-and\-strategic\-takeaways](https://unanet.com/blog/a-comprehensive-look-at-the-2025-aec-inspire-report-key-insights-and-strategic-takeaways) 4. OpenAsset, "Proposal Efficiency 101: Practical Methods to Streamline Workflows" \(2024–2025\) — [https://openasset\.com/resources/proposal\-efficiency/](https://openasset.com/resources/proposal-efficiency/) 5. Kantiv \(formerly Joist\.ai\), "Why 80% of AEC Proposal Content Goes Unused" \(2025–2026\) — [https://www\.kantiv\.com/post/aec\-proposal\-content\-black\-hole](https://www.kantiv.com/post/aec-proposal-content-black-hole) 6. Lean Construction Institute, "How to Detect and Reduce Bottlenecks in Design and Construction" \(2024–2025\) — [https://leanconstruction\.org/blog/how\-to\-detect\-and\-reduce\-bottlenecks\-in\-design\-and\-construction/](https://leanconstruction.org/blog/how-to-detect-and-reduce-bottlenecks-in-design-and-construction/) 7. HotDog Marketing, "AEC's Capacity Crisis: Texas Firms Are Struggling into 2026" \(2025–2026\) — [https://hotdogmarketing\.com/aec\-capacity\-crisis/](https://hotdogmarketing.com/aec-capacity-crisis/) 8. Dragonfly AEC, "Smarter AEC Business Development Starts with Better Filters" \(2025–2026\) — [https://www\.dragonflyaec\.com/post/smarter\-aec\-business\-development\-starts\-with\-better\-filters](https://www.dragonflyaec.com/post/smarter-aec-business-development-starts-with-better-filters) 9. Accelo, "Hidden Bottlenecks in Your Workflows" \(2024–2025\) — [https://www\.accelo\.com/post/hidden\-bottlenecks\-in\-workflows](https://www.accelo.com/post/hidden-bottlenecks-in-workflows) --- **How we made this article:** We use AI in our research and writing so our small team can share more of what we learn. We verify the sources and take responsibility for every article we publish. [Read how we use AI.](https://dancumberlandlabs.com/how-we-use-ai/) --- ## About the author **Dan Cumberland** — Founder, Dan Cumberland Labs Dan Cumberland helps engineering and construction firms see where they stand with AI and decide what to build first. He created Pacemark, the AI maturity model behind that work, from research on more than 300 companies. - Take the assessment: https://pacemark.ai/signal/assessment/?track=aec&utm_source=dcl-site&utm_medium=link&utm_campaign=pacemark-assessment - Book a call: https://book.dancumberland.com/ai-strategy --- Source: https://dancumberlandlabs.com/blog/5-bottlenecks-that-hide-inside-we-re-just-busy/