Proposals built from the estimate you issued
Write the proposal from the issued estimate instead of retyping it into a document, so the price, scope, assumptions, and exclusions the client reads match what the team priced.
Who it’s for
Commercial managers, estimators, and business development leads who send the bid. Approvers who sign off price and terms before it leaves the company.
The practical task
Turn a priced scope into a client-ready document without retyping totals, and make sure the assumptions and exclusions travel with it.
What you do and produce
You start from a template, pull pricing and scope from the estimate, add assumptions, exclusions, and clarifications, apply your branding, and route it for approval. Assistance can draft sections from stored project data for you to edit. The output is a reviewed proposal and PDF tied to the project.
How that output helps another team
The project team inherits the scope, assumptions, and exclusions the client accepted, on the same record that procurement and project controls already use.
Example
On the public Red Mesa Solar demonstration, the proposal carries the foundation package from Estimate Rev 04: 12,400 piles at $218, with the geotechnical assumption and the exclusions the estimator recorded. See the platform tour.
Status today
Proposal templates, branding, pricing, drafting, approvals, and PDF export are in the product. Sending the proposal and capturing an e-signature inside Infrenta are planned, not available yet.
Rules that keep proposals consistent
Company rules can require approval above a margin or value, add standard assumptions and exclusions, and select a template by project type. Rules are declarative; no custom code runs inside them.
Next step
See module pricing or book a demo to walk your own proposal workflow.