ProCheck
AI does the work. Your rules decide how.
ProCheck is a platform for putting AI agents to work inside business processes. The agent is called ProAgent: it researches, browses, drafts and delivers finished work. Who may submit, who the counterparty is, which step needs a signature and when it must stop are set by your rules, and every step it takes is on record.
Book a ConsultHow a case moves
Procurement, reconciliation and order review have little in common, yet a case takes the same path through ProCheck. The rules are not notes beside the path. They are the points on it where a case actually stops.
A procurement comparison, step by step
- 01IntakeA colleague fills in a purchase request: item, quantity, budget. A case is opened.
- 02EligibilityThe system checks that this person may raise this kind of request, then uses department and amount to work out who will have to sign.
- 03ProAgent worksProAgent visits two retailers, checks stock and price, and writes up a comparison with a recommendation. The pages it saw and the reasoning behind each step stay in the case.
- 04Sign-offThe draft lands in the right manager's queue. They see the comparison and the evidence, and can approve, return it or ask for rework. ProAgent can submit for sign-off; it cannot decide for anyone.
- 05Execute and closeNothing is executed until it is approved. Who submitted, what ProAgent did and who decided when remain on the timeline afterwards.
What the rules stop
Most automation tools talk about what AI can do. Business processes care about something else: when it must not. In ProCheck those are settings, not hopes written into a prompt.
- A blacklisted sender never starts an agent
- Cases arriving by email or LINE are matched against known counterparties first. A blacklisted party is blocked with the reason recorded, and ProAgent never begins. A party on the watch list is let through, with a flag attached.
- Requesters cannot approve their own case
- Where a step needs a person, ProAgent can only send it for sign-off. The person who raised the request cannot approve it, and every return and rework stays on the timeline.
- One action stops everything
- When something looks wrong, a single action halts all work in progress, including model calls, sub-workflows and remote execution. Stopped work does not resume by itself.
Processes already running
Each of these has been delivered on ProCheck. The work differs; the rules are the same set.
What IT and compliance will ask
- Deployment
- The whole system runs in your data centre or private cloud under an offline licence. It does not need to reach any cloud service to operate.
- Identity and access
- Sign-in through SSO (OIDC). Department, title and cost centre come from directory sync and can be used directly in sign-off rules.
- Audit
- Every administrative action is written to a hash-chained audit log that can be verified offline and streamed to a SIEM.
- Models
- OpenAI, Anthropic, Bedrock, Vertex, Ollama and vLLM are all supported, and different roles can be given different models.
- Cost
- Every model call is metered and reported by currency. Each run can carry a limit on spend, time and tokens.
- Where work runs
- Remote runners execute the work on machines you designate.
How to start
ProCheck arrives with our delivery service; there is no self-serve sign-up. A forward deployed engineer (FDE) joins your team, starts from one real process, and sets up the rules, the ProAgent and the sign-off until it is ready to go live.
Along the way your IT department learns to deploy and operate it, and your business units learn to write their own rules and adjust ProAgent. When the engagement ends, the process is yours.