ERP for one: why your system should shape itself to each user.

Every ERP gives you a dashboard. You log in, you see the same screen as everyone else, and you spend the first ten minutes of your day navigating to the three things you actually care about. Maybe you've bookmarked a couple reports. Maybe you've memorized the click path to your branch's inventory. Either way, you're working around the software instead of with it.

That's because traditional ERPs are built for the company. The admin configures it once, and every user gets the same experience — maybe with a few role-based restrictions on what they can see. The system has opinions about how your day should start, how your data should be organized, and what your workflow looks like. Your job is to learn those opinions.

We think that's backwards.

An ERP that shapes itself to the individual

In Horizen, every user builds their own views. Not "pick from three preset dashboards" — actual custom views, like spreadsheet tabs, with their own filters, columns, sort orders, and groupings. You build them yourself, in seconds, and they persist.

A branch manager's view of inventory looks different from a sales rep's. A CFO's view of AR aging looks different from the collections team's. The warehouse lead tracks lot expirations; the purchasing manager tracks vendor cost trends. Same data, different lenses — each built by the person who actually uses it.

When you find a view that works, you share it with your team. One click. Now your branch has a shared set of views that reflect how your branch actually operates — not how a software vendor in another state decided you should.

The best software doesn't teach you a new workflow. It makes your existing workflow faster.

You already know your operations

The ag retailers and distributors we work with aren't confused about how to run their businesses. They've been doing it for decades. They know which reports matter. They know which data points to track. They know which workflows their teams follow because they built those workflows themselves, on whiteboards and spreadsheets and sticky notes, over years of trial and error.

They don't need software that imposes a new process. They need software that accelerates the process they already have.

That's the design principle behind Horizen: you know your ops. We give you better tools. Custom views are the most visible expression of that principle, but it runs through everything — custom entities that let you track what no ERP anticipated, workflow automations you build in plain language, and AI agents that learn your business context, not just generic ag data.

Why this matters at scale

When you have 3 locations and 10 users, everyone can adapt to a rigid system. When you have 12 locations and 80 users across sales, operations, warehousing, finance, and management — rigidity breaks. People stop using the ERP for anything beyond the minimum required and go back to spreadsheets for the real work.

ERP for one means the system gets more useful as you add people, not less. Each new user shapes it to their role. Each shared view makes the team faster. The system compounds because it's built on individual productivity, not imposed uniformity.

Your branch in Iowa doesn't work like your branch in Nebraska. Your CFO doesn't work like your warehouse lead. Stop pretending they should. Give each of them an ERP that works how they work.