B-Viz
Fairhallow Travel logo

Fairhallow Travel

Lost£0

AI facts

As at Fri 9 Oct 2026

Fairhallow Travel held a Growth order form at £40k a year, signed 13 Dec 2024, for 1 Jan 2025 to 31 Dec 2025, plus a £12k implementation. No executed paper covers any later term. No usage is recorded in the last 13 weeks, and the last day with usage was 31 Dec 2025. The renewal deal closed lost on 8 Dec 2025 and there is no open deal. The CRM still shows stage customer at £40k.

Read from 18 calls · 31 email threads · 9 tickets · 3 news items · 2 deals · 12 people · 12 documents, newest 23 Feb 26

Profile

Updated 9 Oct 26
  • IndustryTravel managementSource: CRM company record
  • Websitefairhallow.exampleSource: CRM company record
  • CountryUnited KingdomSource: CRM company record · CRM code GB · Region UK
  • HQ cityManchesterSource: CRM company record
  • Size240 employeesSource: CRM company record
  • CRM ownerTom AshdownSource: CRM company record · Account Executive · CSM Marcus Bell
  • Customer since1 Jan 2025Source: first executed order form ctr_020_01, signed 13 Dec 2024 · Growth tier · In the CRM since 11 Sep 2024
  • TypeChurneddiffersSource: contracts and invoices (signals) · CRM stage customer · The sources disagree
  • StateLostSource: AI assessment · As at Fri 9 Oct 2026 · written 21 Oct 2026

AI opinion

As at Fri 9 Oct 2026

Lost, because the Growth term ended on 31 Dec 2025 with no renewal, nothing has been invoiced since and usage stopped the same day. Simon Ashworth let it lapse over cost per booking after the champion left. He said they would review if things change, a possible win-back.

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

Key facts

Updated 9 Oct 26
  • Contracted ARR£0differsSource: executed order forms · CRM £39,600 · Invoiced run rate £0 · As of 9 Oct 2026 · The sources disagree
  • TierGrowthSource: deal_020_01
  • Last contact19 Dec 2025Call: Fairhallow Travel / BG-Demo – Check In · 294 days before 9 Oct 2026
  • Tenanteu-west-1Source: product analytics, reporting since Jan 2025 · 6 connectors configured
  • Licensed seats4031 active users in Sep 2026
Computedmade from

Next step

As at Fri 9 Oct 2026
What
Tom Ashdown moves Fairhallow Travel's CRM stage from customer to churned and clears the £40k amount, because the Growth order form ended on 31 Dec 2025 and nothing has been invoiced since. other
Who
Tom Ashdown Tom Ashdown
When
This week by 9 Oct 2026
Why
Tom Ashdown should move Fairhallow Travel's CRM stage off customer and clear the £40k this week. The Growth order form ended on 31 Dec 2025 and nothing has been invoiced since, so the record overstates ARR. Marcus Bell keeps a cost per booking win-back note ready.

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

The story

As at Fri 9 Oct 2026
Lost

Lost: Fairhallow Travel's Growth order form at £40k a year ended on 31 Dec 2025 without renewal, and usage stopped that day. The CRM still shows stage customer at £40k, and Tom Ashdown is correcting it.

Lost: Fairhallow Travel's only executed order form set Growth at £40k a year from 1 Jan 2025 to 31 Dec 2025. The renewal deal closed lost on 8 Dec 2025, yet the CRM stage still reads customer at £40k.

Questions fell from 1,171 in Oct 2025 to 868 in Dec 2025, and usage stopped on 31 Dec 2025. Tariq Hussain asked 36% of questions over the last 12 months. The champion, Becky Lawton, left in Aug 2025.

On 19 Dec 2025 Simon Ashworth, the COO, let the contract lapse over cost per booking and weak adoption after Becky left. Both invoices were paid within terms, and a news report says the customer is reviewing costs.

Tom Ashdown moves the CRM stage to churned and clears the £40k by 9 Oct 2026, with Rachel Dunmore confirming nothing has been invoiced since. Marcus Bell holds a win-back note.

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

ARR journey

