Precisely? Maybe. Better than guessing.

Scope the work before you price it.

Describe a matter in a few lines. PreciselyMaybe maps the scope, asks only what can change the estimate, models effort and extra-work risk, and adds jurisdiction context when reliable public sources exist.

Your work description is not stored. We may record structured, non-confidential analysis data to improve the beta.

What the output includes

Price Fit

78

70–84 Reasonable fit

Estimated time14 – 22 h
Value per hour545 – 857
Extra-work riskMedium

The flow

  1. 01

    Describe the work

    Up to 300 characters in your own words. Plain language is enough — no documents, no names.

  2. 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.

  3. 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.

  4. 04

    Read the result

    See effort, risk, Price Fit, assumptions and jurisdiction context, with the reasoning kept visible.

Estimated time

An activity-based range, not a single guess.

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.

Percy is still learning how pricing practice varies across markets and jurisdictions.