Keep client work aligned with what was agreed.
Worql connects your signed statement of work (SoW), client requests and delivery evidence. Resolve changes before they become unpriced work, and prepare acceptance with less time spent reconstructing decisions.
Try an example engagement. No account required.
30 minutes to review your scope, changes or next milestone.
Northstar Labs × Keelstone Logistics · Carrier Operations PortalExample engagement
Driver certification filtering requested
Worql checked Slack, Jira and meeting transcripts for this engagement and found no approval.
The value of staying aligned
More time for delivery.
More control over the cost.
Keep changes, decisions and acceptance connected, so your team can move work forward with less chasing.
Less time coordinating.
Bring requests, work and agreement context together for the next decision. Spend less time reconstructing what happened.
Fewer accidental commitments.
Compare changes with the agreed scope. Resolve added effort and conflicting requirements before they turn into unpaid work or rework.
An easier acceptance review.
Bring delivery evidence and agreed criteria into one review, with the decision left to the authorized person.
Time recovered gives the team capacity. Cash savings depend on reducing an expense or avoiding an additional hire.
See how a change becomes a decisionIllustrative fixed-price example
One request. Different economics.
A client requests extra work. Worql connects the request to the agreed scope so the team can decide before committing more cost.
- Original fee
- USD 250,000
- Planned direct cost
- USD 175,000
- Added direct cost
- USD 20,000
Changes this example only. No approval is recorded.
Project gross profit
USD 55,000
USD 20,000 below the original plan
Original plan: USD 75,000 gross profit
- Project fee
- USD 250,000
- Direct delivery cost
- USD 195,000
Assumes the supplier delivers the added work at the original fee and incurs the full added cost.
Client impact: The original fee covers both the original scope and the added work.
Hypothetical figures, before overhead and Worql fees. Gross profit is the fee less direct delivery cost. Outcomes depend on what both sides agree and what delivery costs.
For the services firm Understand the effort and commercial decision before committing the team.
For the client Understand what the change costs, what it includes and which alternatives are available.
See the boundaries for both sidesSmall requests can turn into unapproved work.
A client asks for a new filter in Slack. An engineer starts building it, but the signed SoW excludes it. The request never becomes a formal change.
The cost starts accumulating before the milestone review. Worql brings the request, work and agreement together so the team can clarify what is included, propose a paid change or deliberately absorb the extra work. The client can see what is being proposed before deciding.
Example engagement. Northstar Labs and Keelstone Logistics are made up.
#keelstone-carrier-portal · SlackJul 16, 9:14 AM ET
observed · a request and an informal yes
KEEL-327 · JiraIn progress · Marcus Reid
Certification filter on driver assignment list
Linked PR #471 · 2 commits · Jul 17
observed · delivery has moved
SoW v2 · §5.2 ExclusionsExecuted Jul 2 · Amendment 1
“Certification-based filtering of driver records is excluded from this Statement of Work and may be added by written amendment.”
governing · the version both parties signed
See how a request connects to the agreement.
Follow the signed scope, client request, delivery work, approval status and current version. Select a point to inspect the evidence and any gaps. Expand the record for more detail.
No approval found
Worql checked Slack, Jira and meeting transcripts for this engagement and found no approval.
No matching approval in the connected sources.
Proof that no approval happened anywhere.
Ask someone who can sign to decide how to treat it.
Worql connects the evidence. Authorized people decide what changes.
Work through this decision in the demoFrom scope change to client decision.
Follow the example through five steps. Rohan reviews the scope mismatch and proposes a change. Sofia reviews and approves it, then accepts Milestone 4 against six criteria. Finance receives the acceptance record and supporting history.
Driver certification filtering requested
Daniel Okafor asked in #keelstone-carrier-portal on Jul 16. Ravi Menon replied “Yes, we can do that.” KEEL-327 is in progress with PR #471 linked. SoW v2 §5.2 excludes certification-based driver filtering.
- Looked in
- Agreement, Slack (1 channel), Jira, meetings
- Found
- No approval by anyone with sign-off
- Not connected
- Decides
- Rohan Deshmukh, then Sofia Marquez
- SLACKDaniel Okafor: “Can we filter available drivers by active certification…”Jul 16
- JIRAKEEL-327 In progress · Marcus Reid · PR #471Jul 17
- SoW v2§5.2 Exclusions · certification-based filtering excludedJul 2
There’s more than one correct decision.
Control level · GovernUSD 4,800 is 11.29% of the USD 42,500 agreement, above the 5.00% threshold in the default policy, so a formal change decided by someone with authority is required. The level is set by deterministic rules, not by a model.
Rohan decides the treatment. Sofia decides the amendment. Neither is automatic.
What Worql does.
One shared record from the signed agreement to finance, with every change, decision and handoff in it.
Agreement and control
Contractual commitments translated into actionable workflows
Your signed SoW becomes the scope, milestones and acceptance criteria both teams work against.
Change orders, approvals, and bilateral signatures
A change is approved by someone with authority and signed by both sides before it alters the agreement.
Adaptive Commercial Control
Rules set how much review each action gets, from its value, its share of the contract and its terms.
Shared, versioned, verifiable commercial records
Both sides read one tamper-evident record. Signed versions are never edited in place.
Delivery and acceptance
Delivery coordination against contractual requirements
Work in GitHub, Jira and Slack is checked against the signed acceptance criteria.
Evidence assembly and acceptance preparation
Evidence is gathered per milestone, ready for the client’s acceptance decision.
Financial and contractual obligation management
Obligations, rates and caps are tracked against the agreement.
Operational and financial handoffs
An accepted milestone reaches finance with its decision and full history.
Intelligence and automation
Continuous source-driven commercial intelligence
Worql reads your connected tools and meetings against the agreement and raises what changed.
Autonomous coordination across enterprise systems
The next step moves across your delivery, finance and client systems without manual chasing.
Dependency orchestration and multistep execution
Multistep work runs in order, with every dependency tracked.
Automated cross-system handoffs
Work passes between tools on its own, and the record keeps up.
One shared record, with clear boundaries.
Every acceptance, decision and proposal records the party who made it and when. Signed versions stay unchanged; an amendment creates a new version. Each side’s internal notes, pricing and negotiating position stay private.
Northstar only
- Estimate basis and internal notes
- Internal review before anything goes to the client
- Internal notes on options not proposed
- Open items like RV-031, with the coverage behind each
Your delivery lead sees every open ask on the engagement, which have a decision, and which are still waiting on someone.
The shared record · both sides read the same thing
- SoW v1, v2, v3 and the amendments between them
- Amendment 2 as proposed, with the source it was raised from
- The approval of Amendment 2, with names and times
- Milestone 4 criteria, evidence, questions and acceptance
- The acceptance record finance reviews from
Your finance team sees each accepted milestone with the amount, who accepted it, and the criteria it was accepted against.
Keelstone only
- Sofia’s notes on a milestone before deciding
- Keelstone’s own questions on a criterion
- Keelstone’s internal sign-off gates: business, security, finance, legal
Your client’s approver sees what’s waiting on them: they can approve or decline a change, or respond without deciding, and accept a milestone, send it back, or ask a question. They sign in with an account but don’t need a subscription of their own.
Know which agreement applied at every step.
In this example, Amendment 2 created SoW v3 while preserving v2. Both sides can open the version that applied on a given date. Finance can see which version was used for each milestone’s acceptance.
Scope doesn’t drift. Memory does.
| SoW v2Executed Jul 2 · Amendment 1 | SoW v3 · GOVERNSExecuted Jul 28 · Amendment 2 |
|---|---|
| §2 PRICEFixed price USD 42,500 | §2 PRICEFixed price USD 47,300 (+USD 4,800) |
| §5.2 EXCLUSIONSCertification-based filtering of driver records is excluded and may be added by written amendment. | §5.2 UNCHANGED · §5.2a ADDEDCertification-based filtering of driver records is in scope as specified in Amendment 2. |
| M4 · CRITERION 3Webhook retry SLA met. | M4 · CRITERION 3Webhook retry SLA met, measured per batch. |
Nothing was edited in place. v1 (May 28) is also in the record.
Your firm runs it. Your client signs in only to decide.
- Does our client have to sign up or use Worql?
- No. Your firm runs Worql. Every Monday, Worql emails the client contacts you name a PDF digest of the engagement: what is signed, what changed and what is waiting on them. They need no account to receive it. They sign in only to take part: to sign the agreement, accept a milestone or decide a change.
- Does the client pay for anything?
- No. The subscription belongs to your firm. A client who signs in to sign, accept or decide needs no subscription of their own.
- What can the client see?
- The shared record: the agreement, change orders, milestones and the decisions on them. Your unsent proposals, internal notes and Worql’s suggestions stay on your side, in the app and in the digest.
- Can a client stop the weekly digest?
- Yes. Every digest has a link to stop it, and only the person who stopped it can turn it back on. Your firm can also take anyone off the list.
Find the value in your next engagement.
Explore the example, or review one of your scope changes, acceptance delays or recurring coordination tasks with us.
Try an example engagement. No account required.
30 minutes to review your scope, changes or next milestone.