Discovery

Start with the problem the business is already trying to solve.

Mellorca Discovery looks at the operating problems businesses run into every day. Each article starts with a problem you will recognise, looks at the evidence, works out what it costs and why it happens, and sets out a practical way to fix it.

Business problemsWho it affectsRoot causeIntervention
Latest Discovery

Problems businesses keep running into.

Each article takes one recurring operational problem, shows how to recognise it, explains why it happens and what it costs, and sets out practical ways to fix it.

Inventory & Order Operations

Manual CSV imports are used to keep channel stock aligned

A daily stock file works until the range grows. Why CSV uploads fall behind, what they cannot tell a channel, and how to replace them with a process that scales.

Accounts Receivable & Collections

Sales promises payment extensions that finance cannot see

A friendly yes from an account manager can leave finance chasing a customer who has been promised more time. How to record extensions without taking flexibility away from sales.

Accounts Receivable & Collections

Collections activity is not visible to account managers

Finance chases the overdue invoice while the account manager pitches the next deal, unaware. What an account manager needs to see about collections, and how to put it in front of them.

Accounts Receivable & Collections

Recurring invoice failures are handled as isolated exceptions

Every failed recurring invoice gets fixed by hand, and the same few causes return next month. How to group failures by cause so growth stops multiplying the clean-up.

Accounts Receivable & Collections

Cash forecasts ignore real collections workflow states

A forecast built from due dates treats a promised payment and a disputed invoice alike. How to feed collections states into the cash forecast so it stops running optimistic.

Accounts Receivable & Collections

Small overdue balances consume disproportionate manual effort

Chasing a R340 balance takes as many steps as chasing R340,000. How to set balance bands, automate the small ones and fix the causes behind them.

Accounts Receivable & Collections

Collections handoffs change when staff are absent

Leave, resignations and month-end pressure quietly change how overdue accounts are chased. How to keep promises, disputes and customer preferences with the account, not the person.

Accounts Receivable & Collections

Failed direct debits do not automatically create follow-up work

A returned debit order is a payment result, not an assigned task. Connect each failure to the customer, invoice and next action before unpaid balances accumulate.

Sales Operations & CRM

Marketing leads arrive without useful qualification context

A name and an email address are not a lead sales can work. What to capture at the point of enquiry, how to hand it over, and how to feed outcomes back to marketing.

Sales Operations & CRM

Quotes move to spreadsheets when CRM pricing cannot be trusted

Salespeople build quotes outside the CRM when its prices cannot be trusted. Find the missing data and rules, restore an owned price source, and make the quote usable again.

Sales Operations & CRM

Nobody keeps customer contact roles current after the deal

Decision makers and billing contacts get recorded to win a deal, then nobody keeps them current. Here is how to prompt reviews from real events and protect renewals.

Sales Operations & CRM

Win-loss reasons in the CRM are too vague to change strategy

A pick-list filled in by the salesperson at close says "price" or "other". Redesign reasons around decisions, add a short debrief for big deals, hear from buyers and review quarterly.

Sales Operations & CRM

Sales cannot see a customer's credit or service problems

Credit holds, overdue balances and open complaints sit in finance and service systems. Here is how to bring the few signals sales needs into the customer record.

Sales Operations & CRM

Lead response rules treat a demo request like a download

Routing rules treat every lead the same, so buyers with a deadline wait behind casual enquiries. Tier leads by urgency, set targets per tier and escalate what nobody picks up.

Data, Reporting & Decision Systems

Customer identity differs across analytics domains

Marketing, finance and support each count customers differently. Why identity fragments across domains and how a shared definition and identifier produce one defensible number.

Inventory & Order Operations

Why safety stock rules differ between sales channels

The planner protects a buffer, but each channel publishes its own figure and sells it. How to define sellable stock once and allocate buffers on purpose.

Inventory & Order Operations

Why sales teams cannot check live stock while the customer waits

Reps phone the warehouse before every large quote because the stock figure in front of them is hours old. What a dependable availability lookup needs, and how to build it in stages.

Inventory & Order Operations

Drop-ship stock is counted as if it sits in your own warehouse

When supplier-shipped lines share item codes, locations and reports with owned goods, stock counts, availability and valuation all drift. How to separate the two flows cleanly.

Inventory & Order Operations

Why a cancelled order keeps its stock locked away

A customer cancels, but the units stay committed to an order that no longer exists. Where the release step gets lost between channels and how to close the loop.

Inventory & Order Operations

Why pickers are sent to fetch orders that have already changed

Short picks, wrong quantities and abandoned work usually trace back to a gap between releasing an order and the customer changing it. How to shrink that gap.

Inventory & Order Operations

Finance and operations report different stock ageing for the same goods

Slow-moving stock gets provided for on one number and discussed on another. Why ageing differs by date basis, location and cost, and how to agree one method.

Inventory & Order Operations

New SKUs go on sale before every system has the product data

A product that exists in the catalogue but not in the warehouse, pricing or finance systems produces manual fixes on day one. A release routine that avoids it.

Inventory & Order Operations

Stock exceptions are only found when month-end arrives

Negative balances, odd adjustments and phantom stock sit unnoticed for weeks and then hold up the close. How exception checks and targeted counts catch them while they are small.

