Every price change keeps the rule behind it.
A supplier sends a new price list. Nieme prepares the updates it implies (the catalog, the margin check, the note to sales) and waits for the person who owns the decision.
What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.
Nieme records the change and ties it to the pricing process.
A document changed in a connected folder.
A message was observed in a selected channel.
A new price list lands in the shared folder
Nieme records the change and ties it to the pricing process.
Observed event
- Source
- Google Drive
- What happened
- A new price list lands in the shared folder
- When Nieme saw it
- 12 min ago
Nieme recorded that this event happened. Observation alone authorizes nothing.
Why it matters
Nieme's reason
the source is selected for this Project
Status
Raised as a Signal. Nieme proposes the work; a person decides.
This title is independent of the Objective.
Produces each declared file as a governed Artifact of this one Operation, reviewed together.
Project: Catalog and pricing
From Signal · a document changed in the suppliers folder
Selected Operation Sources (3) — explicitly chosen
Catalog and pricing · operation.on
- XLSXcatalog-october.xlsx118 KBproduced
- XLSXmargin-check.xlsx33 KBproduced
- DOCXnote-to-sales.docx15 KBproduced
Where the work breaks now
Without a record
- Spreadsheets are the process.Updates move by copy and paste between files, and the version that wins is whoever saved last.
- The same question every month.Each cycle works out again what was decided the last time.
- Errors surface downstream.A wrong price is found by a customer, not by a review.
With Nieme
- Observed where it happened.The change in the shared folder is recorded and tied to the process it affects.
- The rule is part of the work.The updates are produced together from the admitted sources, with the policy that applies stated before anything runs.
- Approved before it leaves.A person accepts before anything reaches the store or the sales team, and next month starts from that decision.
From a supplier's new price list to an approved catalog update
-
01 · Observed
A new price list lands in the shared folder
Nieme records the change and ties it to the pricing process.
Google DriveOneDrive -
02 · Governed
The pricing rule is part of the work
Objective, sources and the margin policy that applies are declared before anything runs.
policy.onoperation.on -
03 · Executed
The updates are produced together
An updated catalog sheet, a margin check against the policy and a note to the sales team.
XLSXDOCX -
04 · Reviewed
The owner approves
Nothing reaches the store or the sales team before a person accepts it.
Review -
05 · Carried forward
Next month starts from this one
The accepted rule and its exceptions are there the next time a price list arrives.
decision.on
The work outlives the session that did it.
Every step above writes to one record. Swap the model, the agent or the person who executes, and the objective, the sources, the authority and the decision stay attached to the work.
- objective
- Apply the October supplier price list
- context
- Supplier price list (October) · current catalog · margin policy
- authority
- Approved by the operations owner
- executor
- The model chosen for spreadsheet work
- evidence
- Updated catalog, margin check and the note to sales
- decision
- Accepted with one exception, recorded
The fields Nieme stores for every Operation.
Change prices.
Keep margins.
We start with one supplier and your margin policy. Nothing reaches the store before the owner approves it.
Rather talk to a person? Email the founder.