Maxine Ojo

Person

Bellgrove Pension Trustees · Economic buyer

Maxine Ojo is Chief Executive at Bellgrove Pension Trustees and the CRM economic buyer. She joined the 1 Oct 2026 discovery call, named the cost of manual data gathering, raised security, and agreed to a scoping call.

made from

Who they are

Insight

As at Fri 9 Oct 2026

Maxine Ojo is Chief Executive at Bellgrove Pension Trustees and the CRM economic buyer. She joined the 1 Oct 2026 discovery call, named the cost of manual data gathering, raised security, and agreed to a scoping call.

Role: Chief Executive and CRM economic buyer at Bellgrove Pension Trustees. The record shows one call, no email threads, no tickets and no deals.

Influence: On the 1 Oct 2026 discovery call she described slow member answers and audit readiness as the cost of the current setup, then said to move ahead. That reads as decision-making authority, though the call does not show a budget or decision date.

Watch: She asked about security because of personal member data, and the answer was only high level. It needs to hold up in the scoping call before the proposal.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

AImade from

CRM records

Organisation	Title	Role	Email
Bellgrove Pension Trustees	Chief Executive	Economic buyer	maxine.ojo@bellgrove.example

CRMmade from

Activity

1 Oct 2026callBellgrove Pension Trustees / BG-Demo – Discovery Sophie Ling, Oliver Pennock, Maxine Ojo

CRMmade from

BG-Demo is a fictional company; every organisation and person here is invented. B-Viz is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Viz is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

Summary is the landing page: what happened this week, the calls just held and the calls coming up, the risks and the renewals due.
Organisations lists every customer. Open one to see its key facts, the AI assessment and next step, platform usage, the ARR journey, deals, documents, contacts and activity, and the lineage of every block.
Conversations, Commercial, People, News and Documents cut the same data by topic. System explains how the site is built and where each figure comes from.
Every card ends with a small made from link: it opens the lineage explorer focused on that card, so you can walk from the figure down to the raw rows it came from.
Use the sun and moon button at the top right to choose dark or light. Choose your device's own mode again to go back to following the device.

How to ask

Press Ask B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

Ask B sends your question to Claude through the B-Viz connector. Claude answers from the same records as these pages, read-only, and links each claim to its source page.
Find (the box in the header) finds the organisations, people, calls, emails, tickets, documents and news that match your words, with links to their pages.
The same connector works in Claude Desktop or the B-Viz Claude Project, with the same answers and sources.

What the data covers

Data	Records
Organisations	300
People at customers	1,880
BG-Demo staff records (in post and leavers)	65
Calls	2,593
Email threads	3,882
Support tickets	1,502
Documents	1,582
Deals	403
Invoices	365
Events	49
News items	147

Data as of Fri 9 Oct 2026. Text marked AI was written by the AI from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BG-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Viz is the tool that reads its data.

Who to contact

Email info@b-viz.com or talk to your B-Viz account team. Tell us the page address and what looked wrong; a screenshot helps.

Help