Accounts Receivable & Collections

Disputes are tracked separately from invoice status

A customer disputes one line, the invoice stays overdue, and the reminders keep coming. How to give every dispute a status, an owner and a visible link to the invoice so collections and DSO make sense.

Sales Operations & CRM

Account hierarchies do not reflect real customer relationships

Head offices, branches, subsidiaries and buying groups all appear as unrelated accounts in the CRM. How to model real customer relationships before a system change copies the mess into a new platform.

Data, Reporting & Decision Systems

Spreadsheet extracts become unofficial reporting systems

A one-off export for a meeting becomes the monthly pack, then the number the board quotes. How to spot the shadow reporting layer, decide what to keep, and move the numbers that matter onto a governed source.

Integration & API Operations

Webhook failures are not replayed safely

When a webhook is missed, a person re-sends it from a dashboard and hopes nothing is applied twice. How to store events, recognise repeats, reconcile daily and replay with confidence.

SaaS & Application Portfolio Management

Expense-card software purchases bypass central visibility

Small subscriptions on company and expense cards never pass through procurement, so the application list is incomplete. How to find them, register them and keep visibility without slowing managers down.

Security & Compliance Operations

Security exceptions have no clear compensating controls

Exceptions to security standards are often approved in an email with no substitute protection and no end date. How to build a register that stands up to an insurer, customer or auditor.

Business Continuity & Resilience

Recovery plans list systems but not the business services they support

A recovery plan that lists servers cannot tell you which service comes back first. How to map services to systems, agree recovery times with managers and reorder the plan before a major incident.

Quote-to-Cash & Revenue Operations

One-off implementation fees are forgotten during billing setup

The monthly subscription gets billed on time, but the set-up fee agreed in the quote quietly disappears. How to make one-off charges part of the billing handover so they are invoiced once, correctly.

Quote-to-Cash & Revenue Operations

Quote revisions create duplicate or contradictory order instructions

A repriced quote, a second email and a re-keyed order can produce two instructions for one job. How numbered revisions, acceptance against a version and a block on second orders prevent it.

Quote-to-Cash & Revenue Operations

Why tax and currency are still corrected by hand after the invoice goes out

When VAT treatment and exchange rates are fixed manually downstream, every correction is a potential billing dispute. How to move the rules upstream and give each correction an owner.

Quote-to-Cash & Revenue Operations

Why cancelled and reduced orders take so long to reach the revenue forecast

A customer halves an order and the forecast still shows the original number at month end. How to close the gap between operational changes and the revenue view leadership relies on.

Quote-to-Cash & Revenue Operations

Why usage-based billing data never quite matches the customer contract

Usage records arrive from one system and contract terms sit in another, so every metered invoice needs a human to reconcile them. How to connect the two and stop the disputes.

Quote-to-Cash & Revenue Operations

Why account managers cannot see where their customers' orders stand

Account managers who cannot see order status spend their day asking colleagues and calming customers. What a simple shared status view looks like and who has to own it.

Quote-to-Cash & Revenue Operations

Why pricing rules end up copied across the CRM, spreadsheets and the ERP

When discounts, tiers and price lists are maintained separately in each tool, quotes and invoices disagree. How to pick one source for pricing rules and keep the others honest.

Inventory & Order Operations

Reserved stock is treated as available stock

When a quote, an online basket or a held order reserves stock in one place but not another, the same unit gets promised twice. How to separate on-hand, reserved and available quantities.

Inventory & Order Operations

Why damaged stock keeps showing as available to customers

Cracked, returned or quarantined units are still on the shelf, so the shop keeps selling them. How to give damaged stock its own status that every sales channel respects.

Inventory & Order Operations

Why warehouses with different location codes cannot share stock data

When each warehouse names its shelves and bins its own way, transfers go astray and group reports need translation. A simple convention and the governance to keep it.

Inventory & Order Operations

Why sales and warehouse systems need one product identifier

One product, three codes: the web shop, warehouse and accounts each name it differently, and stock lands on the wrong item. How to give each product one identity.

Inventory & Order Operations

How bundles and kits distort component stock counts

A bundle sells as one line but consumes several parts, so component counts drift and the scarcest part oversells. Choosing a bundle model and keeping one recipe.

Inventory & Order Operations

Why goods received do not reach customer availability promptly

Stock arrives in the morning but customers still see it as unavailable the next day. How to shorten the path from dock to sellable figure.

Inventory & Order Operations

Why stock in transit between locations goes missing in reconciliation

Stock leaves one branch and never quite arrives in the books. How to model transit, tie shipment to receipt and clear open transfers daily.

Inventory & Order Operations

Why cycle-count adjustments need a recorded root cause

Counting finds the difference, but booking it away teaches nothing and the same variance returns. How reason codes and a monthly review turn counts into fixes.

Quote-to-Cash & Revenue Operations

Discount approvals happen outside the quoting system

When a manager approves a discount by message and the quote shows only the final price, finance cannot tell what was agreed or why. How to bring approvals into the quote record.

Quote-to-Cash & Revenue Operations

Orders are created with values that differ from the accepted quote

When order entry starts afresh instead of carrying the accepted quote forward, prices, discounts and fees drift. How to measure the gap and make the quote the source of the order.

