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 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.

No. Every MCP v1 tool is read-only. A connected tool can submit, but nothing it submits is trusted until a different named person confirms it. Writes land Pending and the submitting identity is blocked from self-confirming.

No. The MCP server is a thin, standards-based front door onto the platform's existing access boundary. It reuses the same Personal Access Token a Founder generates from Settings. No OAuth flow, no new credential type.

Yes. MCP access is a read path onto data your seats already pay for, so it is included in every seat at no extra charge.

Yes, in v2, and they are deliberately shaped around the platform's approval workflows rather than generic read-write access. Until then, writes are PAT-controlled inside the app.

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 USD. 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.

The confirmation gate and dual sign-off require at least a Chair, a Founder plus one further signatory, and an admin or operator. Below four seats the governance workflow becomes artificial for the kinds of teams the platform is built to support.

No. The governed record is one product. There are no per-module add-ons and no per-token fees.

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.

Yes. Enterprise and multi-board terms are available on request, including multi-entity governance, custom retention rules and extended audit extracts.

Michael Fasosin, founder and operator of Boardverse, with more than thirty-five years across software, consulting and venture-building, including the exit of a digital agency to a global network.

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 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 two working days. 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.