Skip to main content
Byteflare
Support

Review, edit and price a scope

The generated scope is a draft. This is the review pass that turns it into something you are willing to sign.

Who this is for: Anyone about to send a proposal to a client, and anyone reviewing a colleague's draft.

Review in this order

  1. Exclusions

    What you are not doing is the clause that prevents the argument in week six. The model is systematically more generous here than you would be.

  2. Client responsibilities

    Content, access, approvals, third-party accounts. Every dependency you do not list becomes your delay.

  3. Pricing line items

    Check each amount against your own rate card. The total shown on the proposal is the sum of the line items.

  4. Payment milestones

    Make sure the milestone amounts reconcile with the pricing table and that the first payment lands before substantial work starts.

  5. Assumptions

    Anything the model guessed should be written down as an assumption or removed.

  6. Optional add-ons

    Delete anything you are not willing to sell. Once it is in the document it is an offer.

Versions

A project holds one current scope. Regenerating replaces it. If you need to keep a particular version, there are two durable options:

  • Save it as a template (Team plan). The scope is copied into the template library and is unaffected by later edits to the project. See Templates.
  • Create a public link (paid plans). A share link freezes a snapshot of the proposal exactly as it looks at that moment. Editing the project afterwards does not change what the client sees. See Public links.

Where the dashboard total comes from

The Total Value figure on the dashboard is the sum of every pricing line item across all projects in the current workspace with a status of scoped or complete. It is a pipeline indicator, not revenue, and it does not know whether a client accepted.

Related