Updated 9 Oct 26
Updated 09 Oct 26
CSV
Contracted ARRInvoiced ARR
£0£20k£40kJan 25Apr 25Jul 25Oct 25Jan 26newchurn£0£0Jan 25: Contracted ARR £39,600; Invoiced ARR £39,600Feb 25: Contracted ARR £39,600; Invoiced ARR £39,600Mar 25: Contracted ARR £39,600; Invoiced ARR £39,600Apr 25: Contracted ARR £39,600; Invoiced ARR £39,600May 25: Contracted ARR £39,600; Invoiced ARR £39,600Jun 25: Contracted ARR £39,600; Invoiced ARR £39,600Jul 25: Contracted ARR £39,600; Invoiced ARR £39,600Aug 25: Contracted ARR £39,600; Invoiced ARR £39,600Sep 25: Contracted ARR £39,600; Invoiced ARR £39,600Oct 25: Contracted ARR £39,600; Invoiced ARR £39,600Nov 25: Contracted ARR £39,600; Invoiced ARR £39,600Dec 25: Contracted ARR £39,600; Invoiced ARR £39,600Jan 26: Contracted ARR £0; Invoiced ARR £0

One point per month; the dot and figure at the right end are the latest value. Dashed upright lines mark dated events. Latest (Jan 26): Contracted ARR £0; Invoiced ARR £0. Invoiced ARR matches Contracted ARR in every month, so it is drawn dashed over it. Basis: accounting system, facts.arr_monthly:org_020.

Show the figures as a table
MonthContracted ARRInvoiced ARR
Jan 25£39,600£39,600
Feb 25£39,600£39,600
Mar 25£39,600£39,600
Apr 25£39,600£39,600
May 25£39,600£39,600
Jun 25£39,600£39,600
Jul 25£39,600£39,600
Aug 25£39,600£39,600
Sep 25£39,600£39,600
Oct 25£39,600£39,600
Nov 25£39,600£39,600
Dec 25£39,600£39,600
Jan 26£0£0
Accountingmade from

Finance read

As at Fri 9 Oct 2026

Churned, CRM still shows £40k

Standing Paid upARR Ended

Contracted ARR fell from £40k to £0 when the Growth order form ended on 31 Dec 2025. The CRM still shows £40k and stage customer, but nothing has been invoiced since. The renewal deal was lost.

  • Churned: last order form ended 31 Dec 2025
  • CRM still shows £40k and stage customer
  • Renewal lost, reason acquired_competitor
The analysis

Recurring revenue: The Growth order form ran from 1 Jan 2025 to 31 Dec 2025 at £40k a year. ARR churned in Jan 2026 and is now £0.

Next commitment: None. There is no live order form and no open deal.

Billing: INV-020-0001 (net £12k) and INV-020-0002 (net £40k) were both paid within terms. Nothing is overdue or disputed.

Deals: The renewal deal closed lost on 8 Dec 2025 with the reason acquired_competitor. The CRM shows £40k against an invoiced run rate of £0, a difference of £40k. The executed order form is the truth, so the CRM record is stale. Owner Tom Ashdown is active in HR.

Made from 2 deals · 2 fact tables · 2 invoices

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

History by quarter

As at Fri 9 Oct 2026

