Praxis Ab Machina

S-02 · Sales

The price you agreed
is in an email thread
nobody can find.

Discounts, payment terms and liability caps are approved in Outlook and Teams, then signed as PDFs. At renewal, at audit, or in a dispute, nobody can reconstruct who agreed what.

01 · The problem

Your CRM knows the stage. It does not know the terms.

The document that reaches the signature envelope is not always the version finance and legal approved. Last year’s exception quietly becomes this year’s baseline, and the customer quotes it back to you.

02 · The work

What the week is actually made of.

  • Chasing discount, payment-term and liability-cap approvals through threads that carry no link to a quote version.
  • Rebuilding the tender administrative pack for the tenth time — ΤΕΥΔ, φορολογική and ασφαλιστική ενημερότητα, ΓΕΜΗ extract, εγγυητική επιστολή — against a portal deadline.
  • Renewal notice windows and indexation clauses sitting in executed PDFs nobody has opened since signature, so the uplift the contract entitles you to is never invoiced.
  • Meeting notes that never reach the CRM, so the pipeline reflects what was easy to type rather than what was said.
  • Checking a new customer by hand — VIES, ΓΕΜΗ, the credit insurer’s limit — while a truck slot is being held.

03 · What we build

What the work looks like here.

  1. A-001 Workflow automation An approval trail: every exception tied to the quote version it belongs to and to the person who granted it. lead time 2–6 weeks
  2. B-002 Custom AI agents A reader for your own executed contracts — notice windows, indexation, surcharges never billed — that reports and does not decide. lead time 3–8 weeks
  3. C-003 Bespoke integrations Quote, contract and CRM holding one version of the commercial terms. lead time 1–4 weeks

04 · Delivered

90h

returned every month · KRV² · Athens

KRV² bids for large-scale solar and MEP work, which means somebody has to read every public tender the moment it is published. An agent built on Claude now retrieves them, scores each one against KRV²’s own bid criteria, writes the findings into an HTML dashboard, and tells the people who decide — bid, or walk away. The engineer who used to do that reading has about ninety hours a month back.

Built on Claude · Anthropic

05 · Where it stops

Where it stops.

  • The price. The system assembles the case for an exception; a person still grants it.
  • Anything a customer will read as a commitment. Drafted for a person to send, never sent unseen.
  • The credit decision on a new account. It gathers the evidence; the limit is yours to set.

06 · Governance

A commitment is binding whether or not a machine drafted it.

Everything customer-facing is drafted for a person to send. Recorded calls are a specific limit: they may be transcribed to produce a summary, and never scored for emotion or used to rank the person on the call.

07 · Next

Start with the approval trail. It is the one nobody can reconstruct.