Cascade: public RFP discovery and proposal workflows for AEC firms

AEC bid software should close the loop from RFP to proposal.

Cascade describes a platform for finding public projects, scoring opportunities by fit, writing proposals, and analyzing project specifications. Its September 20 homepage marks government project discovery, proposal writing, and project-spec analysis as live; pre-bid intelligence, private-market signals, bid leveling, and teaming are marked as coming soon.

That status split is the product boundary. A buyer should evaluate the live path without assuming the roadmap is already part of the workflow.

Buyer and workflow

The target is an architecture, engineering, and construction firm that finds work across government portals and spends weeks preparing bids. Cascade says it can scan public portals for projects that fit the firm’s scope, timeline, and project history, then help turn the selected opportunity into a proposal.

The concrete workflow is: identify an opportunity, score its fit, analyze the project specification, draft the proposal, and leave the final commercial decision with the firm.

That is more useful than calling it an “AI proposal writer.” The buyer can ask where the source RFP appears, which capability signals determine fit, and how a reviewer corrects a scope interpretation.

First evaluation

Use three public RFPs: one obvious fit, one adjacent fit, and one poor fit. Check whether the system exposes the source, explains the fit decision, identifies missing requirements, and keeps the proposal tied to the underlying specification. Do not use the page’s time or opportunity figures as independent results.

Keep the roadmap labels intact. A team should not buy a workflow on the assumption that private-market signals, bid leveling, or teaming are live if the current page marks them “soon.”

Data boundary

Cascade’s saved privacy page is labeled for an Excel add-in and describes personal data, usage data, installation information, error logs, and service providers. The public packet does not establish the exact data-processing boundary for every platform workflow. Procurement should request that information before connecting an ERP or internal project history.

Pricing is not established by the cited pages. The product’s public choice is clearer: start with a public-project discovery and proposal loop, then ask whether the same source trail survives into the submitted bid.

Sources checked — September 20, 2026: Speedrun profile, Cascade homepage, and Cascade privacy page.