Sales proposals

Click New proposal and choose the source opportunity (the items are inherited). Adjust items/values/discounts, Save and Send: the system generates a public link and a PDF for the client.

Sales proposals: build them from the opportunity, send them by link, and the customer's acceptance becomes a contract. Versionable, with discount approval authority and PDF. — this is the role of the "Proposals" screen within the platform.

Build the items (description, quantity, unit value, discount and the recurring flag), save and send. The badge at the top shows the stage — draft, awaiting approval, sent, accepted, declined, superseded or expired — and editing locks when the proposal is no longer editable. After sending, the public acceptance link and the PDF to download appear; if the proposal was sent or declined, "New version" creates the next revision without losing the previous one's history.

Ctrl+K opens the screen search from anywhere in the platform: type part of the name (catalog synonyms also count) and go straight there. For those who use this screen often, it's the shortest path.

The proposal opens in the standard form: title, validity and terms on the main tab, the 3-option mode and comparison on top, and the items on the Items tab — "Add item" and each row’s pencil open the dialog; everything is stored together on Save (Ctrl+S). Send, new version and signature sit in the header.

When the client accepts via the link (with date and IP recorded), the opportunity is won and the contract is created — inheriting the recurring value as MRR. A refusal records the reason.

Each revision is a new version (previous ones remain immutable). If the average discount exceeds the authority level, the proposal becomes Awaiting approval and is only sent after being approved.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

Access is governed by profile: whoever administers the account grants "view" (and the other verbs) on the Access screen. If someone on the team cannot find this screen in the menu, the path is to ask the administrator for the grant — absence from the menu is not a bug, it is permission.

With 3 options, the customer compares among YOUR alternatives instead of comparing you with the competitor — and most choose the middle one. A BASE item applies to all three; choosing an option makes the item exclusive to it, creating the step between the columns. The "Generate 3 options" button builds the structure on the spot: the current items become the base scope and each option gets a differentiator already priced by anchoring (Essential ~75%, Recommended = current total, Premium ~135%) — you edit everything before sending. The customer accepts ONE option, and the contract is born from its scope and value.

The "Price by value" button opens the calculation that looks outward: enter the annual gain the customer will have (savings or new revenue) and the share of that gain you capture — the suggested price comes out per year and per month. Example: a solution that saves R$ 120,000/year, capturing 15%, suggests R$ 18,000/year (R$ 1,500/month). Compare it with the total by item cost: if the value-based price is higher, the perceived value supports a better price (or a Premium option); if it's lower, review the scope or the argument.

With a provider configured in Settings → Electronic signature, the "Send for signature" button appears when the proposal is sent or accepted and doesn't yet have a document at the provider: it sends the PDF for the customer's digital signature. The signature status is updated automatically by webhook — you follow it through the badge next to the buttons — and, once completed, the signed document comes back attached, with a link to download the signed PDF straight from the screen.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

A sent, accepted, declined or expired proposal is read-only, and the notice at the top shows the way forward. Sent or declined: use New version — the current one stays in the history. Accepted: what was contracted changes through an amendment to the contract. Expired or superseded: create a new proposal. The accepted proposal that created a contract appears on the contract itself, and the one-time amount goes into the opportunity and the pipeline total.

When the client accepts, the contract is created at once with the accepted monthly amount (in a three-option proposal, that of the chosen option), points to this proposal and gets an obligation "Charge the one-time amount of …" with the payment terms, due 30 days from the start. The term follows the usual rule (one year). Whoever accepted through the link appears as a signer of the contract, with name, CPF or CNPJ and date. If the contract cannot be created, the acceptance is not recorded and the proposal stays sent.

Whoever has the permission to view this screen in their profile, with the module enabled in the plan. Creating and editing proposals are separate verbs, granted per profile — and the discount authority adds a control beyond the profile: a discount above the authority level goes for approval instead of going out directly. The amounts (total, recurring) obey the "View Amounts" permission. Acceptance itself happens outside here: the client decides via the public link carried by the sent proposal.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".

Use the "From request to proposal" panel: paste the conversation, the email or the audio transcript as it came and click "Structure with Tenkai". It creates the scope items (always with price set to ZERO — pricing is your decision), and writes in the notes the problem, the assumptions and "what is NOT included". Nothing you've already typed is changed: the assistant only adds, and you review everything before sending. The panel only appears when the company's AI is turned on.

"What's on the customer's table right now?" — when that question comes up, this is the screen that answers it.

Because it has already been sent, accepted, declined or has expired — the notice at the top says which way to go. Sent or declined: use New version, and the new one is editable again. Accepted: change what was contracted through an amendment to the contract. Expired: create a new proposal.