Commercial change control for client work

Keep client changes from quietly changing the deal.

SentientScope watches the systems where client work happens, checks consequential requests against the current agreement, and routes commercial changes through evidence, human decisions and client authorization before they become delivery reality.

Start free trial →See how it works
  • 14-day free trial
  • Nothing charged until the trial ends
  • Cancel anytime
The SentientScope Overview: three items needing attention — a request that conflicts with the agreed scope, a change to review, and an approved change awaiting its contract update — above the commercial position in dollars and the active projects with their Living Scope revision.
The real product on a sample workspace: what needs attention, the evidence behind it, and the commercial position. Every name and number is fictional.

The control gap

The agreement lives in one place. The changes happen everywhere else.

Most firms already have software for what was sold, what was signed, what the team is doing and what gets billed. None of it owns the moment a client changes something after kickoff.

What was soldCRM
What was signedSOW · agreement
What the team is doingEmail · Jira · ClickUp · calendars
What gets billedPSA · finance
The gapWhat happens when the client changes something after kickoff?The SOW rarely catches up. The delivery systems never ask.

Then a client writes:

  • “Can you add this too?”
  • “Can we move the date?”
  • “Can your team handle this one as well?”
  • “Can we include one more region?”

The request may sound small. The commercial commitment may not be.

Someone says yes in an inbox, a ticket changes the requirement, a date moves, and delivery keeps going. SentientScope closes that gap: the current agreement stays the reference, and every consequential change takes one controlled path through it.

How it works

One controlled path from a client request to a revised agreement.

Comparing a request with a contract is the easy part. The work is what happens next. SentientScope carries the change through all seven stages, so the deal changes only on purpose.

  1. Establish what is agreed

    The verified SOW or agreement becomes a Living Scope: each commitment with the clause it came from, confirmed by a person before anything is monitored against it.

  2. Observe what changes

    Connected mailboxes, delivery tools and CRM records surface relevant client and delivery activity as it happens. Or check a request by hand.

  3. Compare it to current authority

    A potential commercial change is tied to the agreement language it touches — the excerpt and section, not a summary of one.

  4. A person decides

    Confirm it is in scope, absorb it intentionally, ask for clarification, dismiss it, or raise a paid change with its price and schedule effect.

  5. Obtain authorization

    When the client must agree, they do so through a secure review link that shows the change, its cost and its schedule impact.

  6. Update authority deliberately

    Approved does not silently become Living Scope. The contract update your agreement requires is completed first, then recorded.

  7. Preserve the history

    What changed, why, who approved it, what it meant commercially and which revision it produced stay on the project record.

Living Scope

One current answer to “what did we actually agree to?”

SentientScope keeps the verified commitments your team is authorized to deliver against — deliverables, dates, responsibilities, limits, exclusions and commercial terms — as one revisioned record, without becoming another document repository.

Verified once
Extraction proposes. A person confirms every commitment against the exact agreement language before it becomes the baseline.
Revisioned
Every approved and recorded change produces a new revision. The one in force is always explicit, and earlier revisions stay in history.
Cited
Each commitment keeps its excerpt and section, so a later decision can show the line it stands on.
The Living Scope tab of a project: twelve verified commitments grouped as deliverables, dates, client responsibilities, limits, exclusions, approval gates and commercial references, each with its key.
The Living Scope of a sample project: the commitments in force, grouped by kind, each verified against the agreement.

Evidence and decision

See the request beside the agreement.

Evidence first. SentientScope shows what the client asked for, what the current agreement says, and what the difference appears to be. Your team decides what it means commercially.

A decision in SentientScope: the client's email asking for a CRM migration beside the active scope item that excludes it, citing SOW section 6; the analysis; and five ways to handle it — create paid change, confirm in scope, absorb intentionally, need clarification, dismiss.
A decision on a sample project: the client's request, the agreement language beside it, and the five ways a person can handle it.
  1. Client requestWhat was asked, from whom, and where.
  2. Active scopeThe commitment it touches, with the clause.
  3. AnalysisWhat the difference appears to be.
  4. Your decisionIn scope, absorb, clarify, dismiss, or paid change.

