About
About InPlace
The name says two things. Everything in place: every document, order, invoice and payment has a defined and known place. And in place in the control sense: a mechanism that actually exists and holds.
What the system does
InPlace is a procurement-to-payment system, written in Hebrew and read right to left, with this English edition beside it. It connects the chain from the supplier to the bank transfer into one source of truth, and surfaces what needs action without becoming another crowded screen.
The principles it was built on
- A decision screen, not a display screen: every addition is judged by whether it shortens the path from arrival to decision
- Truth over convenience: no invented figure, and no zero pretending to be data. A measure with no data shows a dash, not a zero
- One semantic language: colour marks meaning and never decoration, and meaning never rests on hue alone
- Earned familiarity: standard components and the same visual vocabulary on every screen
- Hebrew and mobile are first-class citizens, not an adaptation made at the end
The three roles
Owner, procurement and accountant. All three work on the same chain, and none of them sees or does what belongs to another. The accountant is the only one who executes transfers, and payment always passes through an approved request carrying a reason and a record.
What the system refuses to be
- Not another metrics screen with no decision on it
- Not an expense product that defines value through spending alone
- Not a heavy general ERP
- Not a loud, colourful or “magical” SaaS brand
These refusals are not modesty. They are what allows the system to do one thing well instead of four things approximately.
Character
Clear, dependable, calm. An interface that handles other people’s money and is therefore never loud, never tries to surprise, and never asks for attention on its own account. The tool disappears into the task.
In practice that means the system carries no animation that does not signal state, no tiny low-contrast text and no critical action hidden behind a hover.
Who stands behind the system
InPlace is a product of In Place, a business registered in Israel. The details here are the same details that appear in the site’s structured data, so that anyone checking who is asking for access to their financial information gets one answer in both places.
InPlace was built by two people, not by a product department. Nir Barmuha brought the problem, and Moshe Sananes built the system that solves it.
Founder
Nir
Barmuha
More than twenty years of experience in business and operations, in Israel and abroad. He runs businesses today, among them a chain in food, and knows at first hand the daily work with suppliers, orders, stock, staff, payments and invoices.
The idea of founding InPlace came out of that experience. Not out of theoretical market research, but out of a real need that came off the ground: to put order into processes that in many businesses still run on WhatsApp, on spreadsheet files, on telephone calls and on manual checks.
The professional content on this site is written from that same point of view: out of practical experience, out of familiarity with the daily difficulties, and out of an understanding of how businesses actually run.
Founder
Moshe
Sananes
Three years building systems that join data, automation and business processes, in which accuracy and control are part of the operation itself. That experience led to the principle InPlace is built on: not to find out from a report, after the payment has gone out, that something was wrong, but to identify the exception and stop it before the money leaves.
| Detail | Value |
|---|---|
| Registered name | In Place |
| Registration number | 036689081 |
| Address | HaRotem 14, Kfar Adumim, Israel |
| Telephone | +972-54-254-7074 |
| Second telephone | +972-52-416-7881 |
Accessibility
The target is WCAG 2.1 level AA: text contrast of at least 4.5 to 1, full keyboard navigation, screen-reader labels and respect for a system preference to reduce motion. The audience includes non-technical users, so every error is written in plain language rather than as a raw database message.
Meaning never rests on colour alone. Every status also carries text or a mark, because a reader who does not distinguish a hue still needs to know what requires attention.
Start with one supplier, and watch the chain work on your own business.
Open a free accountNo credit card. Start with one supplier.