Each earlier quarter in one AI digest of its calls, email threads, tickets and news, newest first; from 1 Jul 2026 the assessment reads every one of them itself.

  1. Q1 2026

    Q1 2026: cost review, single view shelved

    One read in the period: a 23 Feb 2026 news report of cautious results at Fairhallow Travel, a cost and priorities review, and a reconsidered single-view ambition. The read rates it a high-significance renewal signal.

    The analysis

    This period holds one read, a news item. There were no calls, email threads or tickets in the period, so the customer's own voice is not shown.

    Trading: on 23 Feb 2026 Northern Travel Trade Bulletin reported cautious results and tougher trading for Fairhallow Travel. Management is reviewing costs and priorities.

    Ambition: the spokesperson said earlier efforts to bring bookings, service tickets and account reviews into a single view had been reconsidered. The read treats this as a direct signal on value and renewal risk, since that is the kind of use B-Viz serves.

    Risks named in the read: cost scrutiny could lead the customer to cut or downgrade the subscription. The spokesperson declined to say whether further changes were being considered.

    Open at the end: the read suggests preparing a value case with usage evidence before the next renewal conversation and testing the customer's current priorities. The evidence does not show whether any contact with the customer followed in the period.

    Made from 1 news item

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

  2. Q4 2025

    Q4 2025: value challenge, contract lapses

    Simon Ashworth, COO, questioned value from the 2 Oct 2025 renewal notice onwards. A positive QBR on 12 Nov 2025 did not hold: on 19 Dec 2025 he said the £40k Growth contract would lapse on 31 Dec 2025.

    The analysis

    Renewal notice: On 2 Oct 2025 Marcus Bell sent the Growth renewal notice (£40k, 40 licensed users, term ending 31 Dec 2025). Simon replied tersely, asking for usage and monthly cost.

    16 Oct 2025 call: Simon said he pays for forty licences and uses a fraction, and told finance not to forecast the renewal yet. He noted that Becky used to say it was worth it and is no longer there.

    QBR: On 12 Nov 2025 Simon called usage better than he expected. Leanne Moss said review preparation had gone from an afternoon to under an hour, though she remained the heaviest user and the admin.

    17 Nov 2025 call: Tom Ashdown proposed Growth on the same terms. Simon asked to drop unused seats and for the break position; Tom offered Starter and said the term is annual.

    15 Dec 2025 thread: Simon said only a handful of people use the brain and expected no change.

    Outcome: On 19 Dec 2025 Simon declined a smaller set of seats and said the company will let the contract run out. He cited cost per booking and that no one has pushed adoption since Becky left.

    Open at the end: The contract ends on 31 Dec 2025. Simon said the company would review if things change, so a win-back is possible but not planned.

    Made from 4 calls · 4 email threads

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

  3. Q3 2025

    Q3 2025: connector faults, champion leaving

    Two connector tickets in July, then from 18 Aug 2025 signs that champion Becky Lawton was leaving. The 22 Aug 2025 call agreed a value summary for the COO. A webinar invitation on 26 Sep 2025 drew no reply.

    The analysis

    Support: on 2 Jul 2025 dashboards ran slowly after a large batch upload, and a connector query was optimised the same day. On 23 Jul 2025 Becky reported duplicated contact records from a connector; the fix took 22 days.

    People: on 18 Aug 2025 Becky Lawton asked for a check-in soon, saying things were shifting on her side and she wanted to answer while she was still around. The detail of her change was not shown in that thread.

    Renewal: on the 22 Aug 2025 call, Marcus Bell learned Becky had about a week left. About six of forty licensed users are active on a normal day, slightly down on the quarter before.

    Commercial: the contract runs to 31 Dec 2025 and renews from 1 Jan 2026 at £40k a year. The COO will ask who is using it and what it costs. Marcus agreed a one-page value summary and a September team session.

    Adoption: on 26 Sep 2025 Alice Brewer invited Leanne Moss and her team to a webinar on 16 Oct 2025. The thread holds no reply.

    Open at the end: the handover to the COO, the value summary, the September session, a connector audit for duplicates, and batch upload timing windows.

    Made from 1 call · 2 email threads · 2 tickets

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

  4. Q2 2025

    Q2 2025: usage up, value questions at QBR

    Fairhallow Travel's Growth usage rose and Becky Lawton was warm, but at the 19 May 2025 QBR the COO, Simon Ashworth, questioned usage against 40 licences and said they will review at renewal. A June check-in was positive.

    The analysis

    Check-in: On 15 Apr 2025 Becky Lawton welcomed usage figures and asked for views by client. The 17 Apr 2025 call, led by Marcus Bell after Callie's departure, showed six or seven daily users and a client's finance director praising a brain page.

    Scheduling: On 9 May 2025 Becky asked for the QBR to lead with usage by client. The accounting connector still waited on Simon's budget.

    Support: A new finance user request on 12 May 2025 took 341 minutes to first response and 24 days to resolve. Dashboards ran slowly on 15 May 2025 and blocked a client meeting; first response took 41 minutes and it was solved the same day.

    QBR: On 19 May 2025 Simon pressed on who uses the brain and what it costs, and said "Fine. We'll review at renewal." He declined the accounting connector for now, maybe after summer.

    June: Becky said on 20 Jun 2025 "Honestly, I'm happy", asked for one page per client and was curious about the call recorder. The contract runs to the end of the year.

    Open at the end: Becky owes a time-saved figure, logged by Tariq. Tariq is the fastest adopter and unofficial trainer, so key-person risk is building. The renewal conversation has not started. Replies to the Customer Day and webinar invitations are not shown.

    Made from 3 calls · 5 email threads · 2 tickets

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

  5. Q1 2025

    Q1 2025: Growth onboarding, value case pending

    Fairhallow Travel onboarded onto Growth in a positive quarter. Setup was slowed by thin admin capacity and IT access. A duplicate-records fix and a helpdesk connector break were resolved. Becky Lawton still needs a value case for Simon.

    The analysis

    Billing: Invoice INV-020-0002 for the Growth subscription, £40k net, was issued on 2 Jan 2025 and due on 1 Feb 2025. The reads do not show payment.

    Kickoff: On 3 Jan 2025 Callie Brennan opened the implementation with Becky Lawton and Leanne Moss, and Becky was positive. Simon signs but stays out of the project, and Becky expects him to ask what the company gets out of it.

    Onboarding: Calls on 9 Jan 2025, 27 Jan 2025 and 31 Jan 2025 moved from first refresh to three, then five, planned connectors. Leanne was short of people, missed slots, and helpdesk access waited on IT.

    Value worry: On 27 Jan 2025 Becky said Simon will ask what they have for the money. A by-client review pack was the agreed answer.

    Support: A how-to ticket on 17 Jan 2025 was resolved. Duplicate client records on 28 Jan 2025 were cleaned within hours.

    Outage: On 11 Mar 2025 helpdesk tickets stopped loading after an API upgrade. Support moved the connector to the new endpoint.

    Adoption: On 25 Feb 2025 Callie trained Tariq Hussain and Leanne, and Tariq found a bookings dip matching a rise in tickets. On 19 Mar 2025 Becky asked for access for two more account managers.

    Open at the end: Rollout beyond a few users, a value case for Simon, and connector monitoring were all still open.

    Made from 5 calls · 6 email threads · 5 tickets

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

  6. Q4 2024

    Q4 2024: Growth deal signed after price scrutiny

    Fairhallow Travel moved from discovery to a signed Growth order form at £52k including implementation. Becky Lawton championed it; COO Simon Ashworth pressed on value and cost and said they will review at renewal. Kickoff was being set for January.

    The analysis

    Discovery and demos: On 3 Oct 2024 Becky Lawton described account reviews built by hand, and COO Simon Ashworth was sceptical on price and value. Demos on 21 Oct 2024 and 28 Oct 2024 landed well, with a per-client dashboard the main draw.

    Open questions: Leanne Moss, the likely admin, asked on 30 Oct 2024 who fixes a connection if a source system changes. The booking system and travel platform connections were still unconfirmed on 7 Nov 2024.

    Proposal and price: Tom Ashdown presented Growth at £52k including implementation on 7 Nov 2024. Becky asked about flexibility and quarterly payment, and would not promise the 13 Dec 2024 close.

    Negotiation: On 26 Nov 2024 Simon said the plan meant paying for forty and using a dozen, and asked for a monthly view and quarterly billing. On 27 Nov 2024 he said "We'll review at renewal", so first-term value must be shown.

    Signing and start: The order form went out on 11 Dec 2024 and Simon returned a signed copy on 16 Dec 2024, three days late. Invoice INV-020-0001 was sent the same day for a net £12k, gross £14k, with no customer response shown.

    Open at the end: Kickoff in January depends on IT access. Becky wants data by client from the first refresh, and the connector questions remain unanswered in these reads.

    Made from 5 calls · 11 email threads

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

  7. Q3 2024

    Q3 2024: invitations, then a discovery call

    Four reads: an undisclosed regulatory announcement on 23 Jul 2024, two unanswered event invitations, and on 30 Sep 2024 Becky Lawton agreeing to a discovery call, wanting something before her team's next reviews.

    The analysis

    News: on 23 Jul 2024 a trade bulletin reported that Fairhallow Travel issued a regulatory announcement. The company said it did not affect service to existing clients, and the nature of the matter is not disclosed.

    Outreach: on 14 Sep 2024 Sofia Marchetti invited Tariq Hussain to the BG-Demo stand at the Data leaders conference in Amsterdam on 9 Oct 2024. On 24 Sep 2024 she invited Diane Cropper and the finance team to a webinar on 17 Oct 2024.

    Response: neither invitation has a reply in the thread, so interest is not shown.

    Discovery call: on 30 Sep 2024 Tom Ashdown asked Becky Lawton for a discovery call of about forty-five minutes. Becky declined Thursday 10:00 and proposed Friday 11:00 with Leanne from operations, who knows where the data lives.

    Customer view: Becky preferred starting with how the team works rather than a demo. She said her team needs something before the next round of reviews, which is the only clear sign of interest in the period.

    Open at the end: Tom was to confirm Friday at 11:00 with Becky and Leanne. Whether the regulatory matter touches the customer's data was still to be asked at the next call. No reply from Tariq or Diane is recorded.

    Made from 3 email threads · 1 news item

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

  8. Q2 2024

    Q2 2024: technology partnership announced

    One read in the period: a 29 May 2024 trade bulletin report of a partnership with an unnamed technology partner. The spokesperson said no changes to existing arrangements were planned. Low significance, worth awareness only.

    The analysis

    News: this period holds one read. On 29 May 2024 Northern Travel Trade Bulletin reported that Fairhallow Travel had announced a partnership with an unnamed technology partner to give clients a more joined-up view of their travel programmes.

    Terms: the company declined to give commercial terms. The spokesperson said the partnership was not a change in direction and that no changes to existing arrangements were planned.

    Read as: the read rates the news as neutral and of low significance. It notes that the unnamed partner may overlap with tools the customer already uses, but the report gives no sign of any change.

    Open at the end: the partner's identity and what the partnership covers were not known. The read suggests asking at the next call what it covers.

    Made from 1 news item

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