Inventory & Order Operations

Warehouse adjustments do not reach ecommerce systems quickly

A cycle count corrects the warehouse system, but the online shop keeps selling the old number. Why stock adjustments lag and how to make corrections flow to every sales channel.

Accounts Receivable & Collections

Customers receive reminders for invoices they already paid

A reminder for an invoice that was settled last week annoys good customers and wastes collections time. Why payment status lags behind reminders and how to stop it.

Sales Operations & CRM

Opportunities remain open long after buyers go quiet

Deals that have not moved for months still count toward the forecast because nobody closes them. How to set stale-deal rules that keep the pipeline honest.

Data, Reporting & Decision Systems

Reports depend on undocumented manual transformations

Monthly packs often rely on hidden clean-up steps known to one person. How to find those steps, move fixes to the source and make the report reproducible.

Integration & API Operations

The same customer data is integrated through several different interfaces

When customer data is wired into each application separately, the copies drift apart. How to map the connections, name an owning system and consolidate.

Security & Compliance Operations

Customer security questionnaires consume specialist time

Every enterprise deal now arrives with a security questionnaire that lands on the same two people. How to build an answer library, assign ownership and stop re-answering the same questions.

Security & Compliance Operations

Privileged accounts are reviewed without application context

Quarterly lists of admin accounts get approved without anyone knowing what the access allows. How to add application context so reviews remove access.

Security & Compliance Operations

Remediation tickets close without verifying the underlying control

Closing a ticket proves a task was claimed, not that the weakness is gone. How to require evidence, retest automatically and track findings that come back.

Security & Compliance Operations

Security controls are duplicated across teams

When each team runs its own version of the same control, effort and evidence multiply and answers conflict. How to build one catalogue with single owners.

Security & Compliance Operations

Security monitoring creates alerts with no business-priority context

Security tools rank alerts by technical severity, not by what the business can least afford to lose. How to tell the tool and the team which few systems matter most.

Security & Compliance Operations

Audit evidence cannot be reproduced from the original source

When proof of a control is a screenshot or an edited export, customers and auditors cannot confirm it. How to name the source of record and capture evidence that can be re-run.

Security & Compliance Operations

Control testing schedules are maintained in personal calendars

When the only record of when controls must be tested is someone's diary, tests are missed and nobody knows. How to move to a shared control register with owners and deputies.

Security & Compliance Operations

Incident lessons do not update preventive controls

Incident reviews often end in a report while the procedures and settings stay as they were. How to turn lessons into dated, verified control changes so the same incident does not return.

Quote-to-Cash & Revenue Operations

Accepted quotes do not automatically create fulfilment work

A customer says yes, but nothing in the business starts until someone notices. How to make acceptance a recorded event that creates orders, jobs and billing without retyping.

Inventory & Order Operations

Online channels sell stock that the warehouse no longer has

Web shops and marketplaces show a copy of stock that is already out of date. How to publish available rather than on-hand quantity, reserve at order creation and stop cancelling paid orders.

Accounts Receivable & Collections

Collections teams chase customers without a reliable priority queue

An ageing report shows what is old, not which call is worth making. How to segment the debtors ledger, separate disputes and build a daily ranked contact list that moves cash.

Sales Operations & CRM

Salespeople update the CRM only before forecast meetings

When deals are updated once a month, the forecast is a reconstruction. How to find the cause before blaming people or replacing the CRM.

SaaS & Application Portfolio Management

AI add-ons increase software spend outside original budgets

Per-user AI tiers and optional add-ons arrive as small recurring charges that no approval process catches. How to find them, test their value and bring them inside the budget.

SaaS & Application Portfolio Management

Paying for unused software features because contracts are bundled

Suites and tiers bundle features nobody uses, and the cost surfaces only in a merger or renewal. How to break a contract into features, usage and owners.

SaaS & Application Portfolio Management

Why application inventories leave out shadow IT and AI tools

An inventory built from purchase orders cannot see the tools people adopt themselves, including AI assistants. How to find them and keep the list true.

SaaS & Application Portfolio Management

New SaaS purchases create integrations nobody budgets to maintain

The build is funded, the upkeep is not. How to count, own and budget the connections each new SaaS purchase adds, before a merger or vendor change exposes them.

SaaS & Application Portfolio Management

Why single sign-on coverage lags behind the SaaS portfolio

Each new SaaS tool arrives with its own passwords while sign-in controls stay on a few core systems. How to measure SSO coverage and close the gap in a sensible order.

SaaS & Application Portfolio Management

Vendors change packaging and pricing faster than budgets adapt

Vendors can repackage and reprice at any renewal, while budgets are set once a year. How to keep a commitment register and a budget that can absorb the change.

SaaS & Application Portfolio Management

Critical workflows depend on low-code apps built by departed staff

Low-code apps and automations are often owned and credentialed by their creator. When that person leaves, the workflow becomes an orphan. How to find, own and hand over the ones that matter.

SaaS & Application Portfolio Management

Applications are retained because migration effort is unknown

Duplicate and ageing applications survive renewal after renewal because no one has estimated the cost of moving. How to size migration effort cheaply and make keep-or-retire decisions on purpose.

