Answer from the current policy
Search leave, expenses, remote work, benefits, and approval rules in the approved handbook and policy set.
HR workflow / handbook and policy questions
The handbook is the answer. Nobody can find the page.
We deploy private workflows that answer staff questions about leave, expenses, remote work, and approvals from the company's own handbook and policy records. HR keeps the decision, the exception, and the final answer.
Policy lookupLeave questionsExpense rulesApproved exceptions
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where handbook time goes
The question is repeated more often than the policy changes.
Each staff member needs the same answer, and each HR person spends the same minutes finding the current version and checking whether an exception applies.
Show the supporting rule
Return the policy section, the effective version, and the next owner for questions or exceptions.
Route the exception
Prepare the request summary and the open question for HR when the handbook does not decide it.
The HR boundary
The system finds the policy. HR owns the answer.
Use the approved version
The current handbook, policies, and update history remain connected to every answer and citation.
No automatic approvals
Leave, expense, and policy exceptions stay with HR or the manager who holds the authority.
Staff records stay scoped
Personnel files, pay, and sensitive case notes remain in separate permission groups where required.
A first handbook workflow
Start with the questions staff actually ask.
Collect the question set
Gather leave, expense, remote work, benefits, and approval questions from the team's real requests.
Load the approved policies
Use the current handbook, policy documents, and the update history the HR team owns.
Test with real staff questions
Run the workflow against actual requests and review citations, exceptions, and unclear answers.
Hand over the review route
Document the policy owner, escalation path, and the HR person responsible for exceptions.
Staff do not need faster AI. They need the same answer they would get from HR, found faster.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Can it approve leave or expenses?
No. It answers from policy and prepares the request summary. Approvals stay with HR or the manager with authority.
Can it keep personnel records private?
Yes, when scoped. Staff questions can be answered from policies without exposing personnel or pay records.
How is this different from the HR teams page?
That page covers the HR function's broader workflows. This page is one specific workflow: policy questions answered from the employee handbook.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the question set
Which handbook questions keep returning?
Tell us the policies, the question set, and the escalation owner. We will scope a workflow around the handbook your team already uses.