The change-request lifecycle

What you agreed to is never in question.

Confirmed by both sides, on the record. When the project changes, the record changes with it.

Paste any conversation — any language in, a clean scope out → your client confirms it line by line → every new request checked against it.

Start Free → See it in action
Scroll
Who it’s for — premium, change-heavy client work that begins with a conversation

It arrives mid-project. It sounds small. And it costs you nights, weekends, and unpaid work — because nobody can point to what was actually agreed.

0%
of projects experience scope creep — Project Management Institute. The only statistic on this page, and it isn't ours.

Your notetaker remembers what was said — but it can't confirm anything.

Your CRM and project tools track the work on your side — but a task board isn't an agreement your client confirmed.

Nothing holds a record you both confirmed when the work changes. That's the gap ScopeLinq closes.

Every project follows the same pattern
01 / 04
Conversation Agreement New request Decision

It starts in a thread. Paste an email, a text, meeting notes — any capture tool, any language.

Confirmed line by line, by both sides. Signed, timestamped, on the record.

"While you're at it…" arrives mid-project — checked against the record the moment it lands.

The record answers. You decide: quote it now, or save it to the backlog.

Client"yes to the kitchen scope we walked through 👍"
"$12k cabinet allowance works — we'll pick finishes by the 15th"
You"perfect. demo starts Monday — final walkthrough June 20?"
"june works. oh — while you're in there, can we also redo the laundry room? it's a small space"
SL-2210KITCHEN RENOVATION · AGREEMENT
Confirmed · May 2
1Full kitchen remodel per approved plan: cabinets, counters, backsplash
2Cabinet allowance $12,000; selections by May 15
3Work outside the approved plan quoted separately
4Final walkthrough June 20
SENT VIEWED CONFIRMED
Can we also redo the laundry room?
● Out of scope Outside SL-2210, clause 3: "work outside the approved plan quoted separately."
Keep scrolling
Try it yourself

A request arrives.
The record answers.

Tap a client message below — every verdict cites the confirmed agreement, never a bare AI opinion.

SL-1042CONFIRMED BY BOTH PARTIES
Confirmed · Mar 3
1Primary bath + adjacent bedroom: concepts, selections, and finish plan
2Furniture and fixture selections — two revision rounds included
3Designer sourcing and vendor coordination
4Rooms beyond the primary bath and adjacent bedroom quoted separately
5FF&E allowance: $18,000 — client approves overages in writing
6Install complete by May 15; freight, receiving, and storage billed separately
SENT VIEWED CONFIRMED
Ready-to-send reply · yours to edit
TWO EQUAL PATHS, EVERY REQUEST · BACKLOG ITEMS PROMOTE ANYTIME
Try a real world scenario →
The Evidence Ladder

Even silence becomes
part of the record.

Sent

The agreement leaves your hands, on the record.

MAR 1 · 9:14 AM
Viewed

Your client opened it. Timestamped automatically.

MAR 1 · 4:52 PM
Confirmed

Both parties on the record. Every rung has value; reminders capped at two.

MAR 3 · 11:06 AM
"
We're proceeding based on the agreement sent March 1. Reply if anything needs to change.
The Proceeding Notice — silence, documented
Downstream of any capture tool · Upstream of any invoice
Agreement Memory

Smarter with every
confirmed agreement.

Not documents. Not notes. Memory. Your exclusions, your revision patterns, your clients' habits — surfaced from project one.

Capture→ Memory→ Intelligence→ Prediction

THE FIRST TWO ARE HERE TODAY. THE REST IS WHERE THIS IS HEADED — NO PROMISES THAT DEPEND ON DATA WE DON'T HAVE.

PROJECT MEMORYComplete
ProjectWebsite Redesign
Confirmed items42
Change requests7
Most common issueLate revision requests
Recommendation · next projectAdd revision limits earlier. Saved to Agreement Memory.
Why you can believe it
The AI cites its sources or abstains — it’s designed to avoid making things up.
T–01

Every answer points to a line you both approved

If the record doesn't cover it, ScopeLinq says so. A guess is never sent to your client.

T–02

We stay out of your money

No payments, no invoicing, no money movement. You copy the SL reference into the tools you already use.

T–03

Signed, timestamped, yours alone

Both parties on every record, every step timestamped. Your notes and agreements are never used to train AI.

Start free. Upgrade when every project
deserves a record.

Free
$0
Your first project, on the record.
  • Capture a conversation, confirm the agreement
  • Clause-linked verdicts on every change request
  • The Evidence Ladder — Sent, Viewed, Confirmed
  • Ready-to-send replies, yours to edit
Start Free
Pro
$19 /month
Every project remembered.
One $450 change order caught pays for two years of Pro.Less than one billable hour a month.
  • Everything in Free, unlimited projects
  • Backlog, batch review, numbered change orders
  • Proceeding Notices & capped smart reminders
  • Project Memory Cards & Agreement Memory
Start Free, then upgrade →
Fair questions

What skeptics ask first.

I already have contracts.
Good — keep them. ScopeLinq isn’t your contract; it’s everything that changes after the contract is signed. Your contract set the project; the record tracks the "one more things" your contract never anticipated. Keep Bonsai or HoneyBook exactly where they are.
Will clients actually confirm?
Confirming is one click on a clean, plain-English list — and it protects them as much as you. Even when they don’t, a Sent-and-Viewed record already beats a text thread, reminders are capped at two, and the Proceeding Notice turns silence into documented context.
Do I have to record my calls?
No. ScopeLinq records nothing. Paste whatever you already have — an email, a text thread, meeting notes, or the export from any notetaker you use. Any language in, a clean English scope out.
Is this just AI summarizing my notes?
The AI drafts; you edit; your client confirms. From then on, every verdict cites the exact line you both approved — or says the record doesn’t cover it. An AI opinion is never sent to your client.
What happens to my data?
Your notes and agreements are never used to train AI. Records are two-party confirmed, signed, and timestamped — and they’re yours.
Be among the first on the record

Move forward with confidence — not debate.

ScopeLinq remembers what was agreed, so it's never in question later. Your next "Can we also add…" is the perfect place to start.

Start Free →
SL-0001·YOUR NEXT PROJECT·UNWRITTEN — UNTIL YOU START