AI Governance as a Service

There is no list price, because the work scales with what there is to govern. Cost is scoped against the number of AI use cases and vendors in scope, whether governance covers one function or the whole organisation, the cadence the forum runs at and how much of the register, reporting and review work Namandla carries rather than your own team. Scoping produces a firm figure before any work begins. Contact info@namandla.com or call 087 188 3388.

An average is not a useful guide here. An organisation governing three AI use cases inside one finance function and a group governing thirty across several business units are buying quite different services, so a benchmark figure tends to mislead. Compare scoped quotes on what each one includes: which registers are maintained, who prepares the forum packs, how often the forum sits and what happens when an incident needs handling.

Engagements are scoped rather than sold at a rate per hour. Governance is a standing cadence rather than a fixed quantity of work, so an hourly figure says very little about what a year of it will cost. Where something genuinely is once off, such as a single vendor review or a risk assessment, it is scoped as its own piece of work.

Namandla is based in Boksburg in Gauteng and works with organisations across the province and beyond it. The service is cadence based, meaning forum sessions, reviews and reporting, so it runs comfortably as a mix of on site and remote work depending on what suits your team. What matters more than proximity is whether the cadence fits how your organisation already makes decisions.

It depends what it is measured against. The value sits in decisions made earlier and with better information: which use cases proceed, what a vendor may do with your data and who carries the sign off. Scope is also adjustable. An organisation can begin with the use cases carrying the most exposure and widen coverage as adoption grows, rather than governing everything from the first month.

Usually the better lever is a smaller scope rather than a smaller price. Governing five significant use cases properly is more useful than governing forty superficially. An organisation that already has a working risk committee, an established policy set or an internal owner with capacity can carry more of the cadence itself and buy a narrower service. That is a legitimate way to bring the cost down and it is worth raising during scoping.

Pricing is built from scope rather than from a rate card. Scoping settles three things. What is being governed, meaning the use cases, vendors, data flows and business units. What Namandla operates, meaning intake, review, registers, forum administration, reporting and the escalation path. And the cadence all of it runs at. Those three produce the figure. Work outside the agreed scope, such as a new business unit coming into coverage, is rescoped rather than absorbed quietly.

Scope varies by engagement and typically covers governance administration and the operating cadence, structured intake, review and escalation for new AI use cases and the registers, meeting packs, action tracking and reporting that keep the forum working. Your organisation keeps what cannot be delegated. That means accountability at management, executive and board level. It means formal decision rights and risk acceptance. It means business ownership of AI use cases and outcomes.

Where the figure is higher than expected it is usually scope rather than rate. A service that maintains live registers, runs a real intake and review process, prepares the forum properly and follows actions through to closure carries effort every month. A once off policy document costs less because it is a smaller piece of work. Being clear about which of the two is being bought is what makes two quotes comparable.

Narrow the scope to the use cases that carry genuine exposure and bring the rest in as they mature. Use the governance structures you already have rather than standing up parallel ones. Keep an internal owner who can carry routine administration between sessions. Agree a cadence that matches the pace at which AI use cases actually appear, since a monthly forum is not always necessary. Each of these is a scoping decision and each can be raised before an engagement starts.

Operational elements can be outsourced or co-sourced. Formal accountability and decision authority should remain inside the organisation.

Not necessarily. The answer depends on AI volume, risk and organisational complexity. A managed service can provide capacity while the need evolves.

No. Lower-risk activity should have a faster delegated route, with higher-risk proposals escalated for deeper review.

Update them when material changes occur and support that with a scheduled formal review, typically at least annually.

Review at renewal and whenever material changes affect the product, model, data, subprocessors, contract, agents or incident profile.

It should reduce delays by giving teams a clear, proportionate route to review, decision and approval.

Concise reporting on material decisions, major risks, incidents, important vendors, overdue actions, policy changes and meaningful value observations.

Namandla can prepare, advise and support the forum, but the client should retain formal decision authority.