Get early access
For software implementation consultancies

Know what was agreed
before you say yes.

Agreeably checks each new client request against your confirmed scope and approved changes, shows you the exact clause, and records whether you charge, absorb, clarify or decline.

Email us for early access See it check a request

No card · Business features for 14 days · Prices in AUD

Projects

Dispatch Portal Rebuild Baseline v1

Harbour Freight Co · Lead Priya · AUD

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 From Marcus Lee · forwarded email

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.

Every one of these arrives as “a quick one”

  • Can you also bring across three years of invoices?
  • Quick one: add a second sandbox for UAT?
  • Could the sync run every five minutes instead of nightly?
  • Can we get the pipeline report split by region?
  • Our finance team wants Xero connected too.
  • Can you rebuild the lead-scoring rules we mentioned?
  • We need another round of training for the sales team.
  • Just a small tweak to the onboarding workflow…
  • Can the portal support SSO for our partners?
  • Could you clean up the duplicate contacts first?

The problem

Scope doesn’t blow up. It leaks, one “quick one” at a time.

Delivery leads at implementation consultancies already know when a request smells like extra work. The hard part is proving it quickly, deciding consistently, and keeping a record anyone can follow.

  1. 01

    Requests arrive everywhere

    A line in an email thread, a comment on a call, a “while you’re in there”. Each one is small. Together they decide whether a fixed-price project makes money.

  2. 02

    The boundary lives in a PDF

    The statement of work said what was in and what was out. Finding the clause, the approved amendment and the email that changed it takes longer than doing the work.

  3. 03

    The decision leaves no trace

    Someone said yes on a call. Was that goodwill for this one request, or the new normal? Three weeks later, nobody can say, and the next request gets the same answer.

How it works

From signed agreement to a decision you can defend.

  1. 01

    Upload the agreement

    Drop in the statement of work as a text-based PDF, or paste the text. Every version is kept, and each page stays linked to its text.

  2. 02

    Confirm the scope baseline

    Agreeably proposes deliverables, exclusions, limits, dependencies and change procedures, each with a quotation checked word for word against the source. You correct, add and confirm.

  3. 03

    Check every new request

    Paste a client request or forward the email. Each requested change comes back as included, potentially additional or unclear, with the exact clauses behind it.

  4. 04

    Record the decision

    Charge, absorb, clarify or decline, with a reason. Change your mind and the history keeps both. Nothing is sent to the client unless you send it.

Try it

Pick a request. See what the agreement says.

A sample statement of work for a fictional CRM rollout. Each request is labelled included, potentially additional or unclear, and every label points at the words that support it.

Statement of Work · v2 · confirmed Sample
§3.1 Environments p. 3

The supplier will configure one sandbox and one production environment. Additional environments are subject to the change procedure in §9.

§4.2 Data migration p. 7

Migration covers contacts, companies and open opportunities from the legacy CRM. Historical invoices are excluded.

§5.1 Reporting p. 8

Up to five standard reports, including pipeline by stage, owner and region.

§6.2 Integrations p. 10

Integration with Mailchimp is in scope. Integration with the client’s accounting system will be confirmed during discovery.

Client request

“While you’re in there, can you also migrate the last three years of invoices?”

Migrate three years of historical invoices Potentially additional
§4.2 Data migration “Historical invoices are excluded.” ✓ matched to source

The migration list names contacts, companies and open opportunities, and §4.2 excludes historical invoices outright.

Next step Draft a change request, or record absorb if you choose to do it as goodwill.

Labels support your decision; they are not a ruling on the contract. You record charge, absorb, clarify or decline yourself.

The decision

Four answers. Each one means something precise.

The assessment and the decision are separate. Agreeably never decides for you, and each answer does exactly one thing, so nobody has to guess later what “we said yes” meant.

  • Charge 01

    The work is additional and you will ask to be paid for it.

    Recording charge sets no approval, value, invoice or payment. You draft a change request from it on purpose, with a price you enter yourself.

  • Absorb 02

    You will do it at no charge, for this request only.

    Absorbing is recorded as a goodwill exception. It never widens the baseline, so the next similar request is still assessed against what was signed.

  • Clarify 03

    The agreement does not settle it yet. Ask the client.

    The request waits in the Inbox under Waiting on the client until you return to it with an answer.

  • Decline 04

    Out of scope, and not work you will take on.

    The reason is kept with the decision, so anyone on the team can see why later.

Changed your mind?

A new decision is added to the history. The earlier one, its reason and who made it stay visible.

Re-ran the analysis?

The new split asks for fresh decisions. The earlier ones stay attached to the analysis they were made on.

Sent to the client?

Only if you share it in the client approval portal, on Business or Team. Otherwise change requests export as a clean PDF that you send yourself.

Email intake

Forward the email. That’s the workflow.

