You have already chosen your ERP. Pyramid Hybrid Cloud sits on your own server, is set up around how you work and has probably been doing the job for years. What you never chose is for a large part of the day to go on retyping emails, looking up stock and entering orders line by line.
That is where we come in. A digital coworker works in Pyramid just like a colleague: it reads what comes in, looks up what it needs, registers and follows up. You do not change systems, you move nothing to the cloud and nobody has to learn a new interface. Pyramid looks the same as yesterday. It just does a lot more.
What a digital coworker does in Pyramid
Most Pyramid users will recognise the flows below. They are not difficult, there are just a lot of them, and they always arrive when someone has something else to do.
| Task | Today | With a digital coworker |
|---|---|---|
| Sales orders by email or PDF | Someone retypes the order into Pyramid | The order is read, checked against item and price, and registered |
| Stock and delivery questions | Someone searches Pyramid and replies | An immediate answer, with current stock from Pyramid |
| Purchasing | The need is noticed when it is already urgent | The basis is prepared and the order placed according to your rules |
| Inbound deliveries | Registered afterwards, when someone has time | Registered and matched against the order |
| Invoice data | Stalls on a detail someone has to sort out | Prepared so invoicing goes through |
Anything that does not add up, such as an unknown item number, a price that differs from the agreement or a customer over their credit limit, goes to a human. The coworker does not guess.
Smarter, not bigger
Making Pyramid smarter is not about adding more modules. It is about putting what is already in the system to use without someone having to sit and type.
Orders are registered continuously. Instead of waiting for a quiet moment, the order lands in Pyramid when it lands in the inbox. The order confirmation goes out the same day.
Stock is right when someone asks. When inbound deliveries are registered immediately, the stock figures stop lying and sales stops calling the warehouse to double-check.
You set the limits. You decide which orders may be registered automatically, which purchases need approval and what must always be reviewed by a human. The coworker first runs with you as the reviewer, and you let it run fully once you are comfortable.
Everything is traceable. Every action is logged: what the coworker tried to do, which data it used and what Pyramid replied.
Pyramid Hybrid Cloud, not Business Studio
Vitec Pyramid currently has two product lines that are easy to mix up. Business Studio is their cloud-based SaaS system. Pyramid Hybrid Cloud, despite the name, is the solution installed locally on the company’s own hardware, with web access as a complement.
This article and our API concern Pyramid Hybrid Cloud. That is also where the need is greatest: most AI tools on the market assume a cloud API, and a system behind your own firewall is left out.
Under the hood: our own REST API for Pyramid
For those who want to understand how it works technically.
Pyramid Hybrid Cloud does not come with the kind of API an AI coworker needs. So we built our own REST API for Pyramid. That API is how the coworker reads and writes, and it supports Pyramid versions 4.16, 4.17 and 4.18.
Reads and writes. The API retrieves items, prices, customers and stock, but it also creates and updates sales orders, purchase orders and deliveries. Writing is where the time is saved.
Against your own installation. Pyramid stays where it is. No data is migrated and no parallel register is built on the side.
Limited permissions. The coworker gets the rights it needs for the flows you have agreed on, no more. Credentials are stored encrypted and separately per customer.
Every call is a job. Everything the coworker does in Pyramid goes through our job queue. Jobs run in order, are logged in full and can be searched afterwards. If something goes wrong you see exactly which call was made and what Pyramid replied, so the error can be fixed rather than guessed at.
Generic building blocks, your rules. The API contains no customer-specific exceptions. Your business rules, such as which customers get automatic order registration or which suppliers apply to which items, live in the coworker’s instructions. A changed rule is therefore a changed instruction, not a new development project.
If you are on a version older than 4.16, we will go through what applies in your case.
Getting started
Start with one flow, not the whole business. For most Pyramid users that is order intake or purchasing.
- We walk through the flow. You describe how it is handled manually today and where it tends to go wrong.
- You grant access to Pyramid. A one-time setup against your installation.
- We configure the coworker to your rules and test it on real cases from your everyday work.
- You review before it goes live, and let the coworker run fully once you are comfortable.
More on how a digital coworker works is on the platform page, and the Pyramid connection is described under integrations. How WCT Verktyg in Karlstad has Stina handle order intake in Pyramid Hybrid Cloud is in the WCT customer story, with more examples under customer stories.
Running Pyramid Hybrid Cloud? Tell us which flow takes the most time at your company today, and we will show you what it would look like with a digital coworker against your own installation. Book a call.