There is something about watching a business from close quarters that you don’t necessarily learn from books, presentations, or even years of professional experience.
You begin to notice the little things.
The conversations that happen repeatedly. The information someone is trying to find. The decisions that have to wait because one person is waiting for another. The time spent figuring out what happened, when everyone is already busy trying to figure out what needs to happen next.
Individually, these things might seem insignificant. Just another part of running a business.
But when you start noticing them everywhere, you begin to wonder: Why does running a business have to be so complicated?
I have found myself coming back to this question more often than I expected.
What fascinates me about businesses is that so many things have to work together to keep them moving. Sales, procurement, inventory, finance, people, suppliers, customers, compliance. Every function has its own responsibilities, priorities, and challenges. And yet, none of them really operate in isolation.
A sales decision affects inventory. An inventory decision affects purchasing. Purchasing affects cash flow. Cash flow affects what the business can do next.
Everything is connected.
At least, it should be.
But the way we work doesn’t always reflect that.
Information sits in different systems. Documents arrive through email. Orders come in through WhatsApp. Approvals happen over the calls. Someone maintains a spreadsheet because the system doesn’t quite give them what they need. Someone else keeps a separate record because they don’t have complete confidence in the first one.
And before long, people are spending a considerable part of their day connecting the dots themselves.
I find that particularly interesting.
We have spent years building software to help businesses manage different aspects of their operations. We have systems for accounting, inventory, procurement, sales, customer management, reporting, and almost everything in between.
Yet, the people working within these businesses still have to put in so much effort to bring everything together.
Why?
Is it because business is inherently complicated? Or have we, in trying to solve individual problems, sometimes made it harder to see the bigger picture?
I don’t think every problem can be solved by putting everything into one system. Businesses have different needs, existing investments, and ways of working. And technology, by itself, cannot fix a process that was never designed well in the first place.
But I do believe there is a fundamental difference between having systems that record what happens and having systems that help the business understand what is happening and what needs to happen next.
That difference matters.
Imagine a business owner trying to understand the company’s financial position.
The numbers might exist in the accounting system. Outstanding payments might be tracked somewhere else. Pending purchases might be known to the procurement team. Inventory commitments might sit with the warehouse team. And important context for a delayed payment or a pending order might exist only in someone’s email or WhatsApp conversation.
Every person may have a piece of answer.
But the business owner needs a complete picture to make a decision.
And getting that picture shouldn’t have to depend on how quickly someone can collect information from five different places.
This is where I think we need to start looking at business software differently.
Not simply as a collection of modules that perform individual tasks, but as something that understands how those tasks connect to one another.
Something where information doesn’t stop at the boundary of a department. Where a transaction doesn’t become an isolated entry. Where the context surrounding a business decision is not lost between a conversation, a document, and a system.
And increasingly, I think AI gives us an opportunity to rethink how this could work.
A business transaction rarely begins with someone opening an ERP and filling in a form.
It might begin with a customer sending an order over WhatsApp. A supplier emailing an invoice. A team member forwarding a document. Someone asking a question about a payment.
These are ordinary moments in a working day. But they contain information that the business needs to act on.
What if the information could move through the business without someone having to manually carry it from one place to another?
What if systems could understand the context, identify what needs to happen, help complete the work, and bring exceptions to the attention of the right person?
Not to remove people from the process, but to free them from the parts of the process that don’t need their constant intervention.
That is the possibility I find exciting.
Of course, building something like this is far more complicated than describing it. There are real-world processes, exceptions, integrations, dependencies, and countless details that have to work correctly. Every business has its own nuances. And there is a significant difference between demonstrating an intelligent workflow and building something businesses can depend on every day.
We are learning this firsthand at FlowOne.
Some days, building a product means thinking about the bigger picture. Other days, it means working through a small detail that might seem insignificant to someone outside the team but makes all the difference to the person using it.
Both matter.
Because the real measure of technology isn’t how impressive it looks in a presentation. It is whether it makes someone’s working day easier, helps them see something they couldn’t see before, or allows them to make a decision with greater confidence.
That is the standard I want us to keep coming back to.
I don’t expect businesses to become simple overnight. Nor do I think one platform can eliminate every challenge that comes with running a company.
But I do wonder how much unnecessary complexity we have come to accept as a normal part of doing business.
How much time do people spend finding information that already exists?
How many decisions wait because the right context isn’t available?
How much of a team’s energy goes into keeping systems aligned instead of moving the business forward?
And what could businesses achieve if more of that time and energy went into actually running and growing the business?
These are questions we are exploring as we build FlowOne. We certainly don’t have every answer yet, and I suspect the answers will continue to evolve as we work with more businesses and understand their realities better.
But the question that brought us here remains a simple one.
Why can’t businesses just work as one?
Perhaps the answer isn’t to make every part of a business identical, or to force everything into the same process.
Perhaps it is to make the connections between those parts work better.
So that information flows where it needs to. So that people have the context they need. So that systems do more than record work after it happens. And so that running a business becomes a little less about coordinating everything and a little more about moving forward.
That is what I hope we can contribute to with flowOne!
