Assemble the customer record
Collect identity, legal status, ownership, beneficial owner, and contact data from approved sources.
Compliance workflow / KYC and CDD files
KYC files should be ready before the question is asked.
We build private workflows that assemble customer profiles, ownership records, identity documents, screening notes, and risk context into a reviewable CDD file. The workflow prepares evidence; the compliance owner and the institution decide what is sufficient.
Customer profileEvidence fileRisk contextCompliance review
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where CDD preparation loses time
The customer is the same. The file starts over.
The recurring work is pulling identity, ownership, source, transaction, and risk records into one current file without losing the decision trail.
Connect the supporting files
Attach documents, verification records, screening outputs, and prior reviews with dates and versions.
Make gaps visible
Surface missing, expired, or uncertain evidence and the risk or review question for the compliance owner.
The CDD boundary
The system prepares the file. It does not approve the customer.
The compliance owner validates
The workflow flags gaps and prepares drafts. The institution and its responsible officer decide whether a file is complete.
No automatic conclusion
Screening hits and risk indicators are presented for review, never converted into a final approval or decline.
Use current requirements
The applicable KYC, AML, and privacy rules are confirmed against the current official text before a file enters.
A first CDD workflow
Start with one customer segment and one file type.
Choose the segment
Pick individual, corporate, partnership, or another customer type with a known evidence list.
Define the file
List the identity, ownership, verification, screening, and risk fields the team needs.
Run a completeness check
Compare current evidence against the defined file and review missing, expired, or uncertain items.
Hand over the review
Deliver the assembled file, flags, and open questions to the responsible compliance owner.
A CDD file is easier to defend when the customer, evidence, and review question stay together.
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 decide whether a customer is approved?
No. It assembles and checks evidence. Approval, decline, and enhanced-review decisions stay with the institution and its compliance owner.
Can it search external watchlists?
Screening is a separate scoped step with an approved source and review process. The workflow does not turn a hit into a conclusion.
How is this different from the CBN AML/CFT page?
That page covers Nigeria-specific CBN returns and evidence. This page is the general customer file workflow: KYC and CDD preparation for any team.
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 segment
Which customer file takes the longest to assemble?
Tell us the customer type, the evidence list, and the review owner. We will scope the first workflow around the records you already trust.