To scale bulk logistics profitably, you eventually have to break the assumption that throughput and headcount grow together. The commercial pipeline is full. Two new contracts just got signed. A third is in late-stage negotiation, and a fourth is expected next quarter. The tonnage profile for the next twelve months is somewhere between thirty and fifty per cent higher than what your team is handling today. And the CEO has just asked the question you were hoping to avoid for another six months: how many new people do you need to handle it?
You know the honest answer. You could justify five more operations people without breaking a sweat, and if pressed, defend eight. Each one would cost two hundred thousand fully loaded, take four to nine months to become useful, and another eighteen months before they could run a shipment window unsupervised. The math doesn’t close the way the CEO wants it to. By the time the new hires are productive, the next contract will already be signed, and you’ll be back in the same conversation.
This is the moment many commercial operations leaders in bulk commodities walk into. The business is winning commercially. The operational layer is not scaling at the same rate. The default response, hire more people, is slow, expensive, and doesn’t actually solve the underlying problem, which is that your operational leverage per person has hit a ceiling. It is the moment when the question stops being “who do we hire?” and starts being “how do we scale bulk logistics differently?”
The producers who have broken past this ceiling have done it without doubling headcount. They have done it by changing what their people spend their hours on. The question is not “how many more people do I need?” It is “what are my best people spending their hours on today, and could those hours be spent on the work that actually scales?”
This post is about the second question. It is about the specific operational choices that enable a commercial ops team to substantially scale bulk logistics throughput without a proportional increase in team size. None of them involves heroics. All of them involve a deliberate redesign of where human time is spent.
Start with a clear-eyed look at how your existing team spends its time. If you have not done this exercise recently, it is worth doing before any hiring conversation.
In a typical bulk commodity commercial operations team, a commercial ops manager, two or three coordinators, a scheduling analyst, and possibly a logistics specialist, the time allocation often looks something like this. Thirty to forty per cent on reconciliation work: matching emails to rake certificates, matching rake certificates to port intake, matching port intake to vessel loading, matching vessel loading to BL, matching BL to contract. Twenty to thirty per cent on coordination: the emails, calls, and follow-ups that keep stakeholders synchronised. Fifteen to twenty per cent on retrospective reporting: producing the weekly, monthly, and quarterly numbers that leadership expects. Ten to fifteen per cent on exception handling: the operational surprises that demand immediate attention. And whatever is left, often under ten per cent, is on actual forward planning and optimisation.
This allocation does not reflect your people. It reflects the operational environment. The work expands to fit the time because the underlying data infrastructure forces humans to act as middleware. When data does not flow cleanly between systems and between parties, humans have to reconcile. When stakeholders are not on the same page, people have to coordinate. When reports cannot be generated mechanically, humans have to produce them.
The problem with trying to scale bulk logistics in this configuration is that each additional tonne of throughput expands all those time categories proportionally. Double the tonnes, and you double the reconciliation. Double the shipments, and you double the coordination. You do not, however, double the forward planning, which is the only category of work that compounds into competitive advantage. You actually shrink it, because the other categories crowd it out.
This is why the “hire more people” default underperforms. Every new hire absorbs a share of the current allocation, which means you are buying more reconciliation, more coordination, more retrospective reporting, and some marginal increase in planning — at a price per productive hour that is substantially higher than you assume once the training cost, the management overhead, and the key-person risk (which we covered in why your logistics team’s key person risk is a board-level problem) are priced in.
The producers who have managed to scale bulk logistics throughput without scaling the team have done it by shifting the time allocation. They have pushed reconciliation, coordination, and retrospective reporting out of human hands and onto systems. And they have used the released human hours on forward planning, exception judgment, and commercial optimisation.
Let’s put rough numbers on the shift. In a team that has made this move, the typical allocation looks more like: ten to fifteen percent on reconciliation (mostly exception handling where data quality is poor), ten to fifteen percent on coordination (mostly stakeholder relationship work that genuinely benefits from human judgment), ten percent on reporting (mostly narrative and interpretation, because the numbers come out mechanically), twenty to twenty-five percent on exception handling (operational judgment calls, which remain stubbornly human), and thirty to forty percent on forward planning, optimisation, and commercial work.
That is not a small shift. It means that from the same headcount, the team is spending roughly three times as many hours on the work that scales the business. And because forward planning reduces exceptions, better exception handling reduces reconciliation, and cleaner data reduces coordination load, the shift is partly self-reinforcing once it begins.
Doubling throughput on this configuration is not only possible; it is often undemanding. The team handles more shipments without getting busier because each shipment requires less low-leverage human effort. Adding a third, a fourth, and a fifth contract in the commercial pipeline does not raise the operational panic level, because the team’s time budget has headroom for it. This is what it actually means to scale bulk logistics from inside the existing team rather than around it.
The shift is not free. It requires deliberate investment in the data infrastructure, in the process discipline, and in the cultural habits that allow people to stop doing reconciliation work that has become invisible to them. But the investment is typically a fraction of the cost of the equivalent hiring plan, and it compounds.
In our experience, five specific moves account for most of the time-allocation shift that lets producers scale bulk logistics without scaling headcount. None of them requires a multi-year transformation programme. All of them are addressable in quarters rather than years.
Reconciliation time is usually the largest single category of hours for a bulk-commodity operations team and is almost entirely invisible. People don’t describe their week as “I spent eighteen hours reconciling rail certificates to port intake records.” They describe it as “operational work.” But if you sit with a coordinator for a day and classify what they are actually doing, you will find that reconciliation dominates.
The move is to collapse the reconciliation surface. That means using canonical identifiers that survive the handoffs between systems and between parties. It means consuming provider data in a form that can be matched mechanically rather than by human judgment. It means flagging variances automatically rather than surfacing them by inspection. We went into the technical shape of this work in Commodity Traceability Done Right: A Mine-to-Vessel Quality Thread for Bulk Producers. The data thread is the same one that collapses reconciliation.
When the reconciliation surface collapses, a coordinator’s day changes character. Instead of spending the morning matching yesterday’s data, they spend it acting on today’s signals. The work is higher-leverage and more engaging. Retention improves as a side effect.
Move two: eliminate the status-chasing loop.
The second-largest category is coordination: the emails, calls, and follow-ups that keep stakeholders on the same page. A lot of this is genuinely necessary. Relationships with rail operators, ports, stevedores, surveyors, and charterers need human attention; that doesn’t change.
What changes is the status-chasing subset: the calls and emails that exist only because nobody has a shared view of what is happening. “Has the rake left yet?” “Is the berth still on plan?” “Did the surveyor arrive?” “What’s the ETA now?” Every one of those questions exists because the answer lives in a system that the asker can’t see and a mailbox the answerer hasn’t replied to yet.
Eliminating status-chasing does not require eliminating relationship management. It requires exposing the operational data to everyone who needs it, in something close to real time, in a form that answers the common questions without a phone call. We wrote about the structural version of this in why email-based bulk logistics coordination is quietly costing you millions across rail, port and vessels, the same architecture that reduces coordination cost also reduces status-chasing specifically.
In a team that has done this, the coordinators’ inboxes shrink dramatically. The calls they make are higher-quality because they are not status calls; they are substantive, context-rich calls. The human relationship with the provider improves, not degrades.
If your monthly operations report takes more than half a day to produce, it is probably coming out of human time that should be spent elsewhere. The cost of the report is often paid by the most senior operations person, the one whose hours are most valuable and whose judgment is most needed on forward work.
The move is to architect your data so that the report’s numbers are generated automatically. The report itself, the narrative, the framing, the recommendations, still require human thought, and should. But the tabulation, the aggregation, the variance calculations, the charts, the comparisons to prior periods: all of that is mechanical work. If a human is producing it by hand each month, it is stealing hours from work that matters more.
Producers who have made this move typically find that their reporting cadence becomes richer as the cost per report falls. Instead of one monthly report that takes a day, they have a weekly report that takes an hour, a daily digest that takes twenty minutes, and a real-time dashboard that takes zero. Leadership engagement with operational performance improves because the signals are fresh instead of stale. Decisions are made based on current data, not last month’s.
Exception handling, the operational surprises that demand immediate attention, is work that cannot be fully systematised. Something always goes wrong. Weather, mechanical failures, crew issues, counterparty disputes, quality surprises. These require human judgment, and always will.
What can be systematised is the triage. In most commercial operations teams, every exception lands on whoever answers the phone first, regardless of whether they are the right person to handle it. The result is that senior people end up on low-value exceptions, and junior people on high-value ones. Decision quality suffers on both sides.
Explicit triage means: every exception has a category, every category has an owner, every owner has a clear authority scope, and escalation rules are known in advance. This is not exotic process engineering; it is standard operations discipline that is frequently missing in bulk commodity teams because the historical assumption has been that experience will route work correctly. Experience does route work correctly, but it does so at a tax: the experienced person is on every exception until they explicitly choose not to be.
When triage is explicit, senior people spend their time on exceptions that require their judgment, which is a small fraction of the total. The team’s capacity to absorb exceptions without a senior bottleneck goes up substantially. Throughput scales because the exception layer scales, which is one of the cleanest expressions of what it means to scale bulk logistics through process rather than people.
If you do the previous four moves and do not protect what the released hours get spent on, you will find that the hours are absorbed back into the same low-leverage work they came from. This is the most predictable failure mode of a time-allocation shift: humans tend to fill available time with the work that feels urgent, and urgent work is almost always low-leverage reconciliation and coordination.
The move is to establish, explicitly, with the team’s participation, a minimum amount of time that each key role spends on forward planning and commercial optimisation. It can be as simple as two protected mornings a week for the commercial ops manager and one for each coordinator. The time is used on looking ahead, not looking behind.
Producers who have protected this time find that forward planning compounds. The shipments two months from now will get set up more cleanly. The contract pipeline gets stress-tested against the actual operational capacity. The margin optimisations that used to slip through get captured. And the cost of not protecting time becomes apparent by comparison; an unprotected team drifts back into reactive mode within a quarter.
Picture what the team does differently on a typical Monday morning when the goal is to scale bulk logistics rather than survive it.
In the old configuration, the first two hours are for reconciliation. The coordinators are working through weekend shipments, matching rail certificates to port intake records, flagging discrepancies, chasing surveyors for overdue certificates, updating the shipment tracker spreadsheet, and answering charterers’ emails requesting status. The commercial ops manager is producing the weekly report, pulling data from three systems, asking the coordinators for confirmations, and reconciling the top-line tonnes with what commercial expects. By lunchtime, nobody has done any forward work.
In the new configuration, the first thirty minutes are a standup that reads from the data spine. The coordinators walk through weekend exceptions, fewer than before, because the routine work was mechanically reconciled overnight, and commit to the day’s actions. The commercial ops manager reviews the weekly report that was generated automatically over the weekend, adds narrative commentary, and flags decisions for the leadership team. By mid-morning, the forward-planning work begins: the next two weeks of shipments are reviewed, risk points are identified, upstream and downstream parties are on a shared plan, and commercial optimisations are identified and executed.
The team is not working harder. It is working on different things. The tonnage moving through the chain is higher. The exception volume is lower. The relationships with providers are more professional. The leadership team is getting richer signals and making better decisions. And the next commercial contract in the pipeline does not trigger an operational panic because the system has the headroom to absorb it.
Let’s be honest about what it costs to scale bulk logistics this way. The moves described above are not free, and they are not instant. Producers who try to treat them as a pure process exercise, “we’ll just have better meetings and write better SOPs”, usually find that the gains are modest and unsustainable.
The real investment has three components.
The timeline for a visible shift is usually six to nine months. The timeline for a fully embedded shift is eighteen to twenty-four months. The gains appear earlier in specific pockets; a reconciliation task that used to take four hours now takes thirty minutes, but the full throughput-without-headcount outcome takes the full timeline to land.
The cost comparison against hiring is almost always favourable, because the investment is one-time and compounds, whereas hiring is recurring and linear. A team that has made the shift absorbs the next contract for the cost of a little additional data integration. A team that has not made the shift absorbs the next contract by hiring two more people and accepting the nine-month productivity ramp.
This work attracts a specific set of objections, each worth addressing.
Our operations are too complex for this. Often said by producers with the most to gain. Complexity is the reason the time allocation is skewed; it is not a reason to accept the skew. The moves are designed to absorb complexity, not to pretend it doesn’t exist, and they are exactly how complex producers eventually scale bulk logistics without imploding.
We tried to automate reporting, and it didn’t work. Usually, a symptom of trying to automate on top of messy data. The automation worked; the data underneath didn’t support it. The move is to fix the data first; the automation follows.
Our people will resist losing familiar work. Sometimes true. The most reliable countermeasure is to involve the people in designing the shift, and to pair the removal of low-leverage work with a clear picture of what the higher-leverage work looks like. People do not mind giving up reconciliation when the alternative is commercial optimisation. They mind giving it up when nothing fills the vacuum.
We don’t have the data infrastructure to start. This is the most honest version of the objection, and it is usually negotiable. Most of the early moves can be made on modest infrastructure. The canonical identifier work, the shared operational record, the report automation, all of these can start with the systems you have, with targeted, incremental investment rather than a platform refresh.
We’ll just hire more people while we figure it out. This is the default, and it is worth examining carefully. Every hire is a twenty-four-month commitment that locks in the current time allocation. Hiring ahead of the shift compounds the problem you are trying to solve. Hiring after the shift confirms the value. Order matters.
When the CEO asks how many more people you need to handle the new tonnage, the answer is not a number. The answer is a proposal to scale bulk logistics through leverage rather than headcount.
The proposal has three parts. First, a clear-eyed assessment of where the team’s time currently goes, with actual categories and percentages. Second, a specific plan for shifting the allocation, which of the five moves to make, in what order, at what investment, with what expected throughput impact. Third, a hiring plan that is contingent on the plan, not independent of it: the smaller number of people you need after the shift, at a more senior profile you should hire for, at a later point in the cycle, when their productivity will actually match the business need.
Good CEOs welcome this framing. They understand operational leverage and that scaling linearly with tonnage is not a strategy. Less good CEOs will push for the headcount anyway, and at that point, your job is to make sure the headcount commitment comes paired with the shift commitment, rather than instead of it.
Doubling throughput without doubling the team is not a slogan. It is the arithmetic of a specific set of operational choices, made deliberately and in the right order. The choices are available to every producer we’ve worked with. Not every producer makes them. The ones who do scale bulk logistics in a way that the hiring-first default cannot match. The ones who don’t eventually hit a wall, usually at a contract that should have been won on capacity and was instead ceded to a competitor whose operations scaled further on fewer team members.
The window to make the shift is always roughly the same window: now, before the pipeline forces the hiring decision. Starting now makes the headcount conversation a choice. Starting later makes it a constraint.
Nick Ogle has over 30 years of experience in Enterprise IT, spanning engineering, sales, and marketing roles across Australia, the USA, and APJ for various IT vendors.
Nick is passionate about entrepreneurship and Software innovation that drives positive change. Currently, he is the Sales & Marketing Manager at SCIAR Systems, a Newcastle-based SAAS startup, where he is helping commercialise their groundbreaking Bulk Commodity Logistics solutions.
For more information on Nick and to find articles that have been written on the IT sector in the past, feel free to look at his LinkedIn profile or browse some of the additional articles Nick has written for SCIAR.