SaaS & Application Portfolio Management

Renewal calendars are disconnected from architecture roadmaps

The roadmap says retire, but the contract renews for another year. How to join renewal dates and notice deadlines to the technology plan, especially as AI tools multiply.

Security & Compliance Operations

Control owners cannot produce evidence without manual searching

When proof that a control operated lives in inboxes and personal folders, every audit becomes a search exercise. How to capture evidence as the work happens and retrieve it on demand.

Security & Compliance Operations

Risk acceptances expire without reassessment

An accepted risk is only sound at the moment it is accepted. How to give every acceptance an expiry date, recorded assumptions and a reassessment, before a customer asks.

Cloud, Infrastructure & Platform Operations

Why platform logs pile up without anyone knowing what they are for

Many businesses collect and store large volumes of system logs, yet cannot find the right evidence during an outage. How to give every log source a purpose, an owner and a retention period.

Cloud, Infrastructure & Platform Operations

When your cloud accounts reflect history instead of who owns what

Cloud accounts and subscriptions often grow one project at a time, so their structure mirrors old decisions rather than today's owners and workloads. Why that blurs cost, access and risk, and how to restructure.

Cloud, Infrastructure & Platform Operations

Why patch exceptions stay open long after anyone remembers the reason

Servers and applications excluded from patching for a good reason often stay excluded for years. Why patch exceptions drift into permanent risk, and how to give each one an owner, an expiry date and an exit plan.

Cloud, Infrastructure & Platform Operations

When monitoring produces more alerts than your team can triage

Cloud monitoring can generate hundreds of alerts a week, most needing no action. How alert noise hides real incidents, drives up cost, and how to cut it back to signals people act on.

Cloud, Infrastructure & Platform Operations

Why critical services end up depending on one cloud region by accident

Many businesses run production, backups and hidden dependencies in a single cloud region without ever deciding to. How that happens, what it risks, and how to choose resilience deliberately.

Cloud, Infrastructure & Platform Operations

Why infrastructure diagrams are out of date as soon as the project ends

Infrastructure diagrams drawn at project handover go stale within weeks. Why it happens, what it costs during incidents and audits, and how to keep a picture of your environment you can trust.

Cloud, Infrastructure & Platform Operations

Why cloud managed services get adopted without an exit plan

Cloud migrations lean on managed databases, queues and serverless tools without recording what leaving would cost. How to make lock-in a deliberate, priced choice with a practical exit plan.

Cloud, Infrastructure & Platform Operations

Why cloud resource quotas are only discovered when a deployment fails

Cloud and cluster quotas stay invisible until a release or scaling event hits them. How quotas work, what surprise limits cost, and how to monitor and raise them before they cause failures.

Cloud, Infrastructure & Platform Operations

Why platform teams still build every environment request by hand

When every test or development environment is requested by ticket and built manually, platform teams drown in repetitive work and environments drift. How to move to governed self-service.

Cloud, Infrastructure & Platform Operations

Why infrastructure incidents cannot be linked to the change that caused them

Most outages follow a change, yet many teams cannot see what changed before an incident. How scattered change records slow recovery, and how to build a change timeline that speeds it up.

SaaS & Application Portfolio Management

Why departments buy overlapping software for the same capability

Marketing, operations and HR each buy their own forms, project or e-signature tool. The fix is not a purchasing ban but a capability map that is checked before anything new is bought.

Security & Compliance Operations

Why third-party security reviews keep starting from scratch

Each new contract, renewal or audit triggers a fresh supplier questionnaire, and last year's answers cannot be found. Here is how to make supplier assurance reusable.

Security & Compliance Operations

Why IT asset registers miss cloud and SaaS services

Asset registers built around hardware often omit the SaaS applications and cloud resources that hold most business data. How to close the gap before an audit finds it.

Security & Compliance Operations

Access logs that disappear before the auditor asks for them

Sign-in and audit logs are often switched on but kept only for platform-default periods. How to set retention by control need, close the gaps and prove it works.

Security & Compliance Operations

When every system owner reads the same compliance rule differently

General policy wording leaves each system owner to decide what compliance means, producing several versions of one control. How to set one interpretation and apply it everywhere.

Integration & API Operations

Why your integrations multiply faster than your applications

Each new system gets its own direct connections to the others, until the links outnumber the applications many times over. Why point-to-point integration grows this way and how to bring it back under control.

Integration & API Operations

Why manual file transfers survive inside otherwise automated processes

Downloading a file from one system and uploading it to another is often the only manual step left in an automated process. Why it survives, what it costs and how to close the gap.

Integration & API Operations

Why integrations pass testing and then fail in production

When test environments use different versions, stubs or sandboxes from production, integrations pass testing and fail on go-live. How to close the gap without cloning everything.

Integration & API Operations

Why internal teams cannot find the APIs your business already has

When nobody can find the APIs a business already owns, teams rebuild them, scrape screens or fall back to spreadsheets. How an API inventory with owners and descriptions fixes it.

Integration & API Operations

When file names and folders quietly run your integrations

When a file's name or folder decides which process runs, a renamed file can stop an integration without any error. How to find, specify and monitor these hidden rules.

Integration & API Operations

When teams consume events without knowing their delivery guarantees