Platform usage

Updated 9 Oct 26
Active users · Dec 25
31of 40 included on the tier
Questions asked · Dec 25
868
Connectors configured · Dec 25
6of 8 included on the tier
Active admins · Dec 25
1
Data volume · Dec 25
3.1 GB
Active users and questions · monthlyUpdated 09 Oct 26
CSV
Left axisActive usersLicensed seatsIncluded users (40)Right axisQuestions asked
0020600401,200Feb 25Apr 25Jun 25Aug 25Oct 25Dec 25crm stage staleIncluded users (40)4031868Jan 25: Active users 15; Licensed seats 40; Questions asked 219Feb 25: Active users 23; Licensed seats 40; Questions asked 547Mar 25: Active users 26; Licensed seats 40; Questions asked 755Apr 25: Active users 30; Licensed seats 40; Questions asked 880May 25: Active users 32; Licensed seats 40; Questions asked 1,091Jun 25: Active users 32; Licensed seats 40; Questions asked 1,097Jul 25: Active users 32; Licensed seats 40; Questions asked 1,188Aug 25: Active users 31; Licensed seats 40; Questions asked 627Sep 25: Active users 31; Licensed seats 40; Questions asked 1,152Oct 25: Active users 31; Licensed seats 40; Questions asked 1,171Nov 25: Active users 31; Licensed seats 40; Questions asked 1,096Dec 25: Active users 31; Licensed seats 40; Questions asked 868

