How it works
From a short description to a clearer pricing view.
PreciselyMaybe separates interpretation from calculation: the scope is mapped and confirmed first, focused questions refine the assumptions, and a deterministic engine calculates the result.
The flow
- 01
Describe the work
Up to 300 characters in your own words. Plain language is enough — no documents, no names.
- 02
Confirm the mapped scope
PreciselyMaybe maps the description to concrete activities. You review the work type, complexity and activity list before anything is calculated.
- 03
Refine the assumptions
Answer only the questions that can change scope, effort or risk, then add any optional fee, target rate or time estimate.
- 04
Read the result
See effort, risk, Price Fit, assumptions and jurisdiction context, with the reasoning kept visible.
How the decision is built
Interpretation and calculation stay separate.
Language models help read the scope and explain the finished result. The numeric recommendation comes from PreciselyMaybe' deterministic engine, after you confirm the assumptions.
Interpret scope
A generic description is mapped to work type, complexity and expected activities.
Confirm assumptions
You adjust the activity list and answer only questions that can change effort or risk.
Calculate result
The deterministic engine calculates hours, risk, scenarios and Price Fit. AI does not own this math.
Add context
Verified public jurisdiction references are shown when available, with their limits made explicit.
What the output includes
Every number is calculated from the work identified and explained line by line.
Price Fit
78
70–84 Reasonable fit
- Estimated time
- An activity-based range, not a single guess.
- Value per hour
- Your proposed fee divided by the estimated time range.
- Extra-work risk
- Low, medium or high, driven by named scope-expansion factors.
- Price Fit
- A 0–100 reading shown only when a proposed fee exists.
- Missing scope items
- The work most often forgotten in this kind of matter.
- Pricing context
- Public references with their source, strength and legal meaning.
Effort range, not a single number
Activities accumulate into a minimum and a maximum. The longer-work scenario widens only when real uncertainty drivers are present.
Effort range, not a single number
Activities accumulate into a minimum and a maximum. The longer-work scenario widens only when real uncertainty drivers are present.
How Price Fit reads
Price Fit describes alignment with the mapped work. It never says a fee is correct or fair.
How Price Fit reads
Price Fit describes alignment with the mapped work. It never says a fee is correct or fair.
85–100 Strong fit
70–84 Reasonable fit
50–69 Review recommended
Below 50 Weak fit
The math is visible
No hidden multipliers. Value per hour is a division you can check yourself.
The math is visible
No hidden multipliers. Value per hour is a division you can check yourself.
Proposed fee
12,000
Estimated time
14 – 22 h
Value per hour
545 – 857
Why it helps
01
Scope becomes explicit
The activities behind a matter are listed before a number is discussed, so nothing quietly disappears from the price.
02
A defensible starting point
An effort range built from named tasks is easier to explain to a client than an instinct.
03
The expansion risk is named
Unknown revision rounds, ancillary documents and authority dependencies are surfaced instead of absorbed.
04
Same reasoning in three languages
The interface, questions and explanations work in English, Portuguese and Spanish.
Percy is learning
What PreciselyMaybe combines
PreciselyMaybe puts four things in one place: a reading of the scope you described, focused questions that adapt to the practice area, a pricing estimate based on the work involved, and public pricing context presented with its source and limitations.
