Fairhallow Travel: documents logo

Fairhallow Travel - Renewal Proposal v1

Documentdraft

Fairhallow Travel: documents logo Fairhallow Travel: documents · renewal_proposal · draft · 2025-10-21

Internal draft renewal proposal by Tom Ashdown, dated 21 Oct 2025, for the Growth tier term ending 31 Dec 2025. It cites contracted annual recurring revenue of £39,600 and 40 licensed users, and leaves the renewal price to be confirmed.

What it says

What this says

Current to 11 Oct 26

Internal draft renewal proposal by Tom Ashdown, dated 21 Oct 2025, for the Growth tier term ending 31 Dec 2025. It cites contracted annual recurring revenue of £39,600 and 40 licensed users, and leaves the renewal price to be confirmed.

What it is: an internal draft, marked "Draft" for internal review, proposing a further annual term on the Growth tier. It was created and last modified on 21 Oct 2025 and is not an issued customer document.

Commits: nothing binds either party. It proposes keeping 40 licensed users, the same connectors and the same service levels as the current order form, with quarterly reviews led by Marcus Bell.

Unusual: the price section states "The renewal price is to be confirmed", so no renewal figure exists. The £39,600 is the current contracted figure as this document states it, and the text defers to the executed order form.

Not settled: price, discount treatment, the renewal call date and wider adoption. The document states no availability, response times or credits, and it is dated well before the as-of date, so check what became of the renewal.

AI · claude-sonnet-5-5 · 11 Oct 2026

As found in this document

Current to 9 Oct 26
  • Date end31 Dec 2025Source: object_read:doc_020_010

The document

Body

Fairhallow Travel - Renewal Proposal v1

Draft for internal review. Prepared by Tom Ashdown, Account Executive, BB-Demo. Date: 21 October 2025.

1. Context

Fairhallow Travel, a business travel management company based in Manchester, joined BB-Demo on 1 January 2025 on the Growth tier. The brain brings client bookings, service tickets and account reviews into one place so that account teams stop reconciling them by hand. The current term ends on 31 December 2025, and this paper sets out how we propose to renew it.

2. Where the account stands

ItemPosition
TierGrowth
Contracted annual recurring revenue£39,600
Licensed users40
Term start1 January 2025
Term end31 December 2025
Overdue invoicesNone
Support tickets in the last monthNone
High priority tickets in the last monthNone

The account has been quiet and tidy: invoices are paid and nothing has needed escalating. Active use has grown on the previous quarter, though the number of people asking questions is still a small share of the licensed users.

3. Proposal

Read the whole document (2,329 characters)
  • Renew on the Growth tier for a further annual term starting straight after the current one ends.
  • Keep the user allowance at 40 licensed users.
  • Keep the same connectors and the same service levels as the current order form.
  • Hold the quarterly reviews with Marcus Bell, our CSM, so that Fairhallow Travel can see the questions asked and the value delivered.

4. Pricing

The renewal price is to be confirmed. The current contracted annual recurring revenue is £39,600, and the executed order form decides the contracted terms. Any change to price needs checking against the price book before anything goes to the customer.

5. Open points

  • Confirm the renewal price and any discount treatment with the finance team.
  • Agree with Marcus how to show the value case, given that use is growing but is concentrated in a few people.
  • Decide whether to raise wider adoption across more of the 40 licensed users before the renewal conversation.
  • Settle the date for the renewal call with the customer.

6. Next steps

  1. Tom to confirm the price and terms internally.
  2. Marcus to prepare a short usage summary.
  3. Tom to issue the final proposal to Fairhallow Travel once the open points are closed.
Documentsmade from

Unusual terms

Current to 9 Oct 26
  • Renewal price left to be confirmed
  • Draft prepared for internal review only

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain 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 Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain 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.

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

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B

Ask B

B-Brain · read-only