Skip to content
Pricient by IOanyT

After you sign

The thread does not break at signature.

Requirements are objects from the first conversation onward, so the delivery view is the same document you approved — not a project tool someone re-typed it into.

Example
delivery view traceability
Each requirement's progress from quote to acceptance
Requirement QuotedBuiltTestedAccepted
REQ-001 Patients browse slots ●Quoted: done ●Built: done ●Tested: done ●Accepted: done
REQ-002 Card payment at booking ●Quoted: done ●Built: done ●Tested: done ◐Accepted: in progress
REQ-003 Records system sync ●Quoted: done ◐Built: in progress ○Tested: not started ○Accepted: not started
REQ-004 Admin console ●Quoted: done ○Built: not started ○Tested: not started ○Accepted: not started

Regulated projects require this matrix. It is usually a spreadsheet someone updates by hand.

Traceability

One requirement, end to end

The link from quote line to accepted build never gets re-typed, so it never breaks.

one requirement, end to end

REQ-002 · card payment at booking

  1. Requirement

    REQ-002

  2. Quote line

    itemized

  3. Built

    commit-linked

  4. Tested

    4 of 4 passing

  5. Accepted

    on record → billable

In the normal case the requirement is re-typed into a project tool and the link back to the quote line dies there. Here it does not — which is what makes acceptance, and therefore billing, a record rather than a conversation.

Change requests

Changes are priced before they are made

The same engine that priced the original prices the change — in front of you, before you approve it.

  1. 01

    You ask

    "Add single sign-on."

  2. 02

    It is priced

    The same engine prices the delta — cost and added days.

  3. 03

    You approve

    Before any work starts, not after.

  4. 04

    Addendum signed

    A traceable line, joined to the original quote.

You never discover a change in an invoice. If it was not approved, it was not built.

Status

Status you can act on, not noise

Requirement and milestone status, with a confirmed weekly checkpoint — not a raw feed of every build. A red Tuesday fixed by Wednesday is not news. When something genuinely slips, you get a written explanation rather than a changed colour.

Example
weekly checkpoint confirmed by a person
  • Milestone 1 · Booking flow accepted
  • Milestone 2 · Payments slipped

Why, and what now

The payment provider's test sandbox was down for two days. Card flow is complete; retry logic moves to next week. Milestone 3 is unaffected.

Defined by both lists

Describe your project. See what comes back.

Start your spec

No signature, no call. A business email unlocks the full quote.