Events can arrive twice, late, out of order or not at all, depending on the platform and settings. Why consumers need to know the delivery guarantee, and how to publish it.

Cloud, Infrastructure & Platform Operations

Why development environments keep running after projects stop

Test and development servers are created quickly for a project, then left running at nights, weekends and long after go-live. Schedules and expiry dates stop paying for idle environments.

Cloud, Infrastructure & Platform Operations

Why servers get upsized when nobody trusts the utilisation data

After a slowdown, the safe-looking fix is a bigger server, because nobody trusts the utilisation graphs. Why the data is often incomplete, and how to make it good enough to decide on.

Cloud, Infrastructure & Platform Operations

Why inconsistent cloud resource names and tags cause problems as you grow

When cloud resources are named and tagged however each person prefers, costs cannot be allocated, incidents take longer and clean-up is risky. How to set and enforce a simple standard.

Cloud, Infrastructure & Platform Operations

When monitoring alerts fire and nobody knows who should respond

Alerts that go to a shared mailbox or a whole team often get no response, because everyone assumes someone else has it. How to give every alert an owner, an action and a route.

Cloud, Infrastructure & Platform Operations

Why infrastructure changes get made without recording the business impact

Cloud and server changes are usually logged technically, but rarely say which business service they affect or why. How to add a short business impact record to every infrastructure change.

Cloud, Infrastructure & Platform Operations

Why certificates expire when nobody clearly owns their renewal

An expired TLS certificate can take a website, API or integration offline in an instant. Why expiry keeps happening when ownership is unclear, and how to give every certificate an owner and a renewal path.

Cloud, Infrastructure & Platform Operations

Why old DNS records pile up after services are retired, and why it matters

When a website, app or cloud service is switched off, its DNS records often stay behind. Those leftovers can be taken over by attackers. How to keep DNS in step with the services you actually run.

Cloud, Infrastructure & Platform Operations

When capacity planning only happens after something has gone down

Many businesses add server, database or cloud capacity only after a slowdown or outage. Why reactive capacity planning keeps repeating, and how to plan ahead using business events and real usage data.

Cloud, Infrastructure & Platform Operations

Why manual changes keep bypassing your infrastructure-as-code

Infrastructure-as-code promises a reliable record of your environment, but quick console fixes make reality drift away from the code. Why it happens, what it costs and how to bring changes back through the code.

Data, Reporting & Decision Systems

Why data-quality problems are found only after the report has gone out

When a reader spots duplicated sales or missing branches after the pack is circulated, the correction costs credibility. How to test data before reports are published.

Data, Reporting & Decision Systems

Why master data changes break downstream reports without warning

A new product category or a reshuffled sales region can quietly distort every report that depends on it. Why reference-list changes go unnoticed, and how to make them visible before month-end.

Data, Reporting & Decision Systems

Why last year's figures keep changing when reporting logic is overwritten

A churn figure reported to the board in March reads differently in September for the same year. How overwritten rules and attributes rewrite history, and how to make changes to the past deliberate and visible.

Data, Reporting & Decision Systems

When KPI definitions live in slide decks instead of the reporting model

The definitions slide at the back of the board pack describes how KPIs should be calculated. The reports may calculate them differently. Why definitions drift from logic, and how to make them one and the same.

Data, Reporting & Decision Systems

Why the data pipelines behind your dashboards need an operational owner

The overnight loads that feed management dashboards are often built as projects and never handed over. Why reporting pipelines end up ownerless, and how to give them an owner, a freshness target and alerts.

Data, Reporting & Decision Systems

Why system timestamps put transactions in the wrong reporting period

Online orders stored in UTC, invoices in local time, and reports that group by whichever date they receive. How timestamps make period totals disagree, and how to set one clear rule for every measure.

Data, Reporting & Decision Systems

When manual overrides in reports look exactly like source data

Adjustments typed into a reporting spreadsheet carry no author, reason or expiry, and soon nobody can tell measured figures from judgements. How to keep overrides possible but visible and traceable.

Data, Reporting & Decision Systems

Why routine data access requests take days instead of hours

Analysts wait days for approval to use data they are entitled to, so board packs slip and spreadsheets get emailed around. How owned, pre-approved access bundles make the safe route the fast route.

Data, Reporting & Decision Systems

Why sensitive customer and staff data ends up in analysts' spreadsheets

ID numbers, salaries and bank details often leave governed systems inside analyst exports. Why it happens, what it risks under POPIA, and how to give analysts what they need without the copies.

Data, Reporting & Decision Systems

Why reports keep recalculating figures your systems already produce

When reports rebuild margin, ageing or stock value that the ERP or warehouse already calculates, numbers drift and effort doubles. How to spot duplicated logic and move reports onto shared calculations.

Data, Reporting & Decision Systems

When a drop in the numbers is late data, not a business problem

Management reports often cannot show whether a fall in sales or output is real or just data that has not arrived yet. How to build freshness and completeness signals into the figures leaders act on.

Data, Reporting & Decision Systems

When a new business unit invents its own metrics before group definitions exist

New divisions, branches and acquisitions start reporting with their own KPIs, and the board pack inherits the mismatch. How to give new units a definition starter kit before their reporting sets in stone.