Questions asked are read on the right axis, on their own scale, and users on the left: questions run to thousands a month where users run to hundreds. The dotted line is the allowance. Dashed upright lines mark dated events. Latest (Dec 25): Active users 31; Licensed seats 40; Questions asked 868. Basis: product usage, facts.usage_monthly:org_020, signals:org_020.

Show the figures as a table
MonthActive usersLicensed seatsQuestions asked
Jan 251540219
Feb 252340547
Mar 252640755
Apr 253040880
May 2532401,091
Jun 2532401,097
Jul 2532401,188
Aug 253140627
Sep 2531401,152
Oct 2531401,171
Nov 2531401,096
Dec 253140868
Connectors, admins and data volume · monthlyUpdated 09 Oct 26
CSV
Left axisConnectors configuredActive adminsIncluded connectors (8)Right axisData volume
00.0 GB42.0 GB84.0 GBFeb 25Apr 25Jun 25Aug 25Oct 25Dec 25Included connectors (8)3.1 GB61Jan 25: Connectors configured 4; Active admins 2; Data volume 1.71 GBFeb 25: Connectors configured 5; Active admins 2; Data volume 2.18 GBMar 25: Connectors configured 6; Active admins 2; Data volume 2.66 GBApr 25: Connectors configured 6; Active admins 2; Data volume 2.71 GBMay 25: Connectors configured 6; Active admins 2; Data volume 2.77 GBJun 25: Connectors configured 6; Active admins 2; Data volume 2.82 GBJul 25: Connectors configured 6; Active admins 2; Data volume 2.87 GBAug 25: Connectors configured 6; Active admins 2; Data volume 2.92 GBSep 25: Connectors configured 6; Active admins 1; Data volume 2.97 GBOct 25: Connectors configured 6; Active admins 1; Data volume 3.02 GBNov 25: Connectors configured 6; Active admins 1; Data volume 3.07 GBDec 25: Connectors configured 6; Active admins 1; Data volume 3.13 GB