AI helps extract, compare and summarize. People remain responsible for commercial decisions — and where the answer is a paid change, its price and schedule impact travel with it to the client.

The client's secure review page: the proposed change, its added cost and schedule impact, and the Approve proposed change, Request changes and Decline actions, with a note that approving records acknowledgment and the contract is updated separately.
What the client sees: a secure review link with the proposed change, its cost and schedule effect.

Client authorization

Turn a decision into a clear client choice.

Send the proposed change with its price and schedule impact through a secure review link. The client can approve, request changes or decline — no SentientScope account needed. Nothing is signed for them.

  • The client sees the change, the added cost and the schedule impact in plain language.
  • Their response is recorded on the change with who answered and when.
  • Approval records acknowledgment. The contract is updated separately, through whatever change process your agreement requires.

The gate

Approved doesn’t automatically mean authoritative.

A client can approve a proposed change. SentientScope still keeps that approved change separate from the current Living Scope until the contract update your agreement requires has actually been completed — and someone on your team records it.

The gate on a change record: the current authoritative state — baseline revision 2 with the excluded CRM migration and its clause — beside the approved change with its commercial and schedule impact; below, what recording the update will do, and the form for the completion date, reference and confirmation.
The gate on a sample change: the current authoritative state, the approved change, what recording the update will do, and the confirmation a person must give.
Approved change
What the client agreed to, with its commercial and schedule effect and the client's own words.
Current authoritative Living Scope
What your team is authorized to deliver right now — the revision in force, and the commitments it contains.
The record
Who confirmed the contract update, when it was completed, the reference it carries, and the revision it activated.

Existing systems

Keep the tools your team already uses.

SentientScope is not trying to replace your CRM, project-management system or inbox. It connects the systems where commitments emerge and gives commercial changes one controlled path.

Communication

  • Microsoft 365Mail · Calendar
  • Google WorkspaceCalendar · Mail not available yet

Delivery

  • ClickUpContract-update tasks
  • JiraProject activity

CRM

  • HubSpotDeal changes
  • SalesforceOpportunity changes

Automation

  • API & WebhooksScale plan

Commercial history

Know what changed commercially — not just what got delivered.

Reconstruct why a commitment changed: the evidence, the decision, the client's approval, the contract update and the revision it produced — and what it meant in dollars. One commercial history of the project, kept as organizational memory.

  • Evidence
  • Decisions
  • Approvals
  • Contract updates
  • Revisions
  • Commercial impact
The Reports page: requests reviewed, paid changes raised, absorbed intentionally and approved additional work for the period, a monthly chart of approved additional work, how requests were resolved, and each project's position.
Reports on a sample workspace: what was reviewed, approved as additional work, or absorbed intentionally — by month and by project.

Security and data handling

Your agreement stays your agreement.

SentientScope is not trying to become another inbox or document archive. It keeps the project state, evidence and commercial history it needs to control changes, and discards transient source content on its retention schedule.

Uploads are transientYour agreement is processed to build the verified scope, then the uploaded copy is deleted on the documented lifecycle. The commitments and the excerpts that explain them stay.
Least-access mailbox monitoringEach person connects their own Microsoft 365 mailbox with delegated, read-only consent. Ordinary mail is discarded after evaluation; attachments are never fetched.
Workspace isolationEvery workspace is isolated at the database layer with row-level security, and every consequential action is authorized server-side against the caller's role.
People decideAI assists extraction and comparison. It never becomes authoritative project state: pricing, approvals and contract updates require a signed-in person.
Append-only historyDecisions, approvals, reassignments, contract-update confirmations and baseline activations are written to an audit history that shows who did what, when.
No certifications claimedSentientScope does not currently hold SOC 2 or ISO certification, and its security page says so. What it describes are engineering boundaries tested on every change.

How SentientScope handles your information →

Who it is for

