Check your next request against the agreement.
Upload one agreement and paste the last request that made you wince. See what it says in a few minutes.
No card needed · Cancel any time · A$ pricing
Product
The agreement, on hand for every request.
Agreeably keeps the signed scope and every approved change in one place, checks each new
client request against them, and keeps a record of what you decided and why.
Projects
Dispatch Portal Rebuild Baseline v1
- Scope
- Baseline v1
- Needs you
- 1 request
- Waiting on client
- 1 request
- Approved changes
- AUD 38,500.00
- Absorbed
- AUD 1,200.00
Request #3 Awaiting decision
Client request
Hello team, on the tracking page could customers see the arrival window the TMS already calculates? And could we text them when a consignment is out for delivery?
Requested changes · 0 of 2 decided
- Show the TMS arrival window on the tracking page. Included
- Send an SMS when a consignment is out for delivery. Potentially additional
Item 2 of 2
Send an SMS when a consignment is out for delivery.
Potentially additional Agreement v1 · 1.1 · p. 1 Deliverable
The Supplier will rebuild the customer dispatch portal as a responsive web application covering booking, tracking and proof-of-delivery screens.
Quotation matched to source text
The portal covers booking, tracking and proof-of-delivery screens; outbound SMS notifications are not mentioned.
Your decision on item 2
Labels are the AI’s reading of the confirmed scope. Check the agreement wording before you decide.
Inbox Check a request N
-
Dispatch Portal Rebuild · Harbour Freight Co
#4 Fwd: one more thing
Checking -
Dispatch Portal Rebuild · Harbour Freight Co
#3 Could customers see the arrival window?
1 included 1 additional Needs a decision
Reports Download CSV
Last month · 1 Oct 2026 to 31 Oct 2026
- Approved
- AUD 38,500.00
- 1 change request
- Sent
- AUD 38,500.00
- 1 change request
- Absorbed (estimated)
- AUD 1,200.00
- 1 absorbed item
Values are agreed amounts, not invoiced or collected.
- Charge 1 25%
- Absorb 1 25%
- Clarify 1 25%
- Decline 1 25%
Three labels, no scores
Every requested change gets one of three answers.
No confidence percentages. A number would suggest a precision the evidence doesn’t have. What you get instead is the label, the words behind it and what is missing.
Included
The confirmed scope, or an approved amendment, covers the request. The clause that covers it is quoted.
Potentially additional
The request goes beyond a deliverable, hits an exclusion or exceeds a limit. The boundary it crosses is quoted.
Unclear
The agreement is silent, vague or contradicts itself, or an exhibit is missing. The gap is named instead of guessed at.
In detail
Everything between “can you also…” and “approved”.
- Agreement intake
Every version of the agreement, kept.
Upload a text-based PDF up to 100 pages or paste the text. Each page stays linked to its extracted text. Replacing the agreement adds a version; the earlier one stays readable. Scanned, encrypted or empty files are refused clearly instead of half-read.
- Scope baseline
Five kinds of scope item.
Deliverables, exclusions, limits, dependencies and change procedures, each with its quotation and page. Add your own interpretations, labelled as yours.
- Request capture
Paste it or forward it.
Paste a request with context notes, or forward the email to the project’s private address. Quoted thread history is kept as context, not treated as new requests.
- Evidence-based assessment
One request, split into the changes it actually asks for.
A single email often asks for three things. Each requested change gets its own label, quotations, explanation, missing context and suggested next step. Every analysis records the baseline version and model configuration it used. Re-running it creates a new version instead of overwriting the last.
- Change requests
Drafts you price yourself.
Scope, assumptions, exclusions, effort, price, currency, tax treatment and schedule impact. The model may suggest wording. The price and dates come from you. Exported as a clean PDF.
- Amendments
Approved means recorded.
Client approval needs a date, an approving contact and evidence. Scope only changes when the lead confirms the amendment. Pending and rejected changes never widen it.
- Inbox
Nothing waits silently.
Requests that need you, are waiting on the client or are done, across every project you can see. It tells “no requests yet” apart from “intake failing”.
- Roles
Owners, delivery leads and, on Team, viewers.
Owners run the workspace, members and billing. Delivery leads confirm scope, assess and decide. On Team, viewers follow assigned projects without changing them, and members only see the projects they are assigned to.
Client approval portal · Business and Team
Let the client read and approve the change request.
Share a sent change request at client.agreeably.io. The client reads it, asks a question, or approves or rejects it. Your scope stays the same until you confirm the amendment.
- Once a change request is sent, an owner or delivery lead can share it at client.agreeably.io through a link with a random code.
- You choose who can open it (anyone with the link, one email domain, or listed email addresses), whether visitors confirm their email with a 6-digit code, the approving contact, and how many days it stays open, from 1 to 30.
- Every visitor enters a name and email. You see who opened it and whether their email was verified, and you get an email when it is opened, at most once per visitor per day.
- The client sees the change request as a client document with your branding: deliverables, exclusions, assumptions, price and schedule impact. They can download the PDF. They never see internal notes, AI analysis, decisions or agreement text.
- Only the named approving contact can approve or reject, after confirming their email with a code. A rejection needs a reason. Any visitor can ask a question, and you are emailed when they respond or ask.
- An approval is recorded as approval evidence: name, verified email and time. It is not an electronic signature or a contract, and it does not change the agreed scope. The delivery lead still confirms the amendment.
- No payments are taken in the portal.
Boundaries
What Agreeably won’t do.
A scope tool should respect scope. These limits are part of the design, not a roadmap gap.
- Email your client, unless you share a change request in the portal
- Invent a price, a delivery date or an approval
- Treat its assessment as a ruling on the contract
- Change your scope because an email said so
- Act on instructions hidden in a document or email
- Act as an e-signature or identity-verification service