Start with the agreement.
Put the original deliverables beside the client's new request. See which parts need an explicit scope decision.
EARLY-STAGE PRODUCT CONCEPT“Just one
“Just one
more thing.”
Let's scope it.
A clearer way to handle client changes. Compare the request, discuss the impact, and agree on the next step before doing extra work.
Designed for freelancers & small agencies · Claude integration planned
CTHE CLIENT / NEW MESSAGE
“The website looks great! Can we also add online booking and payments?”
Illustrative exampleA change worth clarifying.
Agreed scopeInformational website
New requestBooking + payment workflow
Next stepConfirm scope, quote separately
Illustrative concept output, not a live AI analysis.
THE PROBLEM WE WANT TO TESTSmall requests can carry bigger implications.Make the conversation visible.
A BETTER CHANGE CONVERSATIONCatch the difference.
Catch the difference.
Keep the relationship.
ScopeNivo aims to help freelancers discuss additional work clearly, without losing the context of what was originally agreed.
Make the impact concrete.
Enter your own estimate and hourly rate. Use transparent arithmetic as a starting point for the quote.
Keep the reply constructive.
Draft a response that acknowledges the request, asks the missing questions and seeks approval before work starts.
INTERACTIVE WORKSPACEYour next “one more thing”,
Your next “one more thing”,
made easier to discuss.
This local prototype checks keyword overlap and creates a response from templates. It does not call Claude, understand contracts or estimate effort for you.
01 / PROJECT CONTEXTYOUR INPUT
Inputs stay in this tab. Enter estimates you can justify.
02 / CHANGE DISCUSSIONTEMPLATE DRAFT
Human review required. Keyword overlap does not determine contractual scope. This is a concept demo, not a price recommendation or an automated quote.
WHERE WE WANT TO GOLess guesswork.
Less guesswork.
More shared understanding.
Our hypothesis: freelancers can avoid preventable rework by clarifying change requests before committing to them. We plan to validate the workflow through interviews and prototype tests.
The proposed Claude-powered product would compare requirements in context, flag ambiguity and draft a change summary. Freelancers would review every interpretation and provide their own effort estimates.
NOW
Interactive concept
A browser-only workflow with sample scenarios, editable context and downloadable drafts.
NEXT
Validate with freelancers
Test the problem, the language and the usefulness of the proposed change conversation.
PLANNED
Claude-powered MVP
Add context-aware comparison, evaluate output quality and define controls for client information.
CLEAR FROM THE START
About this prototype.
Is ScopeNivo available as a finished product?
No. This is an early-stage concept and interactive prototype. No customer traction, revenue or production AI capability is claimed.
How does this demo check scope?
It compares a small set of keywords for booking, payments, packaging, data refresh and similar features. If a keyword group appears only in the new request, it flags a possible addition. Otherwise it requests manual review. This method cannot understand obligations, exclusions or nuanced language.
How are the hours and price calculated?
You provide the hours and hourly rate. The demo multiplies those inputs. It does not infer effort, include taxes or fees, or recommend what you should charge.
Does it send my client messages to Claude?
No. The demo processes text in your browser tab without calling an AI API or saving inputs on a server. Downloaded text is stored on your device. Live Claude integration is planned, not implemented.
Before saying yes,
make the change clear.
Explore one example. Then try your own project context.