Fenmoor Specialty Underwriting appoints Imogen Hartley as Chief Data Officer

News

Fenmoor Specialty Underwriting · leadership

On 2 Mar 2026 Fenmoor appointed Imogen Hartley, from Lornefield, as its first Chief Data Officer. She will be responsible for how the firm collects, governs and uses data. Her start date and reporting lines were not disclosed.

made from

What it says

What this says

As at Fri 9 Oct 2026

On 2 Mar 2026 Fenmoor appointed Imogen Hartley, from Lornefield, as its first Chief Data Officer. She will be responsible for how the firm collects, governs and uses data. Her start date and reporting lines were not disclosed.

What happened: the Underwriting Ledger reported the appointment and said platform usage among Fenmoor staff has been rising. The firm said the new role would help it get more from its single view of submission, claims and customer-relationship information.

For the account: a new senior owner of data is a renewal signal, and she may want to review what the platform is worth. Imogen is not yet shown as a contact.

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

AImade from

The item

Updated 9 Oct 26

Date2026-03-02

Typeleadership

Sourcetrade_press

OrganisationFenmoor Specialty Underwriting

Newsmade from

The record

Record

Field	Value
date	2 Mar 2026
news id	news_001_005
news type	leadership
org id	org_001
org name	Fenmoor Specialty Underwriting
source type	Trade press

Newsmade from

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

Help & Support

Open as a page

Help & Support

B-Glass 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-Glass 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-Glass Claude Project, with the same answers and sources.

What the data covers

Data	Records
Organisations	225
People at customers	862
BG-Demo staff records (in post and leavers)	58
Calls	1,995
Email threads	3,013
Support tickets	1,159
Documents	1,218
Deals	315
Invoices	285
Events	49
News items	119

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-Glass is the tool that reads its data.

Who to contact

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

Help