A brochure for each kind of partner.

Make your card the first choice at home and abroad.

The gap between having a benefit and using it, Trip Radar, points in the purchase, protection on a trigger, the three levels, signals for the rest of the bank, and the ways in.

The programme, between flights.

Miles on the ground, disruption as a service, the co-branded card, the connector, COMPANION+ for your VIPs, member privacy and the ways in.

Your rooms and your programme, in the app members use every day.

The stay in the app, what the guest shares, the Towbar integrations, partner success and the micro label.

Your club, in the one app your members use every day.

The membership in the wallet, plans with friends, reciprocity, affiliate income, the club dashboard and the micro label.

Your publication, in the one app your readers use every day.

From the article to the booking, the subscription in the wallet, ancillary income, signals and the micro label.

The card that comes out.

Every bank wants the same things from its card: first choice at home, the card in hand abroad, and benefits that are felt rather than filed. The gap is knowing which one to put in front of which cardholder, and when. Seven arguments on why personalisation is a data question, why the data is already the bank’s, and what has to be true structurally before the right benefit reaches the right cardholder at the moment it applies.

1. The gap between having a benefit and using it
2. Personalisation is a data question
3. Trip Radar — the trip announces itself
4. The trigger — the purchase is the moment
5. Points in the purchase
6. The layer underneath
7. What this looks like next

The other 360 days.

You know your members in the air better than anyone. The rest of the year is where the programme is won or quietly lost. Seven arguments on being present on the ground, giving miles somewhere to go, and owning the demand that assistants are about to route around you.

1. Booking by asking
2. The referrer that vanished
3. The member number, before the search
4. Miles that work on the ground
5. One settlement, anywhere
6. Attribution you own
7. Not a replatform

Sold as if it were yours.

Most channels stand between you and the guest. This one sells your rooms as if they were selling on your own site, hands the guest back as a member, and puts your programme at the front of their wallet. Seven arguments on enrolment in the flow, data that passes through, the stay sold before the door, and the commercial model that makes it work for both of us.

1. The channel that behaves like yours
2. The guest comes back as a member
3. Your programme, first
4. The data passes through
5. Sold before the door
6. Connected to the property
7. The model, and the four ways in

Membership that leaves the building.

The member you see twice a week is the most valuable customer on the book, and the one whose membership stops at the car park. On enrolment in the flow, a membership that travels, and the revenue a club earns beyond the fee.

1. The member you see twice a week
2. Enrolment in the flow
3. The court, the credit, the guest
4. A membership that travels
5. Revenue beyond the fee
6. What the club sees
7. What this looks like next

The page that became a booking.

The page that inspired the trip gets none of the credit for it. On turning editorial into a booking you can see, offers that know the city the reader is in, and a reader who carries the title in their wallet.

1. The page that inspired the trip
2. Attribution for editorial
3. Commerce without a shop
4. The reader, in the wallet
5. Offers that know the city
6. What the title sees
7. What this looks like next

From the answer to the booking.

Language models are good at answering a travel question. Answering is the easy part. On the rest of the job: knowing who is asking and what they hold, checking live supply, holding it, paying once, and sharing it with the people who are coming. Why that takes identity, supply, payment and loyalty working together, not a model on its own.

1. The answer is the easy part
2. Grounded in what the member holds
3. Live supply, held and priced
4. The plan, shared
5. Before they ask
6. What partners get

An agent that can pay.

An agent that can recommend is useful. An agent that can buy changes how commerce works, and it needs four things a recommendation never did: an identity it acts for, authority it can prove, a way to pay across suppliers, and a record of what it did. What that requires, how BLACKBOOK provides it, and what programmes need in place.

1. From recommendation to transaction
2. Identity and authority
3. The call layer
4. Paying across suppliers
5. Controls and risk
6. Getting ready

Who they are, and what they do.

Personalisation needs behaviour: what people actually do, how often, and where. On BLACKBOOK ID, the consent-based identity layer, and the behavioural graph it makes possible: everyday behaviour grounded in real transactions, used only with permission, and returned to partners as signals rather than data.

1. Why personalisation stalls
2. BLACKBOOK ID
3. The behavioural graph
4. Active state
5. Signals, not data
6. What it means for partners

Anonymous by design.

Members call services anonymously, and their identity is resolved only when fulfilment needs it. The principles, the architecture that enforces them, the consent record, the controls, and what a partner reviews before launch. Written for security and data protection teams.

1. Principles
2. Anonymous service calls
3. Permissions before retrieval
4. The consent record
5. Architecture and controls
6. Review before launch