Skip to content

Features

What AI-mated does, and what it deliberately does not.

Everything below exists in the product today. It is a sidecar: your team keeps its task tool, time tracking and chat; AI-mated connects the agreement, the requests and the delivery.

Scope intelligence

One authoritative answer to “what did we agree?”, kept current as changes are approved.

Scope › BaselineMeridian Growth Retainer · Meridian Retail

Agreement in force

Published

Baseline v1

Published1 Jun 2026
Approved budget£8,000.00
Agreed end date18 Dec 2026
Approved changes0

Immutable. An approved change creates v2.

Reviewed scope statements

From the SoW · reviewed by a person
  • Monthly conversion optimisation of existing pagesIncluded
  • Ongoing support and bug fixes on the current siteIncluded
  • Design or build of new pages is not includedExcluded

Requests against this agreement

New landing page for the spring campaignOut of scope
  • Statement of work, uploaded or written

    Upload a SoW or write it in the in-app editor with version history and diff. Approving a version materialises the document; statements carry over.

  • Reviewed scope statements

    AI proposes statements from the document, each citing the passage it comes from. A person classifies them as included, excluded or unclear; unreviewed proposals are never scope.

  • Immutable baselines

    Budget, rates, planned hours and dates are published as a numbered baseline. A change creates the next version; nothing is overwritten.

  • Agreement in force

    The published baseline plus every client-approved change in decision order, at the version the client approved, with the SoW version the statements quote.

  • Project brief

    A living, templated brief with gaps shown, and “Draft the SoW from this brief”.

  • Scope check on every request

    Each change-type request is compared with the agreed scope and the matching clause is quoted. Citations of clauses a newer SoW replaced are flagged so the comparison runs again.

Requests and change requests

Turn an ask in plain words into a priced, scheduled proposal, with the numbers done by rules.

CR-3 · Spring campaign landing pageMeridian Growth Retainer · Meridian Retail
  1. Received
  2. Proposal being prepared
  3. 3Waiting for your decision
  4. 4Approved
  5. 5In progress
  6. 6Completed

What the client asked

Client portal · 11 Sept 2026
Hi both — for the spring campaign we need a new landing page with a signup form. Can the team design and build it this month?

Scope check

Matches excluded scope

Cited from the agreed scope

“Design or build of new pages is not included”

Project manager’s decisionOut of scope
WarningRaised by the possibleScopeChange check

Work outside the agreed scope is not covered by the budget until a change request is approved

Impact on the project

Deterministic
  • Landing page design · Designer16.0h
  • Build and sign-up form · Developer20.0h
  • QA and launch · QA6.0h

low

£4,720.00

expected

£5,860.00

high

£7,640.00

Price to the client at the rate card, with the range of similar past work.

Internal cost£3,310.00
Margin on the change£2,550.00
Earliest finish with today’s capacity21 Sept 2026
ScheduleWithin the current forecast
Health after the changeOn trackOn track

Proposal v1

Waiting for your decision
£5,860.00Time and materials · 42.0h

Decision requested by 23 Sept 2026 · approval becomes baseline v2

  • Seven kinds of request

    Change, new work, information, decision, approval, support and feedback — named per workspace, with starter templates for software, creative, marketing, IT implementation and consulting teams.

  • Queues and triage

    Open, needs triage, needs assessment, waiting on client, in delivery, done — per project and across the workspace. Routes: take on, answer, ask the client, convert to a change request, decline with a reason.

  • Guided assessment

    Lines by role priced from your rate card; hours suggested from similar completed work; billing treatment; timing from the capacity simulation.

  • Impact on the project

    Price, cost and margin as a low–expected–high band, the project’s margin before and after, the earliest finish with today’s capacity, and every health check re-run on the changed plan.

  • Versioned proposals

    Each proposal is a version the client decides on. Prepare the wording with AI, grounded in the records; edit everything before it goes out.

  • Apply the approved change

    Checklist and delivery status per change; a draft baseline for you to publish; a “Change CR-n” section drafted into the SoW from client-safe facts; tasks created in ClickUp after your approval.

  • Retainers

    A monthly allowance per engagement, usage per calendar month from time entries, and whether a request is covered by the retainer or billed.

Approvals and decisions

Nothing consequential happens without an approval, and every approval is something you can point at later.

Client portal · CR-3 Spring campaign landing pageMeridian Retail
  1. Received

  2. Proposal being prepared

  3. 3

    Waiting for your decision (current step)

    A proposal is ready for your decision.

  4. 4

    Approved

  5. 5

    In progress

  6. 6

    Completed

£5,860.00Time and materials
Effort42.0h
TimingWithin the current forecast
Decision requested by23 Sept 2026

Assumptions. You provide the campaign copy and the sign-up tool account.

What the decision records

  • DecisionApproved · Changes requested · Declined
  • ByA client approver, named, in the portal — or the PM, recording a decision taken elsewhere
  • OnProposal v1 and its content hash — this text, not “the latest”
  • ThenDraft baseline v2 for the PM to publish