Built for teams that deliver against an agreement.

Implementation partners, professional-services teams, ERP and CRM implementers, custom software consultancies and other project-based client-service organizations — run by heads of delivery, professional-services leaders, PMO leads, managing partners and founder-operators.

A good fit when

  • There is a real SOW or agreement, and requirements evolve during delivery.
  • Several people on your team talk to the client, and any of them can say yes.
  • Changes affect scope, cost or timeline, and someone has to authorize them.
  • Project state and commercial state can drift apart without anyone noticing.

Probably not needed when

  • One-off tasks with no meaningful agreement behind them.
  • Engagements where every request is included by design.
  • Purely hourly or usage-based work with no boundary to hold.
  • Teams that only need task management.

Pricing

Three sizes of the same product.

Every plan includes the complete change-control workflow and the standard integrations. Plans differ by capacity — how many team members are monitored and how many client projects are active — and the Scale plan adds the API and webhooks.

Starter

A small delivery team with a handful of live client projects.

$59/ month

or $590/year (two months free)

  • 3 monitored team members
  • 5 active client projects
  • Core SentientScope — the complete workflow
  • Standard integrations: Microsoft 365, Google Calendar, ClickUp, Jira, HubSpot, Salesforce
Start free trial

Team

Most teams

A delivery group running client work across several engagement leads.

$99/ month

or $990/year (two months free)

  • 8 monitored team members
  • 15 active client projects
  • Core SentientScope — the complete workflow
  • Standard integrations: Microsoft 365, Google Calendar, ClickUp, Jira, HubSpot, Salesforce
Start free trial

Scale

A services organization with many concurrent engagements and leads.

$149/ month

or $1,490/year (two months free)

  • 15 monitored team members
  • 30 active client projects
  • Core SentientScope — the complete workflow
  • Standard integrations: Microsoft 365, Google Calendar, ClickUp, Jira, HubSpot, Salesforce
  • API & webhooks
Start free trial

14-day free trial on every plan. What counts toward capacity, and how your agreement is handled →

FAQ

Fair questions.

Is SentientScope a project-management tool?

No. It sits alongside the systems your team already uses — mailboxes, delivery tools and your CRM — and controls commercial changes against the current agreement. Delivery keeps running where it runs today.

Does AI make the final scope decision?

No. AI helps extract commitments from the agreement, compare a request against them and summarize what it finds. A person on your team makes every consequential commercial decision, and each one is recorded with who made it.

What happens to the document I upload?

It is processed inside your authenticated workspace to build the Living Scope, and the uploaded copy is then deleted on the documented lifecycle. SentientScope keeps the verified commitments and the exact excerpts that explain each decision — not your document.

Do clients need a SentientScope account?

No. A proposed change reaches the client through a secure review link, where they can approve, request changes or decline. Nothing is signed for them, and approving records their acknowledgment rather than amending the contract.

Do I need to CC SentientScope on client emails?

Not with a connected mailbox. Each team member connects their own Microsoft 365 mailbox with read-only access, and new client mail is checked against active projects as it arrives. Teams that prefer not to connect a mailbox can forward or CC mail to a per-project address instead.

What happens after the client approves a change?

The approval is recorded, but the Living Scope does not move yet. SentientScope keeps the approved change apart from the current authoritative scope until someone on your team confirms that the contract update your agreement requires was completed, and records the date and reference. Only then is a new revision activated.

What happens if the agreement is ambiguous?

SentientScope says so. "Not clearly covered" is a first-class answer, shown with the closest relevant language, because forcing every situation into yes or no would be dishonest about how agreements actually read.

Which systems are supported?

Microsoft 365 (mail and calendar), Google Workspace (calendar), ClickUp, Jira, HubSpot, Salesforce today. Mailbox monitoring for Google Workspace is not yet available. Custom systems connect through the API and signed webhooks on the Scale plan.

Keep the deal and the delivery in step.

Start free trial →See pricing
  • 14-day free trial
  • Every plan includes the complete workflow