Choose the corpus
Start with policies, contracts, manuals, or records the team searches every week.
Retrieval / small team deployment
Small teams do not need a platform. They need one source that answers.
We deploy retrieval-augmented generation around one approved document source, with a client-owned index, source citations, access rules, and a runbook the team can operate. The setup is sized to the workflow, not to an enterprise roadmap.
One source firstClient-owned indexSource citationsRunbook handover
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
What a small team RAG deployment needs
The useful parts are operational, not architectural.
The first deployment should answer real questions from real documents and leave the team with someone who can operate it.
Answer with evidence
Retrieval feeds the model and citations attach the source to every answer.
Hand over the run
Training, the runbook, access rules, and a named owner make it sustainable.
The small team boundary
Small does not mean less careful.
One workflow at a time
A first project covers one source, one interface, and up to 10 users.
Permissions are explicit
Who can see which documents and answers is agreed before sensitive material enters.
Human review stays final
High-stakes outputs keep a named reviewer and approval step.
A first small team RAG project
Deliver one useful answer, then expand.
Pick the source
Name the documents, owners, users, and the questions they keep asking.
Build the index
Configure retrieval, metadata, permissions, and refresh rules.
Test with the team
Run real questions, review citations, and fix gaps.
Train and hand over
Deliver the runbook, train users, and transfer client-owned accounts.
A small team does not need to manage RAG. It needs to trust the answers.
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.
Do we need an IT department?
No. The first deployment is scoped for a named operator, with training and a runbook included.
How many documents can it handle?
The index is sized to the source and question set. We start with the documents that matter most.
What happens after handover?
The team owns accounts and daily operation. Annual support can cover monitoring and updates.
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 source
Which document set should answer questions first?
Tell us the source, users, and questions. We will scope the first RAG deployment around the smallest useful setup.