Pevedy
Start free
Pevedy
Start freeLog in

Detect · Match · Prove · Act

From documents to verified actions.
Automatically.

Something happens. Pevedy finds the documents that matter, checks the evidence behind them against your sources, shows what is still missing, and prepares the next action for you to approve.

Start freeHow it works
  • Source-backed
  • Human approval
  • Missing evidence
  • Traceable states

Every conclusion is traceable to the document it came from. You approve the action.

Demo scenarioNot customer data

Water damage reported at home — 14 March

2 of 3requirements met

  • VerifiedContents insurance policyClause 4.2 covers this kind of damage
  • VerifiedRepair invoiceAmount matches the reported damage
  • MissingPhoto of the damaged itemNeeded before the claim is complete

Next actionPrepare the claim for your review

An illustration of Pevedy's output on an invented example. Not customer data.

The mechanism

One event. Every document it touches.

This is the whole of Pevedy in one frame: what happened, the documents that turn out to matter, the evidence they establish, the piece that is still missing, and the action that follows once it is there.

  • Evidence, not inferenceEvery line in the frame points at a document and the place inside it.
  • The gap is namedWhat no document establishes is listed rather than smoothed over.
  • A person decidesThe action is prepared and waits for approval. Nothing is sent.
Demo scenarioNot customer data
Event

Flight LH441 cancelled

Reported 14 March · Munich to Lisbon

Matched documents

  • Booking confirmationFare conditions

  • Cancellation noticeCarrier statement

  • Travel insurance policy§7.2 Delay and cancellation

Proof

4 of 5 verified

Each one traced to the document it came from.

Missing: Taxi receiptThe one requirement no document in the Vault establishes yet.

Potential recovery

€842

What the matched documents entitle this scenario to claim.

Next step

Add receipt

Add the receipt, and Pevedy prepares the claim for a person to approve.

An invented example, drawn the way Pevedy draws a real one. Not customer data.

One core, two paths

The same evidence-driven core, for a person or an operation.

Pevedy does not change shape depending on who is asking. The same loop — what happened, the documents it touches, the evidence behind them, what is missing — runs for a cancelled flight and for a queue of cases.

What Pevedy does today

For individuals

Personal situations where the answer is already sitting in documents you have.

  • Travel disruptionBookings, fare conditions and cancellation notices.
  • InsurancePolicies, cover limits and the paperwork a claim asks for.
  • Contracts and subscriptionsTerms, notice periods and what a renewal actually commits you to.
  • Bills and statementsInvoices and charges, read against the agreement behind them.
  • EmploymentContracts, payslips and the documents attached to them.
  • Property and homeTenancy and service agreements, and what they say when something breaks.

Where the same core is heading

For businesses

Document-heavy work of the same shape, at more than one case at a time.

  • Claims operationsThe same event-to-evidence path, repeated across a queue.
  • Compliance and review workflowsConclusions that have to be traceable to a source to be worth anything.
  • Evidence-backed case handlingA case file where what is missing is as visible as what is proven.
  • Operational decision supportA person deciding, with the documents behind the decision attached.

There is no separate business product today — no business tier, no enterprise edition and no separate pricing. This is the direction the same core is built for, stated plainly so it is not read as a shipped offering.

Both paths run the loop in the frame above. What changes is the documents you bring to it.

How it works

Four steps, and you decide the last one.

The same sequence runs behind every case Pevedy handles. Nothing skips a step, and nothing past the third one happens without you.

  1. Detect

    Something happens, or you give Pevedy the context.

    A cancelled flight, damage at home, a renewal date coming up. Pevedy starts from the event rather than from a folder you have to organise first.

  2. Match

    The documents that bear on it are connected.

    Pevedy finds the ones that matter and reads where in each of them the answer sits — the clause, the fare condition, the line on the invoice.

  3. Prove

    Evidence is checked, and what is missing becomes visible.

    Every conclusion is traced back to the document it came from. Anything Pevedy cannot establish is named as missing rather than smoothed over.

  4. Act

    Pevedy prepares the next action. You approve it.

    The action is drafted with its evidence attached and waits for your decision. Nothing is sent, filed or committed on your behalf.

Pevedy prepares it. You approve it.Approval is a person's, every time. Pevedy has no authority to act for you, and the landing page will not claim one before the product has it.

Start with one document.

Add something you already have — a policy, a contract, a booking — and tell Pevedy what happened. It reads the document, not your intentions.

Start free

Why it can be trusted

Every conclusion carries the document it came from.

Pevedy does not ask to be believed. It shows the source behind each conclusion, names what it could not establish, and leaves the decision with you.

Source-backed conclusions

A conclusion is shown with the document and the place inside it that supports it. Nothing is asserted from nowhere.

Covered

TravelShield PolicyPage 17

Human approval

Pevedy prepares the next action and stops. You read it, with its evidence attached, and decide whether it happens.

Waiting for you

Prepared claimNot sent

Clear missing evidence

What Pevedy cannot establish is named as missing and stays visible until it is resolved. A gap is never rounded up into a conclusion.

Missing

Taxi receiptNo document establishes it

Traceable state

Every step Pevedy takes is recorded — what it read, what it concluded and when — so the state you see can be explained after the fact.

Recorded

Activity trailEvery state change

Those four lines are how Pevedy writes a state. In the product, the source opens the page it came from; here they are illustrations, not customer data.

Where it applies

Six situations, one mechanism.

The same loop, pointed at whatever happened. Each of these is a document you already have and a question you would otherwise answer by reading it twice.

  • Travel disruption

    A flight is cancelled and the airline offers a voucher.

    Pevedy reads the fare conditions and the policy, and shows what you can claim.

  • Insurance claims

    Something is damaged and the policy runs to forty pages.

    The clauses that apply are matched, and the paperwork still missing is named.

  • Contract obligations

    A contract renews automatically unless somebody notices in time.

    The notice period and what it commits you to are read out of the document.

  • Subscriptions and bills

    A charge appears that does not match what was agreed.

    The invoice is read against the agreement behind it, line by line.

  • Employment documents

    A contract, a payslip and an addendum that do not obviously agree.

    Pevedy connects them and shows which document settles the question.

  • Property and home

    Something breaks and the tenancy or service agreement decides who pays.

    The clause that answers it is found and shown with its page.

Put your documents to work.

Free to start. You keep the decision at every step, and every conclusion shows the document it came from.

Start free