Proposal

When terms were settled in conversation and nowhere else, what got agreed to lived differently in each person's memory. Say the sentence "we'll help with the initial setup" came up in a meeting. The seller meant creating accounts and configuring permissions. The buyer heard migrating every existing file across. Both of them left the room believing they had discussed the same thing.

The bill arrived after the contract. In the first week of rollout an email asks when the data migration is scheduled, and the seller replies that migration is separate paid work. From there, there is no way to establish who was right. No transcript exists, and the sentence isn't in any email either. The first month of the relationship gets spent draining trust instead of building it.

A proposal exists to pin those sentences to a single document, which is why the stage sits in the pipeline at all. Move what was spoken into writing and the room for remembering it differently shrinks, and the places where the two sides diverge surface before signature rather than after. When a prospect reads the proposal and asks whether something is really excluded, that isn't a problem — it's the stage doing its job.

The protagonist here is a document, not a person. Everything up through the demo ran on meetings and conversation; from here on, a file you sent gets read without you in the room.

Four things usually go inside it.

1. Scope — what you'll do and how far. Don't only list what's included; list what isn't. If data migration and internal training are being held out as separate work, that sentence belongs in the document.
2. Price — per-seat rate, seat count, and annual total together. If a discount is in there, put the list price and the applied price side by side and add a line about why it came down. A reduction with no stated reason becomes the baseline at renewal.
3. Term — start date, end date, and whether it auto-renews. If onboarding takes two weeks, say when billing starts relative to that.
4. Payment terms — annual prepayment or quarterly invoicing, and how many days after invoice payment is due. A finance team on the customer side will sometimes decide on approval from this line alone.

The register differs from earlier stages. In a demo you could narrate alongside the screen; a proposal has to stand on its own, because its readers are the approver, the finance contact, and the legal reviewer who were all absent from the meeting. So it avoids abbreviations and internal shorthand, and any sentence that could be read two ways gets split into two.

Longer is not better. A thirty-page proposal doesn't get read, and terms written in a document nobody read were never agreed to. Pagedeck's team-level contracts fit in four pages, and what grows in an enterprise deal isn't the explanation — it's the security and legal sections.

Sending the proposal doesn't move anything. Negotiation, the next stage, is open once three things are true.

1. The prospect has actually read it and responded item by item. "Received, thanks" is not evidence of reading. A question that points at the scope or the term is.
2. There's a list of things to change. A request to switch to quarterly billing, or to fold training in, is where working the terms actually begins.
3. The approval path and a target date exist. Who signs, which departments it passes through first, and by when they want it done.

Sending it and then waiting is the most common mistake in this stage. Handing over a document feels like handing over the next move, but an unread document does nothing at all. Booking a session to read it together within two days of sending beats waiting for a reply by a wide margin, and it also surfaces objections while you're still in the room to answer them rather than a week later over email.

Enterprise deals add one more document here: a statement of work (SOW), which states what will be delivered and how far in a form that carries legal weight. When the scope section of the proposal is vague, drafting that document alone eats weeks.

"Before this proposal goes out, look at the exclusions list once more. That's the line we end up arguing about."

Writing down what isn't included matters as much as writing down what is.

"The proposal goes out Tuesday and we're reading it together on Thursday."

A plan not to throw the document over the wall and wait.

"This isn't at proposal — it's still at demo. The technical questions aren't closed."

Walking a deal back to the stage it's actually in.

At Pagedeck, Sofia works from one proposal template and changes three places per deal: scope, seats and price, and term. The template is fixed less to save writing time than to stop things going missing, and the three variable places are the only ones anyone is allowed to touch. Rewritten from scratch each time, a line like payment terms quietly disappears.

Above a certain deal size, Grace reads the document once. What Grace looks at isn't the explanation but the scope, the term, and the termination clause. Last quarter a proposal nearly went out with the auto-renewal clause missing. Without that line the contract simply stops after a year, and the customer has to push a fresh approval through their own organization to continue.

A frequent belief is that a longer, more carefully produced proposal is more persuasive. Effort reads as good faith, and most people can remember a competitive bid where the thicker document won. But the person opening this file is doing it to decide whether to approve. Ten pages of company background and industry trends in front means they scroll looking for the number, don't find it, and close the file. The price and the scope then sit unagreed while the deal stalls another week.

The other mistake is treating the proposal as a persuasion document. Persuading was the job in every earlier stage, so it looks like the natural continuation. What this document actually does is confirm. The persuading needed to finish at the demo, and a proposal sent to someone not yet convinced leaves them with nothing to reply to, so they go quiet instead of answering. Read that silence as internal review and you lose two weeks to it — including the closing date you told your own team to expect.