Platforms/SalesOS

From first call to signed SOW, in one journey.

Your reps shouldn’t be copying transcripts between five tools to write a proposal. SalesOS is the one place a deal travels through: lead, meeting, summary, SOW, proposal.

Follow one deal →Other journeys
One journey
Lead
Meeting
Transcript
Summary
SOW
Proposal
01 / One rep, one leadFlip the switch

Same deal. Two very different weeks.

A lead comes in on Monday. Here is everything that happens before the client sees a proposal, first the way most teams do it today, then inside SalesOS.

6Tools touched
4Copy-pastes
1Bots in the call
01

A lead arrives

An email, a WhatsApp message or a form fill. The rep notices it eventually and logs it in the CRM by hand.

OutlookWhatsAppCRM
You
Re-type lead into CRM
02

Set the meeting manually

Back-and-forth emails to find a slot, then build the Teams invite yourself.

OutlookTeams
You
Copy invite details
03

A bot joins the call

A third-party note-taker joins the client meeting. The client asks who it is.

Note-taker bot
Third-party bot
Download transcript
04

Summarise with another tool

Paste the transcript into a chatbot and prompt it until the summary looks right.

Chatbot
You
Copy summary
05

Draft the SOW somewhere else

Open last quarter's SOW, save a copy and overwrite it section by section from the summary.

WordSharePoint
You
Copy SOW sections
06

Build the proposal in yet another tool

Rebuild the same content as a proposal deck. Update the CRM stage if you remember.

PowerPointCRM
You

Six tools, four copy-pastes and a stranger bot in the client call. The rep spent the week moving text around.

02 / The moment it clicksMeeting ends → SOW is waiting

Hang up the call. The SOW is already drafted.

Record on Teams like you always do. SalesOS pulls the transcript, writes the summary and fills your own SOW template. Every line links back to the moment in the call it came from.

Teams · Discovery call42:18
Teams meeting
Recording in TeamsHD
ARAccount rep
SASolution architect
NLClient · Head of Ops
NLClient · IT lead
✓ No bots in this meeting
Summary● Auto · 38s after call
Client goals
  • Replace paper dispatch with a driver app 12:41
  • Live view of every delivery for ops 18:05
Constraints
  • Must sync with their existing Odoo 24:30
  • Pilot before peak season 31:12
Next steps
  • Proposal by Friday: account rep 40:02
  • Technical session with IT: solution architect 40:40
SOW draftTemplate · Fixed-price delivery
Statement of Work: Dispatch Modernisation
ScopeDriver mobile app, dispatch dashboard, Odoo integration 12:41
Out of scopeFleet telematics hardware
PhasingDiscovery → pilot → roll-out, pilot ahead of peak season 31:12
CommercialsFrom your rate card, pending review
Review & generate proposalEdit
03 / More journeys in SalesOSThe same idea across the whole funnel

One deal was just the start.

Every sales journey gets the same treatment: one place, no copy-paste, and agents doing the admin in the background.

Journey · CaptureEvery channel, one inboxLeads from email, WhatsApp, Teams and the website land in one queue, and each one gets a reply.
Journey · PrepareKnow the client before the callA research brief on the company, the people and the industry is ready before the meeting.
Journey · RouteThe right rep, first timeLeads are matched on expertise and workload, not on whoever saw the message first.
Journey · ManageA huddle that runs on factsThe morning stand-up reads what actually happened, not what reps remember.
Journey · ClosePOs you can actually findPurchase orders become searchable records, not attachments in a chat.
Journey · CollectInvoices that chase themselvesReconciled with your ERP. Reminders are drafted and escalated on schedule.

Let your reps sell. Let SalesOS do the rest.

We’ll map one of your real deals end to end and show you exactly where SalesOS removes the copy-paste.

Map a deal with us →Next: PeopleOS