Every project gets its own private forwarding address. Forward a client email to it and Agreeably creates a request, runs the assessment and lets the lead know. Your client never sees any of it.

  • Forwarded by a member of your workspace who can see the project
  • SPF or DKIM aligned, with DMARC passing. A From header alone is never trusted.
  • Each provider message processed once, however many times it is delivered
  • Anything that fails is quarantined without revealing the project
  • Attachments are listed for you to review, never silently analysed
  1. Client emails you “One more small thing…”
  2. You forward it to the project’s private address
  3. Checked on arrival sender, authentication, allowance
  4. Request created body extracted, history kept as context
  5. Lead alerted a short summary and a link, once

Do the maths

What does “we’ll just absorb it” cost you a year?

Use your own numbers. This is arithmetic, not a promise: it shows what unbilled hours are worth at your rate.

Unbilled work per year A$7,128
Per month A$594
vs. Core at A$149/mo 4.0×

Trust

Built for documents you can’t afford to misquote.

  • Quotations verified, not generated

    Evidence is shown only when the exact words exist in your agreement. Anything else is flagged for a person to review.

  • Hosted in Sydney

    Application, database and files run on AWS in ap-southeast-2. Analysis by Anthropic happens outside Australia, and we tell you so.

  • Workspaces kept apart

    Every read and write is checked against your workspace. On Team, members see only the projects they are assigned to.

  • The model cannot act

    Instructions inside an agreement or email are treated as data. Sending email, billing and anything that changes state stay outside the model’s reach.

  • History that does not get rewritten

    Confirmed scope versions, assessments and decisions are append-only. A change adds a new entry; the old one stays.

  • Your data, exportable

    Export a readable bundle of a project at any time. A lapsed workspace stays readable and exportable before it is deleted.

Read how Agreeably handles your data →

Pricing

Priced in dollars you already bill in.

Monthly plans in Australian dollars. Start with a 14-day trial of Business, no card needed.

Core

For a firm running a few fixed-price implementations at once.

A$ 149 per month
excl. GST

Email us for early access
  • 5 active projects
  • 3 internal users
  • 200 request analyses a month
  • Scope extraction with verified quotations
  • Request analysis with cited agreement evidence
  • Forwarded-email intake and internal alerts
  • Charge, absorb, clarify or decline decision history
Trial runs on this plan

Business

For a firm that sends branded client documents and reports across clients.

A$ 249 per month
excl. GST

Email us for early access
  • 15 active projects
  • 3 internal users
  • 600 request analyses a month
  • Your logo and colours on client documents
  • Remove Agreeably branding
  • Reusable change-request templates
  • Reports across projects and clients
  • Client approval portal: 30 shares a billing period

Team

For a delivery team that needs approvals, assignments and permissions.

A$ 449 per month
excl. GST

Email us for early access
  • 30 active projects
  • 10 internal users, then A$29 each
  • 1,500 request analyses a month
  • Everything in Business
  • Internal approval workflows
  • Viewer role and per-project permissions
  • Assign reviews and decisions to teammates
  • Team workload and activity reporting
  • Client approval portal: 150 shares a billing period

Every plan includes scope extraction with verified quotations, request analysis with cited agreement evidence, forwarded-email intake and internal alerts, charge, absorb, clarify or decline decision history, change-request drafts with human-entered price and timeline and standard exports of everything you put in. The trial gives you Business for 14 days, without a card, with 50 analyses.

FAQ

Questions, answered plainly

What is Agreeably?

Agreeably is scope-control software for software implementation consultancies. A delivery lead uploads the statement of work, confirms the scope baseline, then checks each new client request against it. Agreeably labels each requested change as included, potentially additional or unclear, cites the exact agreement wording, and records the decision to charge, absorb, clarify or decline.

Who is it for?

Delivery leads and owners at small consultancies, roughly 3 to 20 people, running fixed-price CRM implementations, integrations, data migrations and business automation projects. It suits firms where requests arrive by email and in calls, and the agreed boundary is hard to reconstruct later.

Does the AI decide whether to charge the client?

No. The assessment and the decision are separate. Agreeably shows the evidence and suggests a next step; a person on your team records the decision and the reason. An assessment is not a contractual ruling and never approves work.

How do I know the quotations are real?

Every quoted passage is checked against the stored text of your agreement before it is shown. If a quotation cannot be found word for word, it is removed and the item is flagged for your review instead of being shown as evidence.

What happens when a client request is unclear?

If the agreement is silent, vague or contradicts itself, the item is labelled unclear rather than forced into included or additional. A missing clause never becomes an invented exclusion.

Can it read client emails?

Each project gets a private forwarding address. Forward a client email to it and a request is created for review. Only mail forwarded by a member of your workspace, with passing email authentication, is accepted. Attachments are listed but not analysed.

Does Agreeably send anything to my client?

Only when you share a change request in the client approval portal on Business or Team. Then the approving contact, and any listed addresses, get an email with the link, and visitors get a verification code when the share asks for one. Otherwise change requests are exported as a clean PDF for you to send yourself, and alerts go only to people inside your workspace.

Where is my data stored?

Files and the database are hosted on AWS in Sydney, Australia. Text sent for analysis is processed by Anthropic’s Claude API, which is outside Australia. We disclose this up front rather than in fine print.

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.

Email us for early access Compare plans

No card needed · Cancel any time · A$ pricing