Data, Reporting & Decision Systems

Why data lineage gets rebuilt by hand every time the auditors arrive

When auditors ask how a reported figure was produced, many teams spend weeks piecing together the path from source to report. How to capture lineage as data moves, so audit evidence already exists.

Data, Reporting & Decision Systems

Why dashboards keep running after the process they measure has changed

A process is redesigned, but its dashboard keeps measuring the old steps and statuses. Why reports drift out of step with operations, and how to tie dashboard reviews to process change.

Data, Reporting & Decision Systems

How to find out which of your reports anyone actually uses

Report libraries grow until nobody knows which reports matter. Where usage evidence comes from, why it is easy to misread, and how to turn it into a smaller, trusted set of reports.

Quote-to-Cash & Revenue Operations

Why salespeople cannot see whether an order has actually been fulfilled

The CRM says the deal is won, but delivery and invoicing happen in other systems. Without status flowing back, salespeople phone the warehouse to answer customers.

Quote-to-Cash & Revenue Operations

Why recurring billing is still set up by hand after a deal closes

When contract terms are retyped into billing after a deal is won, missed start dates and escalations repeat for years. How to turn closed deals into billing schedules directly.

Quote-to-Cash & Revenue Operations

Why credit checks happen after sales has already promised delivery

When credit is checked only once an order reaches finance, sales has already made promises the business may have to break. How to move the credit decision to the point of commitment.

Quote-to-Cash & Revenue Operations

When every sales team builds its own version of the same product bundle

When branches and channels each define their own version of a bundle, stock, invoicing and margin reporting drift apart. How to govern bundles without slowing sales.

Quote-to-Cash & Revenue Operations

Why finance cannot trace an invoice back to the deal that approved it

When an invoice cannot be linked to the quote, discount and sign-off behind it, every query becomes an investigation. How to keep the approval attached from deal to bill.

Quote-to-Cash & Revenue Operations

Why every upsell means rebuilding the customer's deal from scratch

When adding a product to an existing customer means recreating their whole commercial record, upsells are slow and billing goes wrong. How to amend the live agreement instead.

Quote-to-Cash & Revenue Operations

Why you cannot measure the time from accepted quote to first invoice

Most businesses know their sales pipeline and their debtors' days, but not how long a won deal waits before it is billed. Why the gap is invisible and how to measure it.

Quote-to-Cash & Revenue Operations

Why revenue leakage only shows up at month-end reconciliation

When unbilled work, wrong prices and missed charges surface only at month-end, much of the money is hard to recover. How to check billing completeness daily instead.

Data, Reporting & Decision Systems

Why sales, finance and operations each define revenue differently

Sales counts signed deals, operations counts shipments and finance counts recognised revenue. Each figure is right for its purpose, but without a bridge the business argues about which one is true.

Data, Reporting & Decision Systems

Why dashboards refresh at different times without anyone knowing

When one dashboard updated at 6am and another last night, the same meeting sees two versions of the business. Why refresh timing is invisible and how to make data freshness visible.

Data, Reporting & Decision Systems

Why analysts keep rebuilding the same data joins in separate spreadsheets

When every analyst matches customers, products and transactions in their own workbook, the same numbers come out differently. How to build the joins once and share them.

Data, Reporting & Decision Systems

Why business users cannot trace a dashboard number back to its source

When a manager asks where a dashboard figure comes from and only the report builder can answer, trust erodes. How to give the people reading the dashboard a path to the source.

Integration & API Operations

Why retry logic creates duplicate transactions at the receiving end

Webhooks, queues and partner APIs deliver the same message more than once by design. When the receiving system cannot recognise a repeat, one payment or order becomes two.

Integration & API Operations

Why batch integrations leave your systems hours out of date

Nightly and hourly integration jobs mean stock, orders and customer records disagree for hours. The answer is not real time everywhere, but the right timing for each flow.

Integration & API Operations

Why teams cannot trace one business transaction across several systems

When a customer asks what happened to an order, staff search four systems by four different reference numbers. A shared business reference carried through every system turns that hunt into a lookup.

Quote-to-Cash & Revenue Operations

When sales and finance work from different product and price data

Quotes go out at one price and invoices at another because the CRM and the ERP hold separate product and price lists. Why it happens, what it costs, and how to give pricing one owner.

Data, Reporting & Decision Systems

Why executives get different answers to the same KPI question

Ask finance, sales and operations for the same KPI and three numbers come back. Why it happens when a board pack is due, and how a certified KPI catalogue and a single answer route fix it.

Integration & API Operations

APIs change without downstream teams being warned

Renamed fields and retired values break integrations when nobody tells the teams that depend on them. How to register API consumers, define breaking changes and give proper notice.

Integration & API Operations

Why integration costs stay hidden inside application projects

Integration work is usually budgeted as a line inside each new application project, so its real build and running cost is never seen. How that distorts decisions, and how to make it visible.

Cloud, Infrastructure & Platform Operations

Infrastructure resources that exist without a clear business owner

Servers, cloud subscriptions and storage that nobody will claim keep running and costing money. Why ownership gets lost, especially during cloud migration, and how to make it a condition of existence.

SaaS & Application Portfolio Management

Business capabilities that depend on tools nobody supports

