# Agreeably

> Agreeably checks each new client request against your confirmed scope and approved changes, shows the exact clause it relies on, and records whether you charge, absorb, clarify or decline. It is built for delivery leads and owners at small software implementation consultancies (about 3 to 20 people) delivering fixed-price CRM implementations, integrations, data migrations and business automation. Pricing is monthly in Australian dollars: Core A$149, Business A$249, Team A$449, excluding GST, with a 14-day Business trial and no card required.

Key facts:
- Each requested change in a client request is labelled included, potentially additional or unclear. No numeric confidence score is shown.
- Every quotation shown as evidence is checked word for word against the stored agreement text; unverifiable quotations are removed and flagged for review.
- A person records the decision: charge, absorb, clarify or decline, with a reason. The AI assessment never decides and is not a contractual ruling.
- Agreeably sends nothing to the client unless the team shares a change request in the client approval portal (Business and Team). Otherwise change requests are exported as PDFs for the team to send.
- A portal approval is approval evidence, not an electronic signature, and the delivery lead still confirms any amendment.
- Hosted on AWS in Sydney, Australia. Analysis uses Anthropic's Claude API, outside Australia.
- The web app is launching soon. For early access, email hello@agreeably.io.

## Product
- [How it works](https://agreeably.io/product/): agreement intake, scope baseline, request assessment, decisions, change requests, amendments, Inbox.
- [Pricing](https://agreeably.io/pricing/): plans, limits, trial and billing rules.
- [Security and data](https://agreeably.io/security/): hosting location, isolation, email intake checks, AI safeguards, export and deletion.

## Use cases
- [Scope control for CRM implementation partners](https://agreeably.io/use-cases/crm-implementation/): Check every client request on a fixed-price CRM rollout against the signed scope: pipelines, objects, reports, environments and training, with the clause quoted.
- [Scope control for data migration projects](https://agreeably.io/use-cases/data-migration/): Keep fixed-price data migrations inside their boundary: which objects, how much history, who cleanses the data and how many trial loads, checked request by request.
- [Scope control for integration and automation projects](https://agreeably.io/use-cases/integrations-and-automation/): For fixed-price integration and automation work: check requests for new systems, faster syncs, error handling and extra workflows against the agreed scope.

## Guides
- [Scope creep in fixed-price software implementations: how to spot it early](https://agreeably.io/guides/scope-creep-in-fixed-price-implementations/): Why fixed-price CRM, integration and migration projects leak margin through small requests, the five shapes scope creep usually takes, and a routine for catching it before work starts.
- [Charge, absorb, clarify or decline: deciding what to do with an out-of-scope request](https://agreeably.io/guides/charge-absorb-clarify-decline/): A decision framework for delivery leads: when to charge for a client request, when absorbing it is the right call, when to ask first, and how to record the decision so it holds up later.
- [How to write a change request a client can approve quickly](https://agreeably.io/guides/how-to-write-a-change-request/): What a software change request needs to contain, the order to put it in, and a plain template you can copy, with the mistakes that slow approval down.
- [Statement of work clauses that make scope questions easy to answer](https://agreeably.io/guides/statement-of-work-clauses/): The deliverable, exclusion, limit, dependency and change-procedure clauses that let you answer “is this in scope?” in seconds, with examples for CRM, migration and integration work.

## Optional
- [Full plain-text product description](https://agreeably.io/llms-full.txt)