The official record
Kenyan legislation and official notices land in the Kenya Gazette. It is a natural anchor for a Kenyan watchlist.
Proactive intelligence / standing brief / Kenya
Standing intelligence briefs for teams in Kenya: a watchlist built around the sources that actually change the work, the Kenya Gazette, National Assembly legislative tracks, ODPC guidance, CBK notices, KRA updates, and CMA circulars. The agent checks approved sources and delivers a short brief with evidence.
Example intelligence / fictional watchlist
Why it matters here
The Kenya Gazette, the National Assembly, the ODPC, CBK, KRA, and CMA are the local frame the watchlist is built around.
Kenyan legislation and official notices land in the Kenya Gazette. It is a natural anchor for a Kenyan watchlist.
ODPC guidance, decisions, and registration updates are monitored from the official source, with timestamps in the brief.
CBK notices, KRA updates, and CMA circulars are monitored when they affect the team's work.
What arrives
Companies, funds, cases, competitors, permits, regulations, products, markets, or keywords — in the local source set.
Deduplicate updates, compare against prior context, and surface only material changes.
A short brief with source links, timestamps, uncertainty, and a clear next question.
The premium setup
One role, one watchlist, three to five source families, scheduled delivery, citations, and tuning.
Continuous source checks, relevance tuning, failure alerts, evaluation, and output maintenance. Client subscriptions stay in client accounts.
How the system works
The entities, topics, locations, or risks that matter, and what counts as material.
Public sources are monitored directly. Private feeds use read-only client-approved access.
The workflow collects, deduplicates, compares, cites, and summarizes the changes.
Your corrections tune relevance. The system records misses, false alarms, and stale sources.
Why trust Pristine3D?
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.
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
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
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One workflow for a small team, with training and handover.
See the one-workflow packageMultiple sources, roles, integrations, and admin handover.
See the deploymentStandard 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
Public sources directly, and private feeds through read-only, client-approved access. Pristine3D does not own your subscriptions.
Material changes from the approved source set, for example Gazette notices, National Assembly tracks, ODPC guidance, CBK notices, KRA updates, or CMA circulars, each with the source and timestamp.
The default is af-south-1 (Cape Town), documented in the architecture. Fully local deployment is available.
Yes, setup from KES 470,000 with the USD floor unchanged.
Own your knowledge base
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.
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Start with the watchlist
Tell us the person, watchlist, source types, and delivery time. We will tell you whether a brief is worth building.