Gather the standing material
Pull prior minutes, decisions, action status, financials, and submissions from approved files.
Board administration / pack assembly and minutes
Board work is not the strategy, it is the pack around it.
We build private workflows that collect prior minutes, decisions, open actions, financial updates, and submissions into a draft board pack, then prepare minutes or action lists from approved notes.
Prior minutesOpen actionsFinancial updatesDraft pack
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where board administration goes
The pack repeats more than the strategy.
Each meeting needs the same assembly: what was decided, what is open, what changed, and what needs a decision.
Trace the open loop
Show each open action, its owner, the last update, and the follow-up due before the meeting.
Prepare the pack and minutes
Produce a draft agenda pack and a minutes skeleton for the company secretary or chair to review.
The board boundary
The system assembles. The board and secretary decide.
Use approved records
Minutes, resolutions, financials, and submissions remain attached to the pack that uses them.
Secretary review is built in
The draft pack and minutes are prepared for the company secretary, chair, or responsible officer.
Corporate filings stay human
The workflow does not file statutory documents or certify minutes without an explicit human action.
A first board workflow
Automate the assembly, not the decision.
Choose the meeting cycle
Pick the standing board or committee pack with a known calendar and file structure.
Map the standing sections
Define minutes, actions, financials, reports, and submissions that belong in every pack.
Test against the last cycle
Compare the prepared pack with what the secretary actually sent and fix missing or stale items.
Hand over the review step
Document the sources, ownership, and final review before the pack is distributed.
A board pack should make decisions visible, not make the secretary invisible.
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 produce official minutes?
It can prepare a minutes skeleton from approved notes. The secretary, chair, or board confirms accuracy and approves the record.
Can it access our board files?
Yes, through scoped client-owned storage with permissions reviewed before sensitive board material enters.
How is this different from meeting transcription?
That page covers turning a recording into action items. This page covers the recurring board pack: minutes, decisions, actions, and submissions.
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 meeting cycle
Which board pack takes the most assembly?
Tell us the standing sections, the source files, and the review owner. We will scope the first pack around what the board already needs.