Quoting, collections or payroll often rest on a tool with no named support owner. Budget cuts and vendor changes expose the gap. How to map capabilities to tools and assign support.

SaaS & Application Portfolio Management

Data-export limits are discovered only when leaving a vendor

Incomplete exports, deletion timelines and missing contract terms turn software exits into a race. How to map, test and negotiate data export before you need it.

Security & Compliance Operations

Why security findings end up in spreadsheets after the scan finishes

Vulnerability scans run, the results are exported to a spreadsheet, and remediation stalls. Why spreadsheet tracking fails audits and lets risk linger, and what a workable alternative looks like.

AI, Automation & Agent Operations

AI outputs are accepted without defined review thresholds

When nobody decides which AI outputs need checking and how closely, review drifts to habit. How to set consequence-based review thresholds and enforce them in the workflow.

AI, Automation & Agent Operations

Automation success is measured by runs rather than business outcomes

Run counts and hours-saved estimates make automation programmes look busy without proving a result. How to define, baseline and report the business outcome each automation should change.

AI, Automation & Agent Operations

Prompt and configuration changes made without version control

When prompts, model settings and automation configuration are edited in place with no history, behaviour changes cannot be explained, reviewed or rolled back. How to bring them under version control.

AI, Automation & Agent Operations

Business rules are hidden inside AI prompts

Discount limits, approval rules and eligibility written into AI prompts are invisible, untested and not reliably enforced. How to extract them and put them where they can be owned.

AI, Automation & Agent Operations

When automation platforms multiply without architectural standards

Low-code flows, RPA bots, integration tools, scripts and AI agents accumulate with no rules on which to use for what. Why that makes automation fragile and costly, and how a short set of standards fixes it.

AI, Automation & Agent Operations

AI-generated decisions cannot be traced to source data

When AI tools keep the answer but not the evidence, challenged decisions cannot be explained. How to design decision records that link AI outputs to source data, rules and approvers.

AI, Automation & Agent Operations

Retired processes leave orphaned automations running

When a process, branch or system is retired, the automations built around it often keep running. How to find orphaned automations, assign ownership and retire them safely.

AI, Automation & Agent Operations

Automation retries create duplicate customer or financial actions

A focused examination of how retry logic in automation can generate duplicate customer records and duplicate financial actions, with practical guidance on achieving idempotent behavior and safer retry strategies.

AI, Automation & Agent Operations

Automation incident response is improvised

Discovery article examining how incident response automation is improvised across teams, the risks this creates, and practical governance steps to improve reliability.

AI, Automation & Agent Operations

Automation candidates are chosen by novelty instead of business value

A focused exploration of why automation initiatives are often selected for novelty rather than demonstrable business value, and how to implement value-driven prioritization for automation portfolios.

Integration & API Operations

Message schemas evolve without version control

Explains how evolving message schemas without version control creates integration risk and operational uncertainty; outlines observable symptoms and practical interventions.

AI, Automation & Agent Operations

The same workflow is automated independently by multiple teams

A governance gap emerges when several teams independently automate the same workflow, duplicating effort, fragmenting visibility, and increasing risk. This article explains the problem, why it matters now, and practical steps to unify automation strategy without stifling teams.

AI, Automation & Agent Operations

Agent permissions are broader than the task requires

Explains how overly broad permissions in automated agents create risk and friction, and outlines practical steps to enforce least-privilege access across automation layers.

Integration & API Operations

API credentials are shared across unrelated integrations

Analyzes why sharing credentials across integrations undermines security and resilience, and how to enforce separation and robust secrets management.

SaaS & Application Portfolio Management

Application owners leave without transferring responsibility

Examines how handoffs fail when ownership is not transferred, creating drift and risk in application portfolios.

AI, Automation & Agent Operations

Teams cannot tell which processes are safe to automate end to end

Highlights the ambiguity around process safety for end-to-end automation and practical ways to establish defensible automation boundaries.

AI, Automation & Agent Operations

AI evaluations are performed only before launch

Discusses the gap created when AI evaluations are restricted to pre-launch, neglecting ongoing monitoring and governance of deployed AI systems.

AI, Automation & Agent Operations

Manual work persists because automation covers only the happy path

Discovery of automation gaps where only the ideal workflow is automated, leaving exceptions to manual effort and creating bottlenecks.

AI, Automation & Agent Operations

Automations break when application interfaces change

Discovery of fragile automation tied to evolving interfaces, causing failures when APIs or UI flows update.

AI, Automation & Agent Operations

AI usage costs are not allocated to business outcomes

Discovery of misalignment between AI spending and measurable business outcomes, hindering optimization and accountability.

AI, Automation & Agent Operations

Human exception queues grow faster than automated throughput

Discovery of escalating human-driven exceptions that outpace automated processing, signaling gaps in automation breadth and governance.

AI, Automation & Agent Operations

Agent conversations are not connected to durable business records

Discovery of disconnected agent dialogues from durable business records, undermining traceability and governance.

AI, Automation & Agent Operations

Why AI Agent Handoffs Need Enough Business Context

Why a technically correct escalation still fails when the human recipient has to reconstruct the workflow state and decision context.

Integration & API Operations

