Upload. Describe. Deploy.

Your process, as a service.

Upload the documents that describe how your work gets done. Show us a few examples of input and output. Tell us — in plain language — how one becomes the other. We take it from there.

Request early access See how it works

No code required Auditable by construction EU-resident hosting available

How it works

Four steps. No code. No prompt engineering.

You bring the knowledge of how your work gets done. We take care of turning that into a running service.

Documents and references

Upload

Drop in the SOPs, policies, templates, sample emails, or whichever files describe how the work gets done today. We read them.

Inputs and outputs

Show examples

Provide a handful of real inputs and the outputs you would expect for each. Five or six is usually plenty. If you can't show examples, describe what good output looks like instead.

How input becomes output

Describe

Write the rules in your own words. "If the invoice is over €10,000 send it for review." "If the supplier is new, request a tax ID." Plain English. As detailed as you want.

A working service

Deploy

We turn your process into a running service with an API endpoint or webhook. Every decision is logged with a signed audit trail. Iterate, refine, version — without touching code.

Built to run anywhere

Fast, auditable, and yours to keep. Abstractor handles the infrastructure so your team can focus on the process logic.

The spec is yours

Your process description and your examples belong to you. Export them as a portable document any time — leave Abstractor without rewriting your rules.

Fast where it matters

Decisions return in well under a second. Predictable latency for production workloads — no cold starts, no surprises.

Show, don't tell

Have examples but no formal rules? Provide a handful of inputs and the outcomes you expect — Abstractor infers the rules and validates them against your examples before going live.

Quality gates

Every change has to pass the examples you provided. If a new rule breaks an old example, the deployment is blocked automatically. No silent regressions.

Auditable by construction

Every decision the service makes is recorded as an exportable audit record. You can show exactly what was considered and why — for one decision or a year of them.

Your region, your rules

Deploy where you operate. EU-resident hosting is the default for EU customers; other regions on request. Compliance tooling for the EU AI Act, GDPR, and similar is included where it applies.

Workflows

Real processes, ready to model.

Six concrete workflows that fit the upload-show-describe model. Pick the closest to your own to see what we'd ask for.

Finance

Supplier invoice approval

Upload: Approval policy PDF · supplier whitelist · VAT verification rules
Show examples: Twelve past invoices, each with the approval decision (approved / flagged / rejected) and the reason.
Describe: If the supplier is on the whitelist and the amount is under €10,000, approve. If the VAT number is missing or invalid, flag for review. If the supplier is new, request a tax ID. Above €50,000 always route to the CFO.
Output: Decision (approved / review / rejected) with a one-line reason, returned to your AP system.

Customer success

Support ticket triage

Upload: Team responsibility matrix · escalation policy · past resolved tickets export (CSV)
Show examples: Twenty closed tickets, each with the team that owned it and the priority assigned.
Describe: Route based on subject keywords and customer tier. Tier-1 customers always get within-1-hour priority. If the customer mentions 'billing' route to Finance. If it mentions 'security' or 'breach' escalate immediately.
Output: Team assignment + priority level, posted to your ticketing system as a comment or automation.

Sales

Inbound lead qualification

Upload: Ideal customer profile (ICP) document · sales-team playbook · sample qualified vs disqualified leads
Show examples: Thirty contact-form submissions, half qualified and assigned to a rep, half disqualified.
Describe: Score on company size, industry fit, role seniority, and budget signals. Discard obvious spam. If the company is in our ICP and the role is decision-maker, route to the AE pool. If borderline, route to SDR review.
Output: Lead score 0–100 + routing decision (AE / SDR / drop), with the reason. Posted to your CRM.

Operations

Outbound communication compliance

Upload: Corporate communication guidelines · regulated-claims list · brand-voice document
Show examples: Forty draft emails, half approved as-is, half flagged for specific reasons.
Describe: Reject anything that promises guaranteed returns or makes uncited statistical claims. Flag anything that mentions a competitor by name. Approve if the tone matches the brand voice and no compliance triggers are hit.
Output: Approve / flag / reject decision with the specific clause that triggered the result.

HR & expenses

Expense report compliance

Upload: Travel and expense policy · approved-vendor list · per-diem reference
Show examples: Twenty-five expense reports, each with the original lines, the lines flagged, and the auditor's reasoning.
Describe: Per-diem limits apply by city tier. Alcohol is reimbursable only on client-entertainment lines. Receipts over €75 are mandatory. Anything from a non-approved vendor is flagged.
Output: Per-line decision (ok / flag / reject) with the policy reference. Returned to the expense tool.

Document operations

Inbound document classification

Upload: Document taxonomy · sample documents per category (PDF, DOCX, scanned)
Show examples: Fifty documents already filed under the right category.
Describe: Classify by document type (invoice, contract, NDA, RFP, technical drawing, …). Extract the counterparty and date. Route to the right folder in your DMS.
Output: Category label, extracted metadata, and destination path.

Your process not on this list? It probably still fits.

Email us what you'd want to automate

Audit & compliance

Every decision, on the record.

Every decision your service makes is recorded, with the inputs and the rationale kept alongside it. Useful in any jurisdiction; required in some. We make it the default.

An example receipt

Each decision your process makes is captured in a self-contained signed record. It can be stored, forwarded, and verified by anyone with the public key — your auditor, a regulator, your customer — without going through us.

{
  "receipt_id": "rcpt_01HX7KQMN2P3QR4ST5UV6WX7Y",
  "process":    "invoice-approval@v3",
  "ts":         "2026-05-24T09:12:33.112Z",
  "input_hash": "sha256:e3b0c44298fc1c149afb...",
  "decision":   "approved",
  "rationale":  "Amount 450 EUR below threshold; known supplier; VAT validated",
  "sig":        "ed25519:3a9f2c8d4b1e6a0f7c3d...",
  "pubkey_id":  "eu-1"
}

Cryptographic integrity

Ed25519 signatures on every receipt

Receipts are signed with Ed25519 keys. Verify any receipt independently using Abstractor's public key registry — no trust required, no platform access needed. Works for everyone, everywhere.

EU residents — AI Act Article 12

Per-invocation audit trail

Article 12 mandates logging for high-risk AI systems. Abstractor delivers a HATP (Hardware Attestation Trust Protocol) receipt on every call automatically — timestamped, signed, and covering inputs, decision, and rationale. No extra integration.

EU residents — GDPR Article 22

Explainable automated decisions

Where your actor makes automated decisions about individuals, GDPR Article 22 requires explainability. HATP receipts include a structured rationale field — the explanation trail your legal team needs, ready out of the box.