The questions operators, boards and risk leaders actually ask.

It joins board governance, risk, finance, pipeline and AI use under one governed operating layer, so leadership teams can evidence what they decided, why, and who approved it.

Every record that enters the platform is provisional until a named person confirms it, and every confirmation is written to an audit trail you can hand to anyone who asks.

No. A board portal typically stores papers, agendas and minutes. Boardverse is a workflow, decision and evidence platform: it enforces who can sign off on what, and produces the artefact that proves it.

No. The platform's AI feature, Ask Poseidon, narrates strictly from the governed record with a source citation on every claim. It does not generate an uncited summary.

Boards, directors, founders, risk, finance and AI leaders in governance-sensitive organisations worldwide, who need AI to be auditable rather than aspirational.

The rule that nothing a connected tool submits to a governance record becomes official until a person who did not submit it says so. The submitter can never confirm their own entry, and the rule is enforced server-side, not hidden in the interface.

A resolution needs a Chair signature and a Founder signature from two different people. If the text changes between the two signatures, the first signature is invalidated automatically, so a signature can never be claimed against text that later changed.

No. Severity is computed server-side, never client-submitted, and recomputed from impact and likelihood on every save. Crossing the organisation's threshold fires an audit-logged escalation to Founder and COO, by email and in-app.

A material variance blocks submission until it is tied to a real board action or resolution. Once approved, a pack is immutable and supersede-only.

Twenty-one, in five groups. Overview: Dashboard and Ask Poseidon. Governance: Board Portal, Resolutions, Risk Register, Board Calendar, Documents and Data Room. Operations: Action Log, OKRs, Financial Review and Leadership Team.

Growth: Campaigns, Clients, Engagements, Product Backlog, Pipeline, Fundraising, Competitive Intel and Customer Reviews. Account: Integrations.

Yes. Language and currency are settings on the person, not the organisation. A chair reading in German and a CFO reading in French are looking at one record, not two translations of it. English, French, German and Spanish ship with the platform.

Thirty. Conversion uses European Central Bank reference rates retrieved through Frankfurter. The rate applied and the date it was taken are recorded against the figure, so a converted number can be checked later rather than taken on trust.

Yes. The language you set is held server-side and passed to the model with your question, so the answer comes back in your language, from the same governed record and with the same citations as everyone else's.

Yes, within limits you set. An agent can submit to nine modules. Four low-stakes records take effect immediately, with the agent named as the source. Five governance records land Pending until a different named person confirms them, and the submitting identity can never confirm its own.

No. An operator connects an agent in one guided step from inside the product, chooses what it may reach in plain language, and the connection details go straight to the agent client. The credential is never shown or copied where a direct route exists.

Yes. MCP access is included in every tier at no extra charge. What an agent may read and submit is set when it is connected, and a submission to a governance record waits for a different named person to confirm it.

Seven of the thirteen an agent can read. An agent can ask which modules accept a submission before trying one, and a refusal says whether the module takes no submissions at all or the credential is not scoped to it, because those need different fixes.

Boards and directors get evidence for every decision; founders and CEOs get a single governed view; risk and compliance get server-computed severity and audit-logged escalations; finance gets variance-linked packs; AI and engineering leaders get governed AI use and an MCP path for the tools your team already runs.

Professional and business services, financial services and regulated advisory, insurance, testing, inspection and certification, technology and AI companies, and any governance-sensitive organisation where AI use is emerging faster than leadership visibility and control.

Yes. The platform is jurisdiction-aware, the data-protection framing references the laws of your jurisdiction, and pricing is quoted in US dollars, pounds and euros. The advisory conversation is led by Michael as founder, regardless of geography.

The first conversation covers the workflows you need governed, the audit artefacts you already owe, and the connected tools in use today. From that the right starting point is clear, typically a readiness diagnostic or a short scoped trial.

Because the thing Boardverse governs is an entity, not a headcount. A board is small by design. The record you are accountable for does not get bigger when a fifth person joins it, but it does when a second company does.

The confirmation gate and dual sign-off need at least a Chair, a Founder, one further signatory and an administrator or operator. Five covers that with room for a finance lead. Below that the governance workflow becomes artificial for the teams the platform is built for.

The confirmation gate, dual sign-off and server-side severity are in every tier. Diligence-ready is what you can hand to somebody outside the company: an attestation for any period showing which controls operated, and extracts of who did what, cut to the period and activity a reviewer asks for. Quoted, because what a reviewer asks for depends on the reviewer.

No. MCP access is included in every tier. An agent can read thirteen modules and submit to nine, four taking effect immediately and five waiting for a different named person to confirm. An operator connects an agent in one guided step, chooses what it may reach, and can see what it has read and written.

No. Four languages and thirty currencies are in every tier, set per person rather than per organisation. There is no localisation tier and no charge for a second language.

Yes. Governed is $400 per entity per month paid monthly, or $4,320 a year paid annually, saving ten percent. In pounds that is £300 or £3,240, and in euros €375 or €4,050. The founding-cohort lock holds whichever way you pay.

Portfolio is sold to the fund or the holding company and deployed to each entity, with roles and access set per entity. It is quoted rather than priced on this page. Terms, retention posture and what each entity's reviewers can be given are confirmed in writing before anything is deployed.

You take your record with you. Every board pack for any period and the signature record of every approved resolution, at no additional fee, at any time.

From month one, a seat holder who refers a paying organisation receives a credit applied to their next renewal cycle. The exact credit value is confirmed at quote stage.

Michael Fasosin, founder and operator of Boardverse, with more than thirty-five years across software, consulting and venture-building, with multiple exits.

It is the reframe that isolated AI wins at task level get mistaken for organisational readiness at firm level. The leadership question is rarely whether AI is being used, it is whether the firm-level view of what is being trusted exists.

Because the platform carries no software resale agenda. The advisory comes first, the platform supports delivery, and the operator can speak plainly about what does not belong in your stack because nothing in the commercial model depends on adoption.

Nothing a connected tool submits to a governance record becomes official until a person who did not submit it says so.

Michael Fasosin, founder and operator. Boardverse is founder-led, so the first conversation is with the person who built the platform and who can answer the questions you actually have.

No. No product tour, no demo theatre, no software resale pitch. The conversation is about the decisions you need to evidence and the workflows you need governed.

A direct reply within 24 hours, Monday to Friday. If you have a live deadline, mention it in the body of the message and it will be escalated.

No. The first conversation is a fit conversation, not a sales call. If engagement is the right next step, it is scoped clearly from there.