Internal gates work the same way: ask a teammate to review the draft, and their answer is an approval bound to the same version.

  • Approval before action

    Baselines, recommendations, change proposals, client messages and task-tool writes all need an approval from a role that may give it. Both the server and the database enforce it.

  • Decisions bound to a version

    A client or internal decision is stored with the proposal version, its content hash and the person who decided — the exact text, not “the latest”.

  • Decision requests for both audiences

    Ask a client approver or a teammate for a decision; an inbox of what waits on you, overdue reminders, and a History view of what is waiting on whom.

  • Recorded, not automatic

    Approvals, dismissals, client decisions and edits are written to an insert-only audit log with the reason. The assistant’s action cards run only after you confirm.

  • Client-safety check

    Anything meant for a client — a proposal, a report, a portal page — is checked for internal cost, rates, margin and restricted notes before it is shown.

Client collaboration

A portal per client, shared project by project, with the sections you choose.

Client portal · Meridian Retailportal/studio-meridian

Meridian E-commerce Replatform

Status as of 16 Sept 2026

Needs attention
  • Parts of the timeline are under review; we will confirm any date changes with you.
  • Some work is waiting on an input or dependency.
Progress17.6%
Agreed end date18 Dec 2026
Forecast completion15 Nov 2026
Next: Beta release25 Sept 2026

CR-3 Spring campaign landing page

  1. Received

  2. Proposal being prepared

  3. 3

    Waiting for your decision (current step)

    A proposal is ready for your decision.

  4. 4

    Approved

  5. 5

    In progress

  6. 6

    Completed

Price£5,860.00
Effort42.0h
Never shown to the clientInternal costCost ratesMarginIssue titles and internal notes
  • Shared sections

    Timeline, deliverables, requests, documents shared one by one, approved status reports and “What you pay” — on or off per project.

  • Requests from the client

    Clients send requests of the kinds you allow, attach files and follow the status. Your assessment notes stay internal.

  • Decisions in the portal

    Client approvers decide on proposals and optionally accept delivered changes; deliverable reviews are recorded with who decided, through the same decision core your team uses.

  • Costs, from the client’s side

    The agreed contract, each approved change at its approved price with who confirmed it, the total agreed and proposals waiting — never your cost, budget, rates or margin.

  • Clients, engagements and contacts

    Clients as a workspace area with what waits on you and on them; optional engagements under a client; contacts with roles (decision maker, approver, contributor, informed).

  • Free client users

    Portal users belong to a client, are invited by one-time link and are never seats. Preview any project as the client would see it.

Project visibility

Know in the week it starts, not on the invoice.

TodayStudio Meridian · analysed 16 Sept 2026

20 items wait on you across 9 projects.

  • Blocked1Blocked projects
  • At risk3At risk projects
  • No data2No data projects
  • On track3On track projects
  1. BlockingRecommendation· Decision needed

    Re-plan "Cutover" start

    Helios Data Platform · "Cutover" is blocked by "Legacy export" — Successor cannot start before the predecessor finishes plus lag.

  2. CriticalRecommendation· Decision needed

    Confirm remaining effort with the team

    Northwind Client Portal · Forecast €28,350.00 over approved budget; Forecast margin below floor — Forecast depends on remaining estimates that may be stale.

  3. WarningRecommendation· Decision needed

    Prepare a change request

    Meridian Growth Retainer · Out-of-scope request "New landing page for the spring campaign" has no change request — The work was ruled out of scope; delivering it without an approved change request gives it away.

  4. WarningRecommendation· Decision needed

    Chase “Payment provider sandbox credentials”

    Meridian E-commerce Replatform · Waiting on the client: Payment provider sandbox credentials; 4 items under "Beta release" are overdue — Work that waits on it cannot move; every day it stays late is lost from the schedule.

  • Deterministic health checks

    Budget and margin, consumption vs. progress, overdue work, date alignment, dependencies, overallocation, stale data, client dependencies, risks, deliverable reviews, scope — each with a documented threshold and its own tests.

  • Issues with evidence

    Related symptoms are grouped under one cause with category, severity, confidence and its reason, evidence, impact and a proposed fix. Approve, edit or dismiss, on the record.

  • Today

    Decisions, actions and what is being watched across every project, ranked by severity, each with why it matters and what to do.

  • Financial position

    Forecast cost, variance and margin from logged time and your rate card, with the basis stated. Missing data lowers confidence instead of hiding.

  • Reports

    Internal and client status reports assembled from the same evidence; the client version is redacted by construction and approved with a content hash.

  • Assistant with citations

    Ask about one project or the portfolio. Every figure is read from a cited record; questions outside your data are declined, not guessed. Proposed actions are cards you confirm.

  • Daily analysis and notifications

    Analysis at 06:00 workspace time and on every sync; in-app notifications for new critical issues, requests, decisions and overdue asks; follow or mute a project.

Connections

Read your tasks, time and technical context from the tools you have. Each connection says what it writes.

  • ClickUpLive
  • CSV importLive
  • GitHubLive
  • SupabaseLive
  • HarvestSoon
  • AsanaSoon
  • JiraSoon

What it writes. ClickUp only: task dates, assignees and new tasks for an approved change — each after a recorded approval, and only if write-back is switched on for that connection. Nothing is ever deleted.

Not in AI-mated, on purpose

  • A task board, timesheets or resource planning — your existing tools keep those
  • Invoicing and payments to clients
  • Automatic writes to your tools or emails to clients without an approval
  • Figures from a language model: no estimated hours, rates, dates or money

Everything on this page is in the product today; roadmap items are marked “Soon”.

See it on your own projects.

Guided pilot for agencies and consultancies of about 10–100 people. One email when your spot opens.