Articles, case studies and news

Business Technology Insights, News and Perspectives.

What we have learned building and running connected business systems for operationally complex companies: written for the people who have to live with the decisions.

All articles, page 8.

529 posts
Three navy component tiles on the left each send a line into one green circle on the right, the finished item they assemble into.
Articles

Zoho Inventory Explained for a Light Manufacturer: Composite Items, Assemblies and the Handoff to Zoho Books.

Zoho Inventory was built for companies that buy and sell finished goods. A light manufacturer makes them, and the difference shows up in exactly four places. Here is how each works, what it does well, and where a manufacturer reaches the edge.

A stack of five navy bars sits on a plain ground; the bottom bar is green and the four above it are plain.
Articles

Process Documentation Software: When the Tool Is Not the Missing Piece.

Every quarter someone proposes buying a tool to fix the documentation problem, and every quarter the documentation stays unwritten. The tool was never the missing piece. Three other things are, and none of them is for sale.

A green line runs through four navy diamonds in a row; the third diamond is drawn with a heavier navy border and stands slightly apart.
Articles

Workflow Documentation: Write Down the Exceptions, Not the Happy Path.

Most workflow documentation describes the day nothing went wrong. That day does not need documenting; the people who do the work already know it. What they know and never write down is what happens on every other day, and that is the part an automation has to read.

A navy padlock sits on a green path just before the path splits into two branches; the lock is closed and both branches are plain.
Articles

ERP Implementation Failure in the Mid-Market: The Three Decisions Made Before the Kickoff.

The post-mortems all say the same things: scope crept, the data was bad, the users resisted. Those are symptoms. The failure was decided months earlier, in three decisions that were never made, and each of them belongs to the buyer, not the vendor.

A stack of five navy bars sits on a plain ground; the second bar from the bottom is green and noticeably longer than the rest.
Articles

ERP Total Cost of Ownership: The Five-Year View a Vendor Quote Never Shows.

The number on the ERP quote is the smallest number in the decision. The five-year cost is made of lines the vendor does not sell, and the largest of them is one most buyers never write down until year three.

A green path passes through four navy gates in a row; the first gate stands open and the three behind it are shut.
Articles

Business Process Mapping Before You Buy Anything: The Map That Decides the Software.

Most software is bought to fix a process nobody has drawn. The map is not documentation for its own sake. It is the artefact that decides what to buy, what to build and what to leave alone, and it takes days, not months.

Three navy columns of unequal height under one green line; the two taller columns are joined at the top by a short green bridge.
Articles

ERP vs CRM: What Each System Is Actually the Record For, and Where the Two Meet.

The question is usually asked as if it were a choice. It is not. A company past a certain size has both whether or not it has bought either, and the useful question is which facts belong to which, and where the seam between them runs.

Four navy tiles in a row joined by grey connectors; the third connector is broken in the middle with a small red marker at the gap.
Articles

Bidirectional Sync Is a Design Failure Most of the Time.

When a company asks for two systems to sync both ways, it is almost always asking for something else: permission not to decide which system owns the record. The sync will run. What it will do to the data is the subject of this post.

Three navy record tiles on the left each send a line into one green circle on the right, one customer assembled from three copies.
Articles

Customer Master Data Management: Deciding Which System Owns the Customer Before Anything Syncs.

Every AI project in a mid-market company eventually asks a simple question, who is this customer, and gets three answers. The fix is not a data cleanup. It is a decision about ownership that most companies have never made.

Four navy tiles in a row joined by grey connectors; the second connector is broken in the middle with a small red marker at the gap.
Articles

An Application Integration Strategy for a Mid-Market Operator: Three Decisions Before Any Connector.

Most companies do not have an integration strategy. They have a list of connectors, each bought to stop one specific pain, and a growing sense that the list is the problem. The strategy is three decisions, and none of them is a product.

A horizontal navy timeline bar with a green bracket over its first two thirds; the final third of the bar is left plain.
Articles

Where Zoho Books Actually Stops: Multi-Entity Consolidation and Revenue Recognition.

Zoho Books is a better ledger than most mid-market operators give it credit for, and it has a hard edge. Knowing exactly where that edge is, and what sits on the other side of it, is the whole eighteen-month ERP question in one decision.

A navy padlock sits on a green path just before the path splits into two branches; the lock is closed and the branches are plain.
Articles

What Fractional CTO Rates Mean, and What the Fee Actually Buys.

The fee for a fractional CTO is easy to quote and hard to compare, because the thing being priced is not hours. It is accountability for outcomes across systems nobody else in the building is accountable for. Here is how to read the number.

Where we're not the right answer

We'll tell you if we're a fit. If we're not, we'll tell you that too.

  • Your current stack works and nobody wants to change it
  • You want licences resold at a discount and nothing else
  • Your internal team owns the operating model and is not handing it over
  • You want hours of configuration work and nothing run for you: that is on our services pages, and it is not a managed solution
How we start

Most of our best clients come to us with a feeling, not a plan.

"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.