Deal Desk.
Keep great deals moving.

A deal review queue for sales and finance

Deal Desk is a starting point for account executives, sales operations and finance reviewers deciding what should happen next on a proposed deal. Its sample queue includes an annual renewal, a team expansion, a pilot requiring changes and an onboarding deal already approved. These are examples of commercial decisions to discuss with your team, rather than evidence of a customer using SpringRoll.

Each record has a deal title, owner, monetary deal value, review status and decision note. Open a row to inspect or edit those fields and see its activity entries. The summary counts separate items awaiting review, approved items and requests needing a change. Search matches the deal title or owner, while the status filter helps a reviewer focus on the next decision.

Walk a proposal through the decision

Create a new deal with a value and an explanation of the requested commercial arrangement. Save it for review, open it again and ask for a change with a clear decision note. Revise the entry, save it back to review and approve it after the missing information is supplied. The changing counts and activity list make that small review loop visible.

All people and records are fictional. The preview runs entirely in your browser, stores edits locally and simulates review. It does not send a contract, update a CRM or enforce separation between a salesperson and a finance reviewer. Use Reset example to return to the starting queue. For a production adaptation, add a shared record store and verify authorization on the server.

Connect the sales context deliberately

A real version could read approved opportunity fields from Salesforce and reference a reviewed pricing or account dataset. Decide which fields a deal reviewer needs before creating the application's data grant. An opportunity summary may be sufficient; unrestricted access to customer contacts, private contract attachments or the whole revenue warehouse is a different request.

Have sales name an App Owner and finance define who can approve the business decision. Keep that decision distinct from SpringRoll's deployment workflow: approving a release does not approve a discount. Test a salesperson, a reviewer and someone outside the intended audience. Record how onboarding learns that a deal is approved and who can correct it if the commercial terms change.

Three prompts for your Claude Code project

Use these as proposed adaptations of the included source. Review and test the changes before entering company records; the prompts describe work to build, not features already present in the starter.

1. Add a discount percentage and proposed contract term to the deal editor, validate both on the server, and show finance the exact values that require a decision.
2. Replace browser storage with a shared database and add separate submitter and finance-reviewer permissions. Test that a submitter cannot approve their own proposal.
3. Read only approved Salesforce opportunity fields through SpringRoll. Keep source credentials outside the client bundle and show a clear state when the grant is missing or revoked.

Take the next step

Start with a renewal your sales and finance reviewers can assess together, then make the handoff to onboarding explicit.

Start with Deal Desk

Download the source