Introducing venpor & Venny
VENNY ARCHITECTURE
Three layers that let Venny execute safely.
Venny is not just a model with a chat box. It is an operating system of connected layers: one layer connects to the systems where work happens, one layer tests behaviour, and one layer carries programme context forward.
CONNECT
Adaptive Integration Layer
Connects Venny to ATS, HRIS, ERP, payroll, supplier, contract, compliance, and payment systems without forcing one rigid data shape.
TEST
Venny Eval Engine
Tests Venny against realistic workforce scenarios before deployment and during production, so reliability is measured instead of assumed.
REMEMBER
Venny Memory
Maintains programme context across workers, suppliers, workflows, approvals, exceptions, and history so Venny does not start from zero each time.
ADAPTIVE INTEGRATION LAYER
Venny works where the workforce work already happens.
The Adaptive Integration Layer connects Venny to the systems that already hold your workforce operation: requisitions, worker records, approvals, contracts, suppliers, compliance evidence, invoices, and payments.
Instead of forcing a long replacement programme, Venny reads the state of work across the stack, understands what changed, and writes governed actions back to the right system.
⇄
Bidirectional by design. Venny does not only observe work. When an approved action is taken, the update is written back to the relevant system with the right context and audit trail.
DEMAND
Requisitions and roles
Open roles, hiring requirements, submissions, shortlists, and approval status.
WORKERS
Worker records
Skills, status, onboarding progress, compliance records, and engagement history.
FINANCE
Spend and cost centres
Budgets, purchase orders, cost allocation, approvals, and payment context.
PAYMENTS
Invoices and payment runs
Timesheets, approvals, supplier invoices, exceptions, currency, and payment status.
SUPPLIERS
Supplier systems
Supplier submissions, response times, rate compliance, contract terms, and performance history.
COMPLIANCE
Risk and evidence
Classification, work authorisation, insurance, audit trails, expiry dates, and country rules.
VENNY EVAL ENGINE
Good AI is not trusted. It is tested.
The Eval Engine tests Venny against realistic workforce scenarios before deployment and during production. It checks whether Venny followed policy, used the right context, handled the edge case, and stayed within the intended authority.
The goal is simple: Venny’s behaviour should be measurable, reviewable, and improvable before your team relies on it in live programme work.
Pre-live
Scenario testing before rollout
Live
Checks during production
Custom
Programme-specific edge cases
WORKFORCE SCENARIOS
Policy checks
Onboarding blocked by missing right-to-work evidence
onboarding
Contract amendment conflicts with approved rate card
contracts
Supplier asks to submit outside approved country scope
supplier
SOW milestone is approved but invoice exceeds tracked labour value
SOW
Payment exception requires finance review before release
finance
Venny Memory
Venny doesn't start from scratch.
Venny maintains a persistent record of your programme across three layers. This is what makes its assessments accurate and its sourcing intelligence meaningful: Venny knows what your programme looks like, who has worked well before, and which suppliers have delivered.
◎
Worker profiles
Skills, compliance status, and past performance retained across engagements. When a new position opens, Venny's talent pool search draws on this history. No re-running searches, no starting from scratch.
◈
Supplier history
Fill rates, time-to-submit, rate compliance, and submission quality tracked per supplier across every requisition. Smart routing decisions are grounded in this accumulated record, not generic rules.
◇
Programme baseline
What normal looks like for your specific programme. Spend patterns, approval rhythms, typical onboarding timelines. Anomaly detection is calibrated to your context, not a generic threshold.
Why memory matters
A generic AI tool treats every session as fresh. It has no knowledge of who worked on your last project, whether a supplier consistently delivers late, or what a normal spend burn rate looks like for your team.
Venny Memory is what separates programme intelligence from a search bar. The longer Venny runs, the more accurate its assessments become, because they're grounded in the specific history of your operation.
Memory in action
Sophie van den Berg — last engaged Q2. Skills: Ops, Project Management. Compliance current. Performance: exceeds. Available from 15 Aug.
Harlow Staffing Partners — 7 of 9 Engineering roles filled in avg 3.8 days. Rate compliance: 100%. Recommended for next Engineering req.
Programme baseline — typical onboarding: 4.2 days. Spend burn avg at T+60: 52%. Current SOW-0041 at 73%. Venny flagged as anomaly.
HOW VENNY COMPARES
A chatbot answers. Venny operates.
Generic AI assistant
Answers detached from workforce systems
Context disappears after the session
Reliability is assumed, not tested
Actions still require manual follow-up
Governance sits outside the AI layer
Venny inside venpor
Connected to the systems where work happens
Grounded in programme memory and knowledge
Tested against realistic workforce scenarios
Executes governed actions with audit context
Your team supervises every sensitive step
FAQ