- Published
- Updated
- 8 min read

TL;DR: A beverage brand could not change its own website, its leads sat in separate tools, and training lived nowhere. Kief Studio built one custom ERP that runs the site, blog and events, captures leads, sends alerts, hosts training and reports on all of it. The lessons: put everything in one system, ship small updates often, and keep a person in charge of AI content.
Update, October 2026: we rewrote this case study to the current standard of our notes. The story and the work are the same. We removed outcome language we could not measure, such as "engagement metrics improved," and added the public rules that shaped the design.
This is a case study of a custom ERP we built for a beverage brand. The client asked us not to name them, so I will describe the work and the decisions rather than the company. I think the decisions are the useful part anyway, because most small and mid-sized brands run into the same walls.
A custom ERP, in our sense, is one system for the work that matters to a business, built around how that business already runs. For this client that meant the website, content, leads, notifications, training and reporting. Inventory and accounting stayed in the tools they already trusted.
What problems did the beverage brand have before the custom ERP?
Five, and they fed each other.
- The website was locked. Staff could not add a page, publish a post or list an event without asking an outside developer. Timely updates and campaigns waited in a queue.
- Systems did not talk. Several separate platforms each held part of the picture, so nobody had a full view of customers or campaigns.
- Marketing was manual. Email campaigns and blog updates were sent by hand and inconsistently, which meant extra steps for staff and gaps for customers.
- Training had no home. Onboarding material for staff and customers lived in scattered files.
- Leads fell through. Leads collected from forms and events did not flow into one database, so follow-up depended on memory.
None of these is unusual. What made them expensive was that each one made the others worse. A lead that came in from an event could not be sent the right blog post, because the blog and the lead list lived in different places.
Why did we choose a custom ERP instead of more tools?
Because the problem was the gaps between tools, and another tool would have added another gap. A custom ERP let us put the website, content, leads, alerts and training on one database, so an action in one place could trigger the right response in another.
It was not the right answer for everything. We left accounting and inventory where they were and connected what needed connecting. A good custom ERP does the jobs that are specific to how a business runs and borrows the rest. We cover the build versus buy question in more depth in bespoke versus off-the-shelf software, and our knowledge base explains ERP systems in plain terms.
I wrote separately about the coordination cost of one vendor versus four (opens in a new tab), and why the gaps between tools often cost more than the tools themselves.
What did the custom ERP include?
Eight parts, built and released in stages.
1. Website and content management inside the custom ERP
Staff can now update pages, publish blog posts and create events without a developer. That one change removed the queue that had been slowing every campaign. The structure was built to take new modules later as real use showed what was needed.
2. A fast, search-ready website
We rebuilt the public site to be responsive, quick to load and accessible. Google indexes the mobile version of a site: it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central (opens in a new tab)) We built and tested against the Web Content Accessibility Guidelines, which W3C describes as "a wide range of recommendations for making web content more accessible." (W3C, WCAG 2.2 (opens in a new tab))
Search settings live in the custom ERP too, so staff can edit page titles and descriptions themselves. The pages carry structured data, which Google says it uses "to understand the content of the page." (Google Search Central, structured data (opens in a new tab))
3. One lead funnel

