Big Blue Ocean
From an accounting workaround to systems that run the business.
A small internal tool built to make accounting easier became the starting point for years of operational improvement.
Today, the systems connect work across accounting, sales, inventory, allocation, logistics, purchasing and customer service.
It started small.
The first problem wasn’t a software problem.
It was an accounting problem.
While working inside Big Blue Ocean’s accounting department, I was dealing directly with the same inefficiencies everyone else was dealing with: printed reports, manual tracking, handwritten changes and information scattered across systems.
Instead of starting with a plan to build a large platform, I built a small internal tool that made one recurring problem easier: tracking accounts receivable and overdue customers.
That solved the immediate problem — and revealed how many other parts of the business were dealing with the same underlying issue.
What wasn’t working
The business worked. The workflows made it harder.
Important information existed, but getting it to the right people — in a useful form and at the right time — required too much manual effort.
Paper everywhere
Reports, invoices and order paperwork were printed, marked up and physically passed between departments.
Disconnected information
Accounting, sales, inventory and logistics all needed the same information, but worked from different views and processes.
Manual cross-checking
Teams spent time comparing reports, checking customer status, locating inventory and confirming changes.
Limited visibility
Useful data existed inside legacy systems, but turning it into information people could act on was difficult.
How it evolved
Solve one problem. Learn what comes next.
Each new system came from understanding more of the business — not from trying to build everything at once.
Accounts receivable
The first application organized customer balances, invoices and payments, made aging information easier to understand and flagged customers who were overdue or on credit hold.
Revisions & approvals
Printed invoice markups became a structured digital workflow where changes, approvals and notes could be tracked instead of passed between desks.
Customer access & reporting
Customers gained secure access to invoices, while internal teams gained better ways to analyze products, customers, sales activity and inventory.
Automation & integrations
Legacy data began syncing automatically into the newer systems, keeping information current without relying on repeated manual exports or uploads.
Inventory & fulfillment
Order allocation, inventory selection, invoicing, checking and logistics moved from printed sheets into a connected digital workflow.
Purchasing & planning
Estimated inbound inventory and presale tools gave the purchasing and sales teams a better way to plan before product even arrived.
What it became
Not one application. A connected way of working.
What began as a small accounting utility grew into a collection of systems and workflows that support multiple parts of the business.
The system grew because the business revealed what it needed next.
One workflow, before & after
From paper trail to digital pipeline.
Printed sheets were physically marked, stamped, rewritten and passed from one department to the next.
Orders move through defined digital states with roles, visibility, notifications and an audit trail.
The result
Less work spent working around the work.
Paper-based order tracking was replaced by digital workflows.
Teams gained easier access to current information across departments.
Parts of order fulfillment that took hours of manual handling were reduced to minutes.
Defined workflow states and audit trails made it clear where work was and who owned it.
Purchasing and sales gained better tools for forecasting and working with incoming inventory.
The systems continue to evolve as the operation and its needs change.
Under the hood
The technology changed as the business did.
This work spans years, so the technology reflects different generations of the systems.
The stack was never the point. The goal was to use the right technology for the problem in front of us — and modernize when it made sense.
The bigger story
The first tool solved an accounting problem. The relationship solved much more.
That is still how we prefer to work.
Start by understanding the problem. Fix what matters. Learn more about the business. Then build the next thing only when there is a reason to.
Tell us what’s not working