Free Consult
Abstract blue background
Rated 4.7 out of 5 on G2SAP Partner

Case Study | Forge AI for SAP Business One

From One AI Pilot to Four Teams

How Harney & Sons Fine Teas scaled Forge AI on SAP Business One without rebuilding the foundation.

Book a demo

Harney & Sons Fine Teas logo

At a Glance

One Pilot, Four Teams, One Source of Truth

Harney & Sons Fine Teas, a family-owned tea blender in Millerton, New York, runs SAP Business One with Third Wave. In March 2026 the team went live on Forge AI, the AI agent for SAP Business One from Third Wave and Structify.

15
People on Forge AI
4
Teams on One Foundation
20+
Paper Forms Replaced
100,000+
SAP Business One Records Matched

The Challenge

A Production Floor Running on Paper

Sachets, filling, blending, and bagging each ran on paper forms. Staff retyped every form into spreadsheets by hand, so a transposed batch number or a wrong quantity landed inside inventory and product cost. Harney wanted clearer data and faster decisions, with no new risk to the systems already running the business.

You should not have to trade control for speed to put AI to work.

The Approach

The Four Breaking Points Harney Cleared

Most AI pilots stall after the first win. The next team needs clean shared data, written rules, and access controls the pilot never had to solve. Harney fixed each one on SAP Business One before adding the next workflow.

  1. Production data nobody trusts

    20+ paper forms across sachets, filling, blending, and bagging were retyped by hand into spreadsheets. Structured digital forms in Forge AI now validate every entry at the point of work, and a product information layer keeps item names, pack sizes, and specifications consistent. Clean records at the source, and one product record for every team.

  2. Answers locked in separate systems

    A question spanning production and sales meant pulling exports and matching rows by hand, often for hours. Forge built a semantic layer, a shared map of what the data means, linking floor forms, purchase orders, and SAP Business One item codes across 100,000+ records. Leaders see production, procurement, and sales from one current picture.

  3. Automation outrunning the controls

    As automation scaled, approvals, access, and business rules drifted out of step with the workflows they governed. Harney set read-only SAP Business One access by default, narrow permissions for every automation, and approval before any automation connects or acts. Nothing posts to SAP Business One until a person approves.

  4. Rules stored in people’s heads

    The supervisor who knows which customer rounds up. The planner who knows which supplier ships short. Each rule is now written once, in one place Forge follows every time, with working know-how captured straight from Slack. Every shift follows the same logic from day one.

The Result

Four Teams on One Foundation

Each new team started from the same trusted data and controls. Harney finished the first phase with a clear, priced plan for the next two automations, product data and order processing.

Production

Structured capture at the point of work.

Procurement

Purchase orders turned into sales orders, with approval before posting.

Product

Product information management on one consistent record.

Commercial

Shared data across sales, production, and procurement.

Your Next Step

A Five-Point Scaling Check for Your SAP Business One Team

Score yourself honestly. If two or more are missing, fix the foundation before you buy the next automation.

  1. Validated capture at the point of work

    No retyping between the floor and the system.

  2. One consistent product record

    The same item data on the floor, at the order desk, and in SAP Business One.

  3. A semantic layer across your sources

    Records matched at scale, so one question gets one answer.

  4. Read-only access and approval before any write

    Scoped permissions for every automation.

  5. Business rules written once

    Kept with each workflow, not in someone’s head.

Get in Touch