What Aromazen Taught Us About Cross-Department Automation

Where Aromazen Started

Like many growing product businesses, Aromazen’s operations had grown faster than its systems. Production tracked batches on paper logs. Inventory lived in a spreadsheet that only one person fully understood. Sales orders came through a mix of an online store and direct WhatsApp orders from retail partners. Each department functioned well on its own - the problem appeared in the gaps between them: stock that looked available online but was not, production runs that did not align with actual demand, and a founder who had to check three different places to answer a simple question such as, “How much lavender oil do we have left?”

The Real Problem Wasn’t a Missing Feature

Our first instinct was to look for the missing feature - a tool Aromazen did not yet have. Instead, we found that the individual tools were adequate; the real problem was that they did not communicate with one another. Production did not know what sales had promised, and sales did not know what production could deliver on time. This is a common pattern: businesses often do not need a better tool within one department; they need their departments to stop operating as separate islands.

What We Connected First, and Why

Rather than trying to unify everything at once, we began with the connection causing the most daily friction: production output and inventory counts. Every completed batch would automatically update stock levels instead of relying on a manual spreadsheet update at the end of the day, often one or two days late. This connection was chosen deliberately - it had high operational impact because stock accuracy affected nearly every other decision, yet it was relatively focused because it involved two systems rather than five. Sales and reporting connections followed once this foundation was stable.

The Result: What Changed Day to Day

The most noticeable change was not a dramatic company-wide transformation - it was smaller and more practical. The founder no longer needed to verify stock personally before confirming large retail orders. Production gained earlier visibility into upcoming demand instead of learning about a large order after it had already been promised. Discrepancies between “what we think we have” and “what we actually have” became something the system flagged automatically, rather than an issue discovered during a stressful stocktake.

What We’d Do Differently With Hindsight

A few things we would approach differently on future projects:

• We would involve the production team earlier in defining what counts as a completed batch - this definition changed twice in the first month and slowed the rollout.
• We would set clearer expectations for the adjustment period - the first two weeks felt slower for the team, and we could have prepared them for that transition.
• We would separate must-have connections from nice-to-have requests more strictly at the start - several early requests mattered much less once the core system was running.

The Bigger Lesson for Any Growing Business

Aromazen’s situation was not unusual - it is what happens to many businesses somewhere between “small enough that everyone knows what is happening” and “large enough that a dependable system is essential.” The lesson extends beyond this project: do not look only for a missing tool. Identify where information stops flowing between the tools you already have, and start there.