From your documents to a working service
Four steps. Days, not months. Every decision your service makes is recorded as an exportable audit record.
Tell us how the work gets done today
Hand us the materials your team already uses. Standard operating procedures, policies, sample emails, CSV exports, templates, training decks. Whatever you'd give a new hire on day one.
-
Policy & SOP documentsPDF, Word, or plain text — the rules your team follows today. -
Sample data exportsCSVs, spreadsheets, JSON dumps — examples of what you process. -
Email templatesHow you currently communicate decisions or approvals. -
Anything elseIf a new hire would need to read it, we want to read it too.
No file you send leaves the EU. EU-resident storage by default.
Show what good output looks like
Five or six concrete examples are enough. Each one is an input you might see, paired with the output you'd want. A sentence on why this example matters.
Examples cover the obvious case, the obvious-rejection case, the edge cases that bite you in production. You already have these examples; they're sitting in last quarter's tickets.
If you can't show examples, describe them in prose. We can work with either.
Explain in your own words
Plain English rules. As detailed or as loose as you want. The rules can be conditions ("approve if amount under €1,000 and supplier is known"), policies ("never approve without a VAT number"), or escalation paths ("anything above €10,000 always goes to manual review").
Write the rules as if you were briefing a new team member. We turn the briefing into an operational service.
If a rule changes, you change the rule and redeploy. No code review. No engineering ticket. The previous version stays available for audit comparison.
Approve invoices under €1,000 from known suppliers automatically. Flag invoices over €10,000 for manual review regardless of supplier. Reject invoices with missing VAT number. If the supplier is on the watchlist, always escalate.
- Endpoint — https://run.abstractor.io/p/<your-id>/invoices
- Web review UI — for humans to inspect flagged items
- Audit feed — every decision, with a signed audit record
- Export — the full rules and history, yours to take with you
Receive a working service
You get a live endpoint, a web review UI for human-in-the-loop decisions where needed, and a continuous audit feed. Plug the endpoint into your existing systems (AP, CRM, ticket router) and the work starts flowing through it.
Days from first upload to first production decision. Iteration on the rules is the same loop — describe, examples, redeploy — with the previous version available for comparison.
Audit-ready, exportable, yours
Three properties of every service you deploy on Abstractor — non-negotiable, in scope by default, no compliance project required later.
Audit by default
Every decision your service makes is recorded as an exportable audit record — including the inputs, the output, and the rationale. Retention is configurable per process.
Your process is portable
The rules, examples, and decision history export to a portable format at any time. No vendor lock-in. If you stop using us, the audit record remains independently verifiable.
Revisions are versioned
When you change the rules, the previous version stays accessible. You can replay any past decision against the new rules to see what would have changed. Reviewers see exactly what shipped, when.
Frequently asked
How long does it take from upload to a live service?
Days, not months. A first version is usually deployable within the same week as the first upload; iterations after that take hours.
Where does my data live?
EU-resident by default. Other regions are available on request. No data ever leaves the region you choose without an explicit decision on your side.
What happens if a rule is ambiguous?
We flag the ambiguity back to you before going live. You can clarify in plain language, add an example, or accept the default behaviour. The service never silently guesses.
Can humans still review decisions?
Yes — the web review UI is built in. Any decision your rules flag for manual review lands in a queue with the inputs, the rationale, and a one-click approve/reject. The decision goes back into the audit feed.
Is this compliant with EU AI Act and GDPR?
The audit-by-default property is built specifically for EU AI Act Article 12 (record-keeping) and GDPR Article 22 (automated decisions). Compliance is a side-effect of the architecture, not a separate workstream.
What if I want to leave?
Export the full rules, examples, and audit history at any time. The exported format is open and independently parseable. The audit records remain verifiable even after your subscription ends.