Siloed regions
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
Property, logistics and infrastructure / Asset intensive enterprises
Operloom builds the operating system behind a port operator: how an commercial enquiry arrives, how it becomes a journey, and how anyone can tell afterwards what actually happened.
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
Before any of this is a technology question, it is an operating question. These are the conditions a port operator works inside, and the ones the build has to answer.
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
It lands on the CMO / CIO / commercial operations leader first, well before it shows up in any number.
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
Because long asset cycles and site-level operations that head office cannot see directly, this one compounds rather than staying still.
It tends to hold until volume rises. At that point the informal version stops working and nothing has replaced it.
02Enterprise
This is the shape the system takes for a port 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 port operator is actually run on.
Who is told, when, and what they are expected to do about it.
03Enterprise
The CRM and customer data platform holds global accounts, contacts, buying groups, territories, opportunities, contracts, partners and service relationships. Configured around how the work is actually run, rather than around the default pipeline the platform ships with.
Each passenger exists once, with the history attached rather than scattered across inboxes.
A lifecycle short enough that people update it, which is the only kind that stays accurate.
A pipeline you can read in a minute, because the fields that nobody maintains are not on it.
Source captured on the first touch, because reconstructing it later is guesswork.
Ownership is explicit, so "I thought you had it" stops being a category of loss.
Follow up scheduled when the journey is created, not when someone remembers.
Reporting out of the working system, so the numbers and the work cannot disagree.
Access matched to role, which matters as soon as more than one person is involved.
04Enterprise
Written as it actually happens rather than as a funnel diagram. The steps that matter are the handovers.
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
For a port operator the site is a working part of the system rather than a brochure in front of it. That changes what gets built.
06Enterprise
Each workflow below states what starts it, what has to be true, what it does, where a person stays in the loop and where the result lands. Automation without those five is just an undocumented side effect.
07Enterprise
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
08Enterprise
These are the measures worth reporting for a port operator. Any figures shown in charts on this site are illustrative and labelled as such: we do not publish client data.
Defined once and written down, so it means the same thing next quarter.
Tracked as a trend, because a single period rarely means anything.
Broken down by source, so the number leads somewhere.
Measured from the record rather than reconstructed at month end.
Tracked as a trend, because a single period rarely means anything.
09Enterprise
The communication a port operator sends is mostly operational rather than promotional, which is exactly why deliverability has to be right first.
10Enterprise
Where attention comes from decides where effort goes. For a port operator demand arrives through tender, framework agreements and long-standing relationships.
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
Money moves through the same records as the work. That is the whole point: what was agreed and what was billed cannot drift apart if they are the same document.
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
The diary is the constraint. account, technical, sales and service meetings routed by segment, geography and capability, and the system is built around protecting it.
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
Not every business needs every capability, and pretending otherwise is how implementations get expensive. This is the mix a port operator typically needs, split by how load bearing each part is.
CRM setup and data model supports port operator businesses by helping to connect global demand
Pipeline and lifecycle design supports port operator businesses by helping to connect global demand
Lead routing, scoring and follow up supports port operator businesses by helping to connect global demand
Website build or redesign supports port operator businesses by helping to connect global demand
Service and landing pages supports port operator businesses by helping to connect global demand
Email infrastructure and deliverability supports port operator businesses by helping to connect global demand
Email campaigns, nurture and reminders supports port operator businesses by helping to connect global demand
Analytics and conversion tracking supports port operator businesses by helping to connect global demand
Dashboards and attribution supports port operator businesses by helping to connect global demand
Client, patient or customer portal supports port operator businesses by helping to connect global demand
Help desk and service workflows supports port operator businesses by helping to connect global demand
Platform integrations and APIs supports port operator businesses by helping to connect global demand
Security, privacy and maintenance supports port operator businesses by helping to connect global demand
Multi location and franchise management supports port operator businesses by helping to connect global demand
Enterprise governance and data architecture supports port operator businesses by helping to connect global demand
Brand identity system supports port operator businesses by helping to connect global demand
Technical and on page SEO supports port operator businesses by helping to connect global demand
Content strategy and copywriting supports port operator businesses by helping to connect global demand
Documents, forms and e signature supports port operator businesses by helping to connect global demand
Workflow automation supports port operator businesses by helping to connect global demand
14Enterprise
None of this is a promise about revenue. It is a list of things that currently depend on somebody remembering, and what it would look like if they did not. Each area names the measure that would tell you.
Removing the steps between interest and a committed journey, and making the next action obvious at every point.
Measure: Account engagementBeing findable for the terms a passenger actually uses, rather than the ones the business uses internally.
Measure: PipelineKnowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: ConversionTaking 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: InfluenceBeing able to change how the work runs without needing the person who originally set it up.
Measure: Service and revenue reportingMaking the second journey as deliberate as the first, rather than leaving it to whoever remembers.
Measure: Account engagement15Enterprise
A short audit of the platforms, the data in them and the points where an commercial enquiry stalls.
Decisions made once, in writing, so the build is execution rather than a series of small arguments.
Built in the order that gets a port operator value soonest, not the order that is tidiest to build.
Integrate the platforms so CRM, ERP, product, service, identity, data warehouse, analytics and integration platforms behave as one system.
Everything written down, because a system only one person understands is a risk rather than an asset.
Tracking, dashboards and definitions, so the effect is checkable rather than asserted.
A review cadence with a short list of changes, run against the same measures each time.
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.
We are implementers, not advisers. What we do is build the controls your obligations require once they are confirmed, and make them evidenceable. What we will not do is tell you what those obligations are.
19Enterprise
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.
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.
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.
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.
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.
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.
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.
Bring the version of the process that actually happens rather than the documented one. That is the one worth designing against.