For implementation firms that eat the cost of scope drift
The scope changed seven times. You billed for none of them.
Konosa captures scope changes the day they happen, and collects client acceptance per requirement with the evidence attached. Now the invoice is a receipt for work your client already approved, not an argument you have to win.
Your client approves in their own portal. They see a before/after diff with the price on it, not a surprise invoice eight months later.
Wrenfield Logistics · the record
Discovery call → paid invoice · one chain
- 14 MarDiscovery call → 35 requirements draftedDraft
- 21 MarClient signs the baseline, line-by-lineSigned
- 02 JunREQ-021 drifts · diff detected from PAY-412Drift
- 03 JunCO-004 approved · +$8,400 · +2 weeksBilled
- 17 JunREQ-018 delivered with evidence · client accepts in portalAccepted
- 30 JunInvoice cites 28 acceptances by ID · paid in 31 days+$31,200
Every line links to its signed version, evidence, and certificate
Built for the three moments that decide whether you get paid.
- Scope drifts
- Price it as a change order the same day, with the diff attached
(instead of absorbing it and calling it goodwill) - Work lands
- Collect acceptance on that requirement, evidence included
(instead of chasing one sign-off at the end) - “We never agreed”
- Show the signed line, timestamped, in one click
(instead of searching eight months of email and Slack)
01
The leak
Agencies don’t lose scope disputes in court. They lose them quietly, every month.
That extra integration, that last-minute round of revisions, that extra report nobody scoped: all delivered, unbilled, with the cost absorbed. Not because firms don't want the money, but because by the time anyone noticed, the dispute wasn’t worth risking the relationship.
- 78%
- of agencies rarely or never charge for out-of-scope work.Ignition 2025 · n=273
- $1–5K
- lost per month to unbilled out-of-scope work. Roughly 30% lose more.Ignition 2025
- $7.70
- of new revenue you must sell to replace the profit on every $1 you absorb, at a 13% net margin.Promethean Research 2025 · Derived from 13% net margin
Consider this proven model
A good mechanic sends you a photo of the worn brake pad with the quote, and a photo of the new one with the invoice. You pay without issue because the evidence arrived before the bill did.
Konosa is that discipline, applied to a six-month implementation: evidence with the quote, evidence with the invoice, per requirement.
Konosa workspace · change order CO-004
REQ-021 drifted from the signed text: + ACH via Plaid, retry logic
Jira · linked as source
Call excerpt · 02 Jun · 14:12
Evidence with the quoteauthorizes
Client portal · review queue
REQ-018 · Month-end close reports. Delivered, evidence attached
Close report · screenshot 1 of 3
Walkthrough · 4:12
Evidence with the invoicegets paid
02
The chain
One unbroken chain from discovery call to paid invoice.
Each link of the chain produces the evidence the next one runs on. Break the chain anywhere and you’re back to disputing from memory.
1Automated capture
Konosa automatically drafts every requirement from the discovery call and the threads that follow. Your team makes adjustments, and nothing enters the ledger without its source.
Output
A requirement, in writing, with its source
included in v12Client sign-off
The client reviews the scope and signs the baseline. This is the source of truth that we refer back to. Agreements are versioned, all actions are timestamped
Output
A signed, versioned agreement on the baseline
included in v13Drift → change order
When discovery and discussions diverge from the last agreement, Konosa allows you to price and send the change order the day it happens, not at the end of the month.
Output
A priced change order, same-day
included in v14Parked scope
Not everything that has drifted should be worked immediately. Park it with an explicit client acknowledgment, so deferred work never silently becomes expected.
Output
An acknowledged deferral
next5Prove & get paid
Each requirement ships into review with its evidence. The client accepts it there, and the invoice cites the acceptances by ID.
Output
An acceptance certificate per requirement
included in v1
Deliver to clients the day work is ready, not at the next demo.
When a requirement is done, it moves into the client’s review queue with all the evidence attached. The client then accepts it or raises an issue. They can give feedback on the requirement, that week.
No more one giant sign-off at the end, where a single objection holds the whole invoice hostage.
Monday
Wednesday
Invoice day
03
The difference
Your tools currently track “who’s doing what today.” Konosa answers “what did we promise, what has changed, and what’s been accepted.”
| Capability | Konosa | PM tools | E-signature |
|---|---|---|---|
| One signed source of truth per requirement | ✓ | ✕ | The PDF, once |
| Versioned diffs when scope drifts | ✓ | ✕ | ✕ |
| Drift priced as a change order, same day | ✓ | ✕ | ✕ |
| Per-requirement client acceptance with evidence | ✓ | ✕ | ✕ |
| Court-grade record: identity, timestamp, hash | ✓ | ✕ | ✓ |
| Who is doing what today | ✕ (keep your PM tool) | ✓ | ✕ |
04
The numbers
The cheapest margin you’ll ever recover.
Benchmarks put services leakage at ~4.5% of revenue. Let's assume Konosa recovers a conservative fifth of it.
Assumes 4.5% of services revenue leaks (SPI benchmark) at a 13% net margin (Promethean 2025). The 20% recovery rate is our own conservative estimate, not a benchmark.
Per year
Per project
05
Evidence
Built like evidence, because someday it might be.
Every signature and acceptance is recorded the way courts already accept from e-signature platforms: who, when, from where, and against exactly which version of the text — exportable as a certificate PDF whenever you need it.
Most of the time you’ll never need it. The point is that your client knows you have it, which is why the dispute doesn’t happen.
Plus: a lawyer-drafted MSA clause template that makes portal acceptance your contract’s official amendment mechanism.
Konosa
Record
Requirement
Accepted by
Method
Timestamp
IP address
Snapshot hash
Meets the standard courts already accept from e-signature platforms. Nothing more claimed, nothing less kept.
06
Roadmap
Let's be honest about where we’re at.
Shipping first · v1
- Requirements drafted from call transcripts, generated as agreements
- Support for both new and in-flight projects
- Agreements sent to client for line-by-line review
- Signed, versioned scope baseline
- Per-requirement delivery evidence
- Manual drift detection → we generate and send priced change orders
- Client acceptance loop and review queue
- Acceptance certificates on every sign-off
Next
- Video call provider integrations (e.g. Google Meet, Zoom)
- Project management tool integrations (e.g. Jira, Linear)
- Automated drift detection → we generate and send priced change orders
- Parked-scope registry, with client acknowledgment
Not building
- Task boards, standups, or time tracking
- Resource planning
- Anything that answers “who’s doing what today” (leave that to your current PM tools)
07
Pricing
Priced per project, not per seat.
The design-partner offer · limited
Run your next project on Konosa.
This cohort exists to prove the assumption the whole product rests on: that clients will accept work per-requirement when the evidence arrives with it.
Price
Commitment
You get
Exit
7 spots remaining
Standard plans · live pricing
08
FAQ
You probably have some questions.
Isn’t this just another tool my team has to update?+
No. Your tracker stays your tracker. Konosa watches the agreement, not the work. Drift is detected from the artifacts you already produce, and the only person who has to act is the one sending the change order.
Will clients actually review and sign requirements?+
They already sign SOWs; this is the same act with better resolution. Honest note: per-requirement acceptance at delivery time is the assumption our design-partner program exists to prove.
Does a Konosa signature hold up legally?+
Signatures and acceptances are recorded under ESIGN/UETA the way e-signature platforms record them: identity, timestamp, IP, and a hash of the exact text signed. It meets the standard courts already accept from those platforms. We claim nothing beyond that.
We already have PandaDoc/DocuSign.+
Those sign the SOW on day one. Konosa governs everything that happens after: that's the change orders, the parked work, the “while you’re in there” asks. That’s the part where the money leaks.
What happens to our records if we leave?+
Full export, always. Every version, signature event, and certificate.
If AI drafts the scope, who’s responsible for what it says?+
You are, which is the design. AI drafts from the discovery call, your team edits every line, and the client reviews everything before signing. Nothing is ever agreed to that two humans didn’t read.
Our scoping is messy. Half of it happens on calls.+
That’s the input, not the obstacle. Konosa drafts requirements from exactly that mess and turns it into something signable. Messy scoping is why the write-offs exist.
Won’t change orders on every drift annoy my clients?+
Detection isn’t invoicing. You see every drift, you choose which become change orders, which get parked with acknowledgment, and which you absorb deliberately. The difference is that absorbing one becomes a decision, not a default.
09
Contact
The next “we never agreed to that” is already on your calendar.
I spent years writing estimates, managing delivery, and running implementation at an agency. What I learned is that the money we missed out on was never lost in negotiation... rather it was lost quietly. It was lost in the gap between what was said and what was documented.
Scopes change often, and I know that some requirements never even make it from sales to the implementation team. On top of that, a lot of clients truly don't know what they want (until they see what they don't want).
I've come to accept that project scopes will always evolve, and that good communication is necessary for these projects to be successful.
Konosa is the solution that I wish my teams had to help wrangle all of the scope creep, pending change orders, and parked work. A handful of firms now get to help us shape it. If you're feeling the same struggles that I did, I’d like one of them to be you.
- Brad
Every signature and acceptance is recorded with identity, timestamp, IP, and a hash of the exact text signed, encrypted in transit and at rest. Your records are yours, with a full export available at any time: every version, signature event, and certificate, for as long as your account exists and after you leave.