Document the AI use
Record the system, provider, purpose, data, users, outputs, and human review for each business use.
Compliance / EU AI Act preparation
The EU AI Act is risk based and most uses are not high risk.
We build private workflows that help teams map the AI they use, the role they play, the likely risk tier, and the documentation that supports their position. The workflow prepares records; the client and its advisers make the legal call.
Role mapRisk tierDocumentationReview pack
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where AI Act preparation loses time
The obligation depends on the actual use.
The useful starting point is a record of the system, the provider, the purpose, the data, and the humans who decide.
Prepare the risk view
Organize the information advisers need to assess risk tier, role, and applicable obligations.
Keep the review pack current
Maintain documentation, logs, update records, and open questions for the responsible owner.
The EU AI Act boundary
The system prepares records. It does not declare compliance.
Provider and deployer differ
The workflow records the facts. Advisers determine the role and obligations under the current regulation.
Obligations apply on different dates
Timelines depend on risk tier and role. The current official text is confirmed before any page or workflow is trusted.
No automatic certification
The workflow does not certify, register, or conclude compliance. Legal and regulatory sign-off remain with the client.
A first AI Act workflow
Start with the systems the team actually uses.
List the AI uses
Record the tools, providers, purposes, data, users, and outputs in scope.
Assemble the record
Collect documentation, logs, policies, and review notes for each use.
Prepare the risk view
Organize the facts advisers need to assess risk tier, role, and next steps.
Hand over the review pack
Deliver the current record and open questions to the responsible owner and advisers.
AI Act preparation is easier when every system has a record and every record has an owner.
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.
Does this certify our AI Act compliance?
No. It prepares the record and review pack. The legal assessment and any certification remain with the client and its advisers.
Does the EU AI Act apply to us?
It depends on the system, role, risk tier, and current official text. The workflow organizes the facts; the legal call stays professional.
What is a good first workflow?
One AI inventory record with the system, provider, purpose, data, users, and review owner.
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 inventory
Which AI systems should become a documented record?
Tell us the systems, the data, the users, and the responsible owner. We will scope the first record around what your team already uses.