Siloed regions
The cost is rarely dramatic. It is a small amount of lost time and lost context on every journey, repeated all year.
Property, logistics and infrastructure / Asset intensive enterprises
For a airport operator, most of the work sits between the systems. Operloom designs that layer deliberately, builds it, connects it and documents who owns what.
The pressure sits in one place: long asset cycles and site-level operations that head office cannot see directly. That is the part worth designing.
Primary conversion: Enterprise enquiry, account opportunity, partner application or digital transaction
01Enterprise
These are the recurring constraints for a airport operator. Each one has a system consequence, which is what the implementation is scoped against.
The cost is rarely dramatic. It is a small amount of lost time and lost context on every journey, repeated all year.
Passengers tend to notice this before the business does, even if nobody inside would describe it as a problem yet.
None of this is unusual for a airport operator, which is exactly why it goes unaddressed for so long.
It tends to hold until volume rises. At that point the informal version stops working and nothing has replaced it.
Because long asset cycles and site-level operations that head office cannot see directly, this one compounds rather than staying still.
02Enterprise
This is the shape the system takes for a airport operator. The connections matter more than the boxes: most of the failures happen between systems rather than inside them.
Where a passenger first finds the business.
The pages a passenger reads before deciding to make contact.
Qualifying questions asked once, at the point of enquiry.
Every passenger, every journey and who owns it.
Real availability for a journey, with the preparation time it needs.
Estimates and invoices raised from the agreed scope.
Payment taken and reconciled against the record.
Operational and lifecycle messages that arrive and are logged.
The rules that move work between systems, with human review where it matters.
What a passenger can see and do without contacting anyone.
Campaigns tracked through to the record they produced.
The measures a airport operator is actually run on.
Who is told, when, and what they are expected to do about it.
03Enterprise
A CRM and customer data platform only earns its place when it is the record everyone trusts. For a airport operator that means holding global accounts, contacts, buying groups, territories, opportunities, contracts, partners and service relationships and nothing nobody maintains.
No duplicates, and no separate spreadsheet holding the version people actually trust.
The stages a passenger actually moves through here, named the way the team already names them.
Open journeys with a realistic value and a next action, so the forecast means something.
Source captured on the first touch, because reconstructing it later is guesswork.
Somebody is responsible for every open journey, and the system knows who.
Tasks that appear on the right day for the right person, and chase when they do not happen.
A short set of measures, defined once, produced the same way every period.
Access matched to role, which matters as soon as more than one person is involved.
04Enterprise
This is the route a passenger takes. Each step is a place where the system either holds the context or drops it.
A passenger finds the business through tender, framework agreements and long-standing relationships.
They check whether this is the right organisation for them. This is what operational track record, compliance and reporting that stands up to scrutiny is for.
They send an commercial enquiry. The form asks the questions that decide whether it can be scoped, and nothing else.
The commercial enquiry is routed and qualified against the criteria that actually predict a good journey.
The passenger is set up with access, expectations and a first result worth having.
The journey is delivered. What happened is recorded against the passenger, not in a separate note.
An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.
Renewal is worked before it is due, from usage rather than from the date alone.
05Enterprise
The recommended build is enterprise B2B experience, solution and account platform. The modules below are the ones this operating model needs, not a sitemap template.
06Enterprise
These are the workflows that carry the repeatable parts of a journey. Every one of them has a human review point, because the useful automations are the ones people trust.
07Enterprise
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
08Enterprise
Reporting is built around the decisions the business actually makes. For a airport operator that is a short list, which is the point.
Measured from the record rather than reconstructed at month end.
Broken down by source, so the number leads somewhere.
Tracked as a trend, because a single period rarely means anything.
Defined once and written down, so it means the same thing next quarter.
Broken down by source, so the number leads somewhere.
09Enterprise
Email only works when it arrives. Authentication and list hygiene come before anything creative, because a message in spam is worse than no message.
10Enterprise
Discovery for a airport operator runs through tender, framework agreements and long-standing relationships. The channels below are the ones that follow from that, and nothing is included because it is fashionable.
The foundations: crawlability, speed, structure and the markup that describes what this business is
Solution, industry, product, integration, location and thought leadership architecture
Location and regional presence management where commercial relevance exists
Answering what a passenger needs to know before they will make contact
Corporate, executive, product, employer and account based content governance
Search, LinkedIn, account based media and retargeting tied to pipeline
Customer proof, references, analyst content and corporate reputation
Campaign pages built from the same components, so they are fast to ship and consistent to measure
11Enterprise
Quoting, invoicing and payment are built as one path rather than three tools, because the gaps between them are where revenue goes missing.
A passenger asks for pricing with enough detail attached to answer properly.
Approval is recorded against the scope it approved.
Where a deposit is how the work is committed, it is taken at that point.
Raised from the agreed scope, not retyped from it.
Without a phone call, and reconciled automatically.
Available to the passenger rather than requested from you.
Visible on the record, so chasing is informed.
12Enterprise
Scheduling for a airport operator is where most of the avoidable loss sits. account, technical, sales and service meetings routed by segment, geography and capability.
Read from the real calendar, so double booking is not possible rather than unlikely.
Preparation and turnaround built into the slot, because a appointment is not only the time with the passenger.
The questions that decide whether the slot is right, asked before it is taken.
On the interval this kind of work needs, each one carrying a reschedule link.
A passenger can move a appointment without a phone call, which is how you find out early.
A clear policy applied consistently, with the slot released for rebooking.
To the right person and the right location, using rules rather than judgement.
Handled properly wherever the work crosses them.
13Enterprise
Scope is decided by what the operating model requires, not by what is available. Core is structural for a airport operator. Recommended follows shortly after. Optional depends on the year you are having.
CRM setup and data model supports airport operator businesses by helping to connect global demand
Pipeline and lifecycle design supports airport operator businesses by helping to connect global demand
Lead routing, scoring and follow up supports airport operator businesses by helping to connect global demand
Website build or redesign supports airport operator businesses by helping to connect global demand
Service and landing pages supports airport operator businesses by helping to connect global demand
Email infrastructure and deliverability supports airport operator businesses by helping to connect global demand
Email campaigns, nurture and reminders supports airport operator businesses by helping to connect global demand
Analytics and conversion tracking supports airport operator businesses by helping to connect global demand
Dashboards and attribution supports airport operator businesses by helping to connect global demand
Client, patient or customer portal supports airport operator businesses by helping to connect global demand
Help desk and service workflows supports airport operator businesses by helping to connect global demand
Platform integrations and APIs supports airport operator businesses by helping to connect global demand
Security, privacy and maintenance supports airport operator businesses by helping to connect global demand
Multi location and franchise management supports airport operator businesses by helping to connect global demand
Enterprise governance and data architecture supports airport operator businesses by helping to connect global demand
Brand identity system supports airport operator businesses by helping to connect global demand
Technical and on page SEO supports airport operator businesses by helping to connect global demand
Content strategy and copywriting supports airport operator businesses by helping to connect global demand
Documents, forms and e signature supports airport operator businesses by helping to connect global demand
Workflow automation supports airport operator businesses by helping to connect global demand
14Enterprise
The honest claim is narrow: a well built system makes certain failures much less likely and makes the rest visible. For a airport operator the areas below are where that shows up first, each with the measure that would prove it.
Being able to change how the work runs without needing the person who originally set it up.
Measure: Account engagementRemoving the steps between interest and a committed journey, and making the next action obvious at every point.
Measure: PipelineAsking the qualifying questions at the point of enquiry, so the journey is scoped before anyone spends time on it.
Measure: ConversionCutting the gap between an commercial enquiry arriving and a person answering it, which is usually the single largest lever.
Measure: InfluenceKnowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: Service and revenue reportingTaking the repeatable parts of the journey out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.
Measure: Account engagement15Enterprise
A short audit of the platforms, the data in them and the points where an commercial enquiry stalls.
The operating model on paper first: stages, ownership, definitions and the measures that will judge it.
Build and configure, sequenced so the part that is losing work today is fixed first.
The handovers between CRM, ERP, product, service, identity, data warehouse, analytics and integration platforms made explicit and monitored.
Everything written down, because a system only one person understands is a risk rather than an asset.
Instrumented against account engagement, pipeline and conversion, with the definitions agreed first.
Regular review with a small change list, judged against the baseline rather than against opinion.
16Enterprise
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
17Enterprise
Recommended starting scope
Enterprise Revenue and Digital Operations
A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.
Core measures
Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.
18Enterprise
Privacy, security, industry obligations, records, accessibility and global governance.
That is a factual summary of the areas that tend to apply, not advice. Requirements vary by jurisdiction and change. We build to what your advisers confirm applies, and we implement it properly: consent capture, retention, access control, audit trails and secure handling.
19Enterprise
Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.
It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and customer data platform and commercial enquiry capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.
Through a shared data model and explicit ownership rather than a single template imposed on everyone. Common definitions, governed components and one measurement layer, with local teams able to move inside agreed boundaries. Accessibility, security and documentation are part of the build rather than a later phase.
You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.
Carefully, and within our lane. Privacy, security, industry obligations, records, accessibility and global governance. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.
The scope starts from how this kind of business runs rather than from a package. In practice that means enterprise B2B experience, solution and account platform, a CRM and customer data platform holding global accounts, contacts, buying groups, territories, opportunities, contracts, partners and service relationships, and the booking and follow up around it. The nearest starting point in our catalogue is Enterprise Revenue and Digital Operations, which is a scope to argue with rather than a fixed list.
Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: commercial enquiry capture that carries its source, tracking that survives, and a clean handover into the CRM and customer data platform. The CRM question is whether it can hold global accounts, contacts, buying groups, territories, opportunities, contracts, partners and service relationships without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.
Availability comes from the real calendar, not a copy of it, so a journey cannot be booked into a slot that is already gone. Account, technical, sales and service meetings routed by segment, geography and capability. Every booking writes back to the passenger record, so the diary and the pipeline are the same story.
Tell us what a journey looks like now, end to end. That conversation usually makes the scope obvious, and sometimes makes it smaller.