Why Integration Failures Should Not Route to Personal Inboxes

Why integration exceptions need durable queues, ownership and recovery controls rather than dependence on individual email accounts.

SaaS & Application Portfolio Management

Why Software Portfolio Decisions Need Business Value, Not Only Licence Counts

Why application rationalisation needs capability, dependency and outcome evidence alongside usage and licence data.

Security & Compliance Operations

Why Security Architecture Decisions Need Linked Risk Exception Records

Why security design decisions and accepted exceptions need a traceable relationship so risk remains reviewable over time.

Integration & API Operations

Why Critical Integrations Need a Named Operational Owner

Why business-critical interfaces need durable responsibility for monitoring, incidents, change and lifecycle decisions.

AI, Automation & Agent Operations

Why Critical Low-Code Automations Need Support Ownership

Why maker-built workflows need an explicit support model when they become business-critical.

Integration & API Operations

Why API Rate Limits Create Intermittent Business Failures

Why rate limiting needs deliberate queue, pacing, retry and business-completion controls.

SaaS & Application Portfolio Management

Why Free Trials Become Production Dependencies

Why experimentation needs a visible transition into ownership, authorization and lifecycle governance.

Security & Compliance Operations

Why Compliance Evidence Should Not Depend on Screenshots

Why assessment evidence needs provenance and reproducibility rather than disconnected image files.

SaaS & Application Portfolio Management

Why Application Costs Cannot Be Allocated to Business Units

Why technology spend needs durable mappings between billing structures, applications and business responsibility.

AI, Automation & Agent Operations

Why Automations Should Not Run on Personal Credentials

Why production workflows need governed workload identities rather than employee accounts.

AI, Automation & Agent Operations

Why AI Tools Fail Without Authoritative Data

Why AI needs governed access to trusted systems of record before it can perform reliable operational work.

Integration & API Operations

Why Integration Incidents Require Several Vendors to Diagnose

Why end-to-end transaction tracing and ownership matter when every platform appears healthy in isolation.

SaaS & Application Portfolio Management

Why Legacy Applications Remain Live Without an Owner

Why application retirement requires ownership, dependency evidence and a controlled decommission decision.

Security & Compliance Operations

Why Policy Acknowledgements Need a Reliable System Record

Why policy evidence should be version-aware, reproducible and governed rather than reconstructed from scattered records.

AI, Automation & Agent Operations

Why Bots Fail When Upstream Data Formats Change

Why critical automations need explicit data contracts, visible exception paths and monitoring when source applications evolve.

Integration & API Operations

Why Failed Integration Messages Sit in Queues Until a User Notices Missing Data

Why dead-letter queues need operational ownership, alerting and safe recovery rather than acting as invisible holding areas.

SaaS & Application Portfolio Management

Why Software Renewals Need a Confirmed Business Owner

Why renewal decisions should connect application ownership, capability, usage and risk before contractual notice windows close.

Security & Compliance Operations

Why Supplier Access Survives After the Supplier Engagement Ends

Why external access needs sponsorship, expiry and lifecycle reviews tied to the underlying supplier relationship.

Integration & API Operations

Why Undocumented Interface Mappings Make Integration Change Risky

Why durable interface contracts and mappings reduce dependency archaeology during application change and incidents.

AI, Automation & Agent Operations

Why AI Agents Can Answer Questions but Cannot Complete Work Across Business Systems

Why agent value depends on governed tools, integrations, permissions, workflow state and exception handling—not conversational ability alone.

Integration & API Operations

Why Integration Monitoring Can Show Green While the Business Transaction Still Fails

How component uptime can hide incomplete orders, leads, invoices and other cross-system transactions.

SaaS & Application Portfolio Management

Why Businesses Cannot Produce a Complete List of the Applications They Use

Why distributed software acquisition creates cost, security and architecture blind spots without a living application portfolio.

Security & Compliance Operations

Why Vulnerability Severity Needs Business Criticality

Why remediation priority improves when technical severity is connected to exploitability, service criticality and business exposure.

SaaS & Application Portfolio Management

Why Application Risk Assessments Cannot Be One-Time Reviews

Why application risk changes as data, integrations, users, ownership and business criticality evolve.

Identity & Access Lifecycle

Why New Employees Wait Days for Access to the Systems They Need

Why onboarding access delays are an identity-lifecycle design problem.

Procurement & Supplier Operations

Why Procurement Requests Disappear Into Email and Chat

How unstructured procurement intake turns email into a workflow engine.

Contracts & Obligation Management

Why Contract Renewals Surprise Finance and Operations

Why renewals and notice windows should not depend on memory and spreadsheets.

Quote-to-Cash & Revenue Operations

Why Sales Quotes Have to Be Re-Keyed Before an Order Can Start

Why re-keying accepted quotes into order systems is a broken transaction handoff.

Inventory & Order Operations

Why Inventory Numbers Disagree Across Sales, Warehouse and Finance

Why stock disagreement often comes from inconsistent definitions, event ownership and synchronisation.

How Discovery works

Every Discovery article follows the same path: what the problem looks like, who it affects, what usually triggers it, what it costs, why it happens and what to do about it.

We write about real problems that businesses can solve, backed by evidence, not about keywords or trend headlines.