Every lead, from any form or event, now lands in the custom ERP. From there the system can send the right content notification without asking the customer to sign up again for each list.
4. Automated alerts, within the rules
The custom ERP sends blog and event alerts to the people who asked for them. Automated marketing email has rules even between businesses. The FTC's CAN-SPAM guidance says "The law makes no exception for business-to-business email" and requires senders to "Tell recipients how to opt out of receiving future marketing email from you." (Federal Trade Commission (opens in a new tab)) Every alert carries a working opt-out, and the system honors it.
5. Content and sell sheets
An integrated blog supports education and search, and staff can write timely articles without outside help. Templated sell sheets let the sales team produce on-brand collateral quickly.
6. Custom AI writing tools, with a person in charge
We built AI writing tools tuned to the brand's voice for drafts across the website, blog and marketing. A person reviews and edits before anything is published. Google is clear that "Appropriate use of AI or automation is not against our guidelines," while pages made mainly to manipulate rankings are spam. (Google Search Central Blog (opens in a new tab)) The tools are updated on a regular bi-weekly cadence, each release shaped by how the team actually uses them. Our AI quality gates article explains the review idea.
7. Training inside the custom ERP
The custom ERP hosts training for employees and customers: onboarding, product guides and how-to material. Access is role-based, so staff, customers and partners each see their own path.
8. Reporting and support
Dashboards track leads, web traffic, campaign performance and content engagement in one place. We wrote training documents for the handover and keep regular check-ins, so the system changes as the business does.
What did the custom ERP change for the client?
I will stick to what we observed rather than percentages we did not measure.
- The team runs its own digital work. Pages, posts, events, campaigns and training are managed in-house, on their schedule.
- Leads have one home. Every lead lands in one place, with follow-up content sent automatically and an opt-out honored.
- Customers do less work. They no longer have to sign up separately for each kind of update.
- The brand sounds like itself at volume. AI drafts start on brand, and a person keeps the final say.
- The system keeps improving. Small, regular releases replaced the old pattern of a big rebuild every few years.
What lessons from this custom ERP apply to other brands?
Automate the customer's extra steps first
The most valuable automation removed steps from the customer, not just from staff. Fewer forms, fewer separate sign-ups, and content that arrives because they asked once.
Ship small and often
Treating the custom ERP as a living system, with small releases shaped by real use, kept it aligned with what people needed. A static system starts drifting from the business the day it launches.
One system beats many connections
Connecting website, marketing, leads, training and reporting in a single custom ERP made it faster to respond to a new campaign or a new product. Brian has a good story about a client who asked for a dashboard and actually wanted a decision (opens in a new tab); this project had the same shape.
If your business is weighing the same choice, our note on when a business outgrows its accounting software covers the earliest signs.
What would we tell a brand starting the same project?
Start with the one problem that slows everything else. Here it was the locked website, because every campaign, event and announcement waited behind it. Fixing that first bought goodwill and time for the harder parts.
Write down where every lead comes from before you build anything. Forms, trade events, distributor referrals, phone calls and social messages all count. A lead source nobody listed is a lead source that will keep living in someone's inbox.
Decide who owns the content after launch. Tools make publishing easy, but someone still has to choose topics, check facts and say no to a draft that does not sound like the brand. That ownership is the difference between a blog that stays current and one that stops in month three.
Finally, plan training as part of the build, not as an afterthought. Short guides written for the people who will use each screen are what turn a new system into a habit.
Frequently asked questions
What is a custom ERP?
One system for the work that matters to your business, built around how you already run. For this beverage brand it covered the website, content, leads, alerts, training and reporting.
Does a custom ERP have to replace accounting and inventory?
No. We left the client's accounting and inventory where they were and connected what needed connecting. A custom ERP should do the jobs specific to you and borrow the rest.
Can staff update the website without a developer?
Yes. That was the first goal. Staff publish pages, posts and events, and edit page titles and descriptions, from inside the custom ERP.
Are automated email alerts legal for B2B customers?
Yes, if they follow CAN-SPAM. The FTC says the law makes no exception for business-to-business email, so every alert needs a working opt-out that is honored.
How is AI-written content kept on brand?
The AI tools are tuned to the brand's voice and draft first. A person reviews and edits before anything is published, and the tools are updated on a bi-weekly cadence based on how the team uses them.
This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.
Where we fit
Kief Studio is in Shrewsbury, and a custom ERP is one of the systems we build: one system for inventory, orders, money and people, built around how your operation already runs. We map the work as it actually moves, build the system with roles and an audit trail, connect the tools you keep, and move your data over without losing history. Then we host and support it on dedicated infrastructure.
It is for operators whose day runs on spreadsheets and separate logins that never quite agree, and for businesses that packaged ERP software does not fit.
First conversation is free. No commitment.




