Skip to content

Use case · SOW generation

Draft the SOW
from the calls that agreed it

Scope from the proposal, service levels from the call that agreed them, ramp from the delivery review. Every clause carries the source it came from, and anything nobody confirmed is flagged before legal sees it.

  • Eight sections, drafted
  • A source marker on every clause
  • Open questions with owners

Documents

Sample data

Open

AnyCRM. Documents.

The ask

Caldwick Group sits at Negotiation with a verbal agreement from Tobias Lenz on 18 June. The delivery lead asks in plain English: draft the SOW from what we agreed.

Gathering

Scope from the accepted proposal of 2 June, volumes and channels from discovery notes of 14 May, service levels from the call of 28 May, ramp and staffing from the delivery review of 6 June, governance from the proposal, named stakeholders from the buying committee.

Draft

Eight sections: scope of services, volumes and channels, service levels, staffing and ramp, governance, commercial terms, term and termination, assumptions. Every clause carries its source marker.

Open questions

Data residency for recordings and holiday coverage over the year end were never settled. Both become open questions with owners and suggested language.

Risk

A service level the buyer asked for on 28 May is in the draft, and nobody in delivery ever agreed to it. The clause is flagged with the quoted line and its date.

Your call

Three moves: send to the delivery lead to confirm, propose alternative language, or run a War Room simulation of committing to it. The simulation says the peak hours fall outside what the ramp plan staffs for.

Resolved

The lead chooses the alternative language: a target through ramp, a commitment from phase two, reviewed monthly. The clause turns green because a human agreed to it.

Alongside

The order form is generated from the same commercial terms, and the MNDA is already signed on the account.

Send

A read-only link goes out for review. The activity is logged, and the stage moves on approval, not on opening.

Close

Every clause, back to the call that agreed it.

A statement of work drafted from the calls that agreed it. A coded simulation. Not connected to a live account.

Caldwick Group, where Tobias Lenz said yes on a call, and Elif Demir has to deliver what the document promises.

How it works

Four steps, and none of them is typing.

  1. 1

    Ask for it in plain English.

    Caldwick Group

    Sample
    • Draft the statement of work

      From the accepted proposal and the calls

      Asked

    Every clause will name the call, the note or the proposal that produced it.

    Draft the SOW from what we agreed. The assistant reads the deal, the accepted proposal, the notes and every dated call on the account.

  2. 2

    Every clause carries its source.

    SOW draft

    Sample
    • Scope of services

      Accepted proposal

      Sourced
    • Service levels

      28 May call

      Sourced
    • Data handling

      Nobody settled it

      Open

    Scope, volumes and channels, service levels, staffing and ramp, governance, commercial terms, term and termination, assumptions. Anything never discussed becomes an open question with suggested language and an owner, rather than an invented sentence.

  3. 3

    A clause your side never agreed.

    SOW draft

    Sample

    A service level the buyer asked for, and your side never confirmed.

    Unconfirmed clause

    A service level the buyer asked for that your delivery team never confirmed is flagged as a clause at risk, with the quoted line and its date. Send it for confirmation, propose alternative language, or simulate committing to it in the War Room and read the projected impact before anyone signs anything.

  4. 4

    Out for review, not signature.

    Documents

    Sample
    • The SOW draft

      Eight sections, a source marker on every clause

    • The order form

      Generated alongside

    Sent for review

    A read-only link shares the draft, the order form is generated alongside it, the MNDA on the account is checked, and the stage moves when you approve it.

The risk beat

When something turns, it tells you and shows you the moves.

Here the turn is: A service level the buyer asked for, and your side never confirmed. Three moves were offered and a person took one: propose alternative language.

Risk beat · AnyCRM AI

Sample data
  1. 1

    Detection

    A service level the buyer asked for, and your side never confirmed.

  2. 2

    Explanation

    Tobias Lenz asked for a twenty second answer time on the 28 May call. It is in the draft because she asked for it. Nobody in delivery has ever agreed to it.

    Unconfirmed clauseCaught before legal reads it
  3. 3

    Options

    • Send to the delivery lead to confirm
    • Propose alternative language
    • Run a War Room simulation of committing to it
  4. 4

    Human choice

    Propose alternative language

    A person presses one. Nothing is sent or written until then.

  5. 5

    Resolution

    Service level clause, agreed on both sides.

    The wording is in the draft, the simulation that produced it is on the deal, and the clause cites the call it came from.

    Every clause sourcedNo open questions on the critical path

Where the answers come from

The record you already have.

A statement of work is a record of what was agreed. Everything in it was said somewhere: on a call, in the proposal, in the delivery review.

The accepted proposal

Scope and commercial terms you already put in writing

Discovery notes

Volumes, channels and the shape of the work

Meeting transcripts

Service levels, quoted with the date they were asked for

The output

The SOW draft

Every line points back at one of these.

The delivery review

Ramp, staffing and what the plan actually supports

The buying committee

Named stakeholders and who governs what

Files on the account

The signed MNDA and anything already agreed

What you receive

Documents, not a dashboard.

Legal gets a draft where every clause names what produced it, and delivery gets the list of things nobody ever settled.

See the full CS Teams page
  • The SOW draft

    PDF

    The SOW draft

    Eight sections, every clause marked with its source

  • The order form

    PDF

    The order form

    Generated from the same commercial terms

  • Open questions

    PDF

    Open questions

    What nobody settled, with suggested wording and an owner

  • Read-only. Revoke any time.
    Link

    A read-only link

    For review and comment before anything is signed

Why BPOs need this

What we heard, in their words.

  • The problem

    We commit to service levels in a call and find out at signature.

    A head of delivery

  • The problem

    Half the SOW is copied from the last one and nobody remembers why.

    A customer success lead

  • The problem

    Legal asks where a clause came from and the answer is somebody's memory.

    An account director

Questions

The honest answers.

Does it write clauses we never discussed?

No. What was never discussed is raised as an open question with suggested language and an owner. Nothing is invented to fill a gap.

How does it know what we agreed?

From the accepted proposal, discovery notes, the delivery review and dated meeting transcripts. Each clause carries the source it was drawn from.

What if a service level was asked for but never confirmed?

The clause is flagged as at risk with the quoted line and its date, and you are offered the moves: send it to the delivery lead, propose alternative language, or run a War Room simulation of committing to it.

Does the deal stage move on its own?

No. The link can be opened and commented on all week. The stage moves when you approve it.

Give your team the unfair advantage.

Full deal intelligence from day one. No credit card required.

Get started free

AnyCRM, end to end