Data volume is read on the right axis, in GB, and connectors and admins on the left, as counts: one scale would flatten the counts. The dotted line is the allowance. Latest (Dec 25): Connectors configured 6; Active admins 1; Data volume 3.1 GB. Basis: product usage, facts.usage_monthly:org_020, signals:org_020.

Show the figures as a table
MonthConnectors configuredActive adminsData volume
Jan 25421.71 GB
Feb 25522.18 GB
Mar 25622.66 GB
Apr 25622.71 GB
May 25622.77 GB
Jun 25622.82 GB
Jul 25622.87 GB
Aug 25622.92 GB
Sep 25612.97 GB
Oct 25613.02 GB
Nov 25613.07 GB
Dec 25613.13 GB

Usage read

As at Fri 9 Oct 2026

Usage ended December 2025

Direction Ended

Usage has ended: no usage in any of the last 13 weeks, and the last day with any usage was 31 Dec 2025. Every listed contact's platform user is deactivated and there is no live order form.

  • No usage in the last 13 weeks
  • Last usage on 31 Dec 2025
  • One person asked 36% of questions
  • No live order form
The analysis

Recent weeks: all 13 weeks ending 9 Oct 2026 show no usage reported, and the last 90 days hold 0 questions. The last day with any usage was 31 Dec 2025.

Trend: questions fell from 1,171 in October 2025 (the 12-month peak) to 868 in December 2025, with average daily active users down from 8.3 to 5.8.

Who used it: Tariq Hussain carried 1,132 of 3,135 questions (36%) over the last 12 months, a key-person concentration. Callum Bailey had 369 (12%). Leanne Moss was the admin, and her platform user was deactivated on 31 Dec 2025.

Against the order form: there is no live order form. In September 2026 the records show 31 active users against 40 licensed users and 6 connectors configured.

Made from 2 fact tables

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

Documents

Updated 9 Oct 26

12 documents in 6 folders; 2 drafts hang on their executed paper. All documents

  • commercial
  • delivery
  • presales

Size is importance: state 40%, category 20%, recency 25% (18-month half-life on the as-of date) and usage 15%. There are no view counts: usage means how many of our own analyses cite the document, saturating at 5. A draft hangs on the executed or issued document it drafts for, in the same folder. A draft with nothing executed behind it stays a small leaf on its own.

Folders and documents as a list
Documentsmade from

Open deals

No open deals.

Open tickets

No open tickets.

Helpdeskmade from

Activity

Contacts

Evidence trail

Updated 9 Oct 26
Key
  • Source rows
  • Raw things
  • People
  • Organisation
  • Organisation AI
  • Pages
  • AI-written record (ring)
  • AI record not written yet
  • belongs to the organisation (one line per group)
  • Size: how many records a group holds
  • Columns, left to right: Source rows, Raw things, AI summaries, People, Organisation, Organisation AI, Narratives, Pages

Fairhallow Travel's pages are written from 3 organisation-level AI texts (assessment / next steps), 8 period digests and 1 narrative-level AI text, which in turn draw on 73 AI summaries of 77 raw things (calls, tickets, emails, news), 1 usage read, 1 finance read, 12 people (12 with an AI write-up) and 5 staff (0 with an AI write-up), shown on 14 pages.

The trail as a list (block, record, entity, raw row)
Computedmade from
Sources AI · Accounting · Calls · Contracts · CRM · Documents · Events · Support · Email · Web · Usage

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

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.

What the data covers

DataRecords
Organisations300
People at customers1,880
BG-Demo staff records (in post and leavers)65
Calls2,593
Email threads3,882
Support tickets1,502
Documents1,582
Deals403
Invoices365
Events49
News items147

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

Ask B

B-Viz · read-only