Send your first proposal

A proposal in STrOp isn't a separate document you assemble — it's a view over your estimate. The numbers come from the estimate revision; the proposal adds the addressee, the scope narrative, the qualifications, and control over what the GC actually sees. That means the price on the paper is always the price in your system, and a revised estimate gets a fresh proposal instead of a stale PDF.

What you need

  • A pursuit with an estimate priced far enough to stand behind.
  • The GC and contact in your directory so the proposal can address itself.

Build it

  1. Open the project → Proposal (or from the Proposals directory (/proposals), where a pursuit without one shows Create →). There's no "new proposal" button on the project — walking onto the tab creates the draft from the current estimate revision automatically.
  2. The builder is two panes: Settings on the left, the live document on the right. Address it — GC / Addressee, Prepared For — and set the proposal date, expiry, and the plans-and-specs date you priced from (that date is your scope anchor if the drawings move later).
  3. Write the scope narrative and check your qualifications and clauses — the words that say what the number includes, which is what proposals are actually for.
  4. Shape the output: Package totals or Line detail, and uncheck any lines the GC shouldn't see itemized. Hidden lines still count in the total — you're controlling presentation, not the math.

Send it

  1. ⎙ Print / PDF in the preview toolbar produces the document. Delivery is yours — attach it to the bid email, upload it to the GC's portal, hand it across the table. STrOp doesn't email it for you.
  2. Set the status to Submitted. That's the system's record that the bid is out — it also marks the underlying estimate revision submitted, freezing the claim of what you offered.
  3. Move the pursuit to Bid Submitted on the pipeline board — the stage is a separate, deliberate act, so the board says what you've actually done.
  4. From there the proposal ends Accepted, Expired, or Withdrawn — keep it honest; the outcomes feed your bid analysis.

Common mistakes

  • Pricing in the proposal instead of the estimate. The proposal shows the estimate; it doesn't override it. If the number needs to change, revise the estimate — the proposal follows.
  • Leaving it Draft after the bid went out. Then the pipeline says you never bid, your estimate never froze, and next month's funnel is fiction.
  • Skipping the expiry. An open-ended number is an option you gave away for free. Material prices move; date the offer.

See also

This is how STrOp works

The data flows you read about here are how the platform threads bid, execution, billing, and closeout. Single pipeline. No re-keying.

Request beta access →

Last updated 2026-08-20.