See it in action →
For Interior Designers

The 9pm "just one more thing" text. How many hours did it take this month?

Two questions. One number. The math stays on the screen, and every assumption is yours to change.

The two-question audit
Q1  How many active client projects right now?
Q2  Out-of-scope asks per project, per month — texts, "quick" swaps, the extra room?
in unbilled design time per month ( hours)
Assumptions — adjust them:
1.5 hours reflects what a "quick" ask really takes: the sourcing, the revised board, the follow-up thread. Yours may run longer.
Put your next consult on the record — free See how it works →

Death by a thousand small cuts

It rarely arrives in a meeting. It arrives as an inspiration image texted at 9pm. A "while we're at it, what would you do with the guest room?" A "tiny" swap that means re-sourcing, a revised board, and a new thread with the workroom. Each ask is small, sincere, and sent by a client who genuinely loves working with you — which is exactly why saying "that's outside our scope" feels impossible in the moment.

So you absorb it. Designers describe this pattern the same way, over and over: death by a thousand small cuts. Not one big dispute — a slow leak of evenings and sourcing hours that never appear on an invoice, because by the time you could bill them, pointing back to the letter of agreement feels like litigating against a friend.

The real problem is the missing record

Your contract defines phases and fees. What it can't hold is the living detail of what was actually agreed in the consult — which rooms, how many concepts, how many revisions, what was explicitly out. That detail lives in your notes, your inbox, and two people's memories. When a request drifts past the boundary, there's no shared reference to point to, so the choice becomes: do it free, or have an awkward conversation with nothing to stand on.

Some designers have started solving this by hand — keeping timestamped meeting notes precisely so clients can't later say they forgot what was agreed. It works. It's also unpaid administrative work, and it only helps after a dispute has already turned cold.

Confirmed once, answered forever

ScopeLinq does the by-hand version automatically, and adds the step that changes the relationship: the client confirms. After the consult, paste your notes or emails — ScopeLinq turns them into a clean scope, line by line, and your client confirms it in one click. To the client it reads as care, not caution: here's everything we discussed — confirm it looks right.

Then when the 9pm text arrives, you check it against the record. The verdict cites the confirmed line it falls under — or shows it's new. If it's new, you get a ready-to-send reply that keeps the warmth and adds a price: love this idea — it's beyond what we confirmed, want me to quote it as an addition? The extra room becomes a proposal instead of a lost weekend.

The record is the boundary, so you never have to be.

ScopeLinq isn't a contract and doesn't touch your billing. It sits between your letter of agreement and your invoices: the shared memory of what was decided, kept current as the project evolves.

Fair questions

Won't asking clients to confirm feel adversarial?

It reads as the opposite — a clear, professional recap confirmed in one click. Clients get certainty too. The friction designers fear lives in the mid-project boundary conversation; confirming at kickoff is what makes that conversation unnecessary.

Is this a contract?

No. It's a shared record of what was agreed, confirmed by both sides — evidence and clarity that sits alongside your letter of agreement, not in place of it.

Do I have to write everything up?

No. Paste the consult notes, emails, or texts you already have, in any language. ScopeLinq turns them into a clean scope. You edit, the client confirms.

What does it cost?

Your first project is free, no card. Pro is $19 a month — less than twenty minutes of billable design time.

Your next "just one more thing" is the place to start

First project free. Paste your consult notes, send the record, and see the difference on one client.

Try it in five minutes →