Know tomorrow's production plan before the first shift starts.
Per machine and shift, from the orders that exist, changeovers counted.
The planner signsFor companies that run on orders, stock, machines and cash
We do the work. You take the decision.
Simon G. prepares your operating decisions every night, from the data you already have, and brings each one to the person who signs.
On your own serverNo internet neededYour data shared with no one
Extrusion line 2 runs out on 8 November at the current plan. Lead time 12 days.
Why now: three orders for the same film confirmed this week; the supplier's last two deliveries were four days late.
Fictional plant. An example of a prepared proposal, not a promise.
Does this sound like your week?
The people are composites. The mornings are not.
None of these is a people problem. They are what happens when decisions are prepared by hand, in the gaps between other work.
So what does that cost you?
Nobody books these hours to a cost centre, so nobody sees them. Set the figures to your company. Nothing you type leaves this page.
Orders of magnitude, not promises. In a pilot the first thing we do is measure yours, with a baseline fixed before anything changes.
What would Tuesday look like instead?
Mara runs purchasing, Tomas the plan, Ilse the money, at a plant that could be yours.
Three windows open. Builds the order list by hand. Misses the supplier who was late twice this month.
Reworks the week because printing has no rolls for order 4458. Nobody told him extrusion was behind.
Asks for the cash position. Gets it Thursday. Decides Friday. The overdraft was needed on Tuesday.
One list, prepared at 05:00: twelve orders with stock, need, lead time and the supplier's record. Nine are inside her limit. Three need her signature. She enters all twelve in the ERP. Done by 08:40.
Reads the plan per machine and shift, built from the orders that exist. The missing rolls were flagged yesterday. The order went out.
Sees thirteen weeks of cash with the two largest customers' real payment behaviour. The decision on terms for customer A is prepared. She signs it.
What changed between the two columns?
Your systems record. Your spreadsheets reconcile. Your managers decide, in the time left over. That last step is where the money leaks, and it is the only step nobody has automated.
The systems do not change. The spreadsheets go. The decision arrives prepared, and the person who signs it is still the person who signs it.
How it gets there
No implementation project. No budget line for one. You say what you want decided better; we read your data and set it up.
Which decisions hurt or come too late: orders, production, credit, cash, the plan. One conversation, with the person who owns them.
We take what your systems already record, ourselves, with your IT beside us for a few hours: the first export, then the same export scheduled to run each night. Your products, your limits, your people.
Every night Simon G. prepares them with their evidence. Inside a signed limit they need no signature. Outside it, the person you named approves or rejects, with a reason. Simon G. changes nothing in your systems: your people enter the decisions in the ERP, as they do today.
What lands on your desk
Each one with the person who signs it. Your field decides which come first.
Per machine and shift, from the orders that exist, changeovers counted.
The planner signsNeeds by week against stock and open orders, with the supplier to call today.
Purchasing signsProposals per supplier every night, forecast error shown honestly.
Head of supply chain signsA limit from each customer's own payment record, and this week's action.
The credit controller signsReceivables by the date each customer really pays. Three scenarios.
The finance director signsOne management result that ties to the books, variance explained.
The board readsThe question you are about to ask
Five questions a managing director asks before the second meeting.
Four days to a written verdict on your data. Three weeks to the findings and one decision prepared on a real case of yours. Eight to twelve weeks for a pilot with your people signing real decisions. Installation takes minutes.
No. Simon reads exports from the systems you have, spreadsheets included. It never writes back to your ERP and never asks for passwords.
A fixed-fee diagnostic, credited to the pilot. A monthly pilot you can cancel. A yearly licence per kind of decision, given in the first conversation. No implementation budget, because there is no implementation project.
No. A few hours of your IT's time on one day, to run the first export with us and schedule it for each night. Then a named owner who signs, and thirty minutes a week with us during the pilot.
Nobody learns a system. They arrive to a list of prepared decisions, a reason beside each, and an Approve button. A rejection is written down with its reason. If the reason is a rule or a limit, a person changes it, and the next proposal follows.
And then?
Before a decision is applied, we write down the figure it should change and its value today. Afterwards we measure the same figure the same way. A result without a baseline proves nothing.
Weekly error 14%. The gap in week 38 is a missing export, drawn as a gap, never as zero. Fictional data.
Don't take our word for it
A founder goes through one decision of yours, on your questions, and you get a written answer on whether it fits.
Talk about one decisionThe rules behind every decision Simon G. prepares, written down so your auditor and your IT can hold us to them. The full method comes in the first conversation.
The seven principlesStock, working capital, credit, decision charter. On your own file, never uploaded.
Open the free toolsWhat we think, in writing
By Dan Olea, founder: a former CFO and auditor who ran the ERP implementation he now reads exports from.
It is not paranoia. It is risk management. Decisions prepared every morning, in your own house.
Read DecisionsWhat a decision should leave behind, whoever proposed it: a name, a limit and a record.
Read on groma.ro AccountabilityThe rules keep moving their dates. The decisions you take every day do not.
Read on groma.roStart with one decision
Thirty minutes with a founder. We go through how Simon G. would prepare it and say in writing whether it fits.
We do the work. You take the decision.
Or write: office@gromasystems.com
Groma S.R.L. · Timișoara, Romania · English, Romanian, French, German.
Questions we are asked first
Nowhere. Simon G. installs on your own server, needs no internet connection to run, and shares your data with no one: not with other companies, not with us, not with a cloud model or a chatbot.
The spreadsheets, not the ERP. It reads what the ERP records and prepares the decisions the spreadsheets were trying to prepare, with evidence and a record. It never writes back. If you plan production in Excel today, read about an Excel alternative for production planning.
The engine is deterministic: the same inputs give the same proposal, and every step can be traced. An assistant on your own server may explain a proposal in plain words; it does not decide, and no company data goes to a cloud model.
Nothing. You tell us what you want decided better. We take the exports from your systems ourselves, with your IT beside us for a few hours, and set Simon G. up for your activity.
A fixed-fee diagnostic credited to the pilot, a monthly cancellable pilot, then a yearly licence per kind of decision and company size, given in the first conversation. How the pilot works.
Yes: four free browser tools on groma.ro that never upload your file.