Jeen Technologies: How Much Of The 2026 Order Base Is Actually Firm, And How Much Still Rests On Statements Of Work
The main article showed that the gap between orders and revenue is the core issue. This follow-up shows that out of management's NIS 61 million revenue target for 2026, only a limited layer rests on work orders already received, while most of the base still depends on Statements of Work and on revenue that is not yet signed.
What This Follow-up Is Isolating
The main article already made the core point: the headline around orders is not enough on its own, because the real test is conversion into revenue. This follow-up isolates the next layer down: how much of the revenue base Jeen is using for 2026 has already moved into a firmer stage, and how much still sits in a softer layer of Statements of Work, future customer usage decisions, and management assumptions.
The bottom line is fairly sharp. Near the report date, the company shows NIS 64.7 million of expected revenue and SOW-based orders. But only NIS 37.2 million of that amount is even allocated to 2026 in the table attached to the annual report. Out of those NIS 37.2 million, only NIS 10.8 million sits on work orders already received, while NIS 26.4 million, about 71% of the disclosed 2026 base, still sits on Statements of Work that have not yet turned into work orders.
The gap becomes sharper once management guidance is added. The board report sets a 2026 revenue target of NIS 61 million, but explicitly says that the number relies not only on work orders already received and signed Statements of Work, but also on additional expected revenue for which neither a work order nor a Statement of Work has yet been signed. So the debate here is not whether demand exists. Demand exists. The debate is what quality of demand has already taken enough contractual shape to serve as a reliable 2026 revenue base.
What Has Moved Into A Firmer Layer, And What Still Rests On SOW
The report describes the engagement model directly. In a large share of projects, the customer signs a Statement of Work, or SOW, that defines the work the customer expects to receive and the payment scope, and only later sends work orders at its own discretion. That is the critical point, because once that structure is understood, the NIS 64.7 million figure stops looking like one hard revenue base and starts looking like a mix of layers with very different quality.
The company hints at that itself. In the backlog section it stresses that these figures are not order backlog as defined in the regulations. More than that, it writes that the figure reflects both non-binding work orders and signed Statements of Work for which no work orders have yet been received, and that in ongoing engagements it is calculated based on about 12 months of activity at the customary volume of that customer relationship. In other words, even before asking whether NIS 64.7 million will convert into revenue, the right first step is to separate what has already moved into a work order from what still rests on assumed future usage.
| Recognition period in 2026 | Work orders received | Statements of Work without work orders | Total |
|---|---|---|---|
| Q1 | NIS 1.727 million | NIS 0.088 million | NIS 1.814 million |
| Q2 | NIS 4.553 million | NIS 5.330 million | NIS 9.883 million |
| Q3 | NIS 2.448 million | NIS 8.044 million | NIS 10.492 million |
| Q4 | NIS 2.040 million | NIS 12.951 million | NIS 14.991 million |
| Total 2026 | NIS 10.768 million | NIS 26.413 million | NIS 37.180 million |
That is the center of the picture. The only layer that has already moved beyond the framework stage into a more advanced work-order stage is NIS 10.8 million. Even that still sits inside disclosure the company does not present as binding backlog under the regulations, but it is at least one step closer to revenue than pure SOW. By contrast, most of the disclosed 2026 base still rests on Statements of Work that have not yet become work orders.
That does not mean the numbers are invented. It means revenue quality is different. A work order already received is a layer closer to revenue, even if it is not perfectly hard. A Statement of Work still waiting for a work order is a layer that depends on customer discretion, timing, and actual consumption.
2026 Guidance Also Rests On Revenue That Is Not Yet Signed
This is where the gap between the headline and the economic base becomes real. The board report presents a 2026 revenue forecast of NIS 61 million. But the same paragraph explains that the forecast relies on three sources: work orders already received, Statements of Work that have been signed but do not yet have work orders, and additional expected revenue for which neither a Statement of Work nor a work order has yet been signed.
In plain arithmetic, the March 2026 table allocates NIS 37.2 million of expected revenue into 2026. That is not an outside estimate. It is simply the sum of the four quarters in the company's own table. Against a NIS 61 million forecast, that leaves a gap of NIS 23.8 million. The gap is not a math error. It is exactly the layer management is pointing to when it refers to additional expected revenue that is still unsigned.
That changes the right way to read 2026. This is not a year with an almost locked revenue base. It is a conversion year. To reach NIS 61 million, the company does not just need to execute what it already has in hand as work orders. It also has to convert a large share of the SOW layer into actual work orders, and then add another layer of revenue that is not signed at all today.
ARR adds another useful angle. In December 2025, annual recurring revenue, ARR, stood at only NIS 3.683 million. The company itself stresses that ARR is not a direct revenue forecast and even argues that the order base is the more relevant growth measure. But that is exactly why ARR still matters here. It shows how small the recurring layer already sitting in the system still is relative to the NIS 61 million headline. Put simply, most of 2026 is supposed to come from conversion and expansion, not from a recurring floor that already looks stable.
The Two Immediate Reports Show Exactly How That Quality Is Built
The two immediate reports around the annual filing do not contradict this reading. They illustrate it.
| Event | Headline number | What is concrete now | What is still conditional |
|---|---|---|---|
| March 16, 2026, strategic customer through Jeen Defense | Immediate work order of about NIS 4.3 million | License and services for immediate execution | Additional optional work items that may reach up to NIS 45 million including VAT, over 24 months and at the customer's discretion |
| March 25, 2026, Israeli healthcare body | Agreement of up to about NIS 9.1 million over 3 years if the customer consumes all services | First work order of about NIS 2.3 million | The total agreement size, including the annual framework amounts of NIS 2.5 million, NIS 3.1 million, and NIS 3.5 million, still depends on actual service consumption over the term |
The March 16 report is especially sharp because it separates the immediate layer from the optional layer in the same disclosure. There is NIS 4.3 million for immediate execution, but there are also optional work components that may reach up to another NIS 45 million over 24 months, at the customer's discretion and according to its needs. It is almost a textbook example of the difference between a headline number and a hard revenue base.
The March 25 report works in the same way, only in a more civilian wrapper. There is a three-year agreement with a total size of NIS 9.1 million if the customer consumes all services, but at signing the first work order is only NIS 2.3 million. Even within that first order, the company says that about NIS 1.4 million of services had already been performed in recent months as part of the marketing effort, and therefore will not require additional inputs. Here too, the full headline and the immediate base are not the same thing.
The investor presentation adds one more useful cue. It shows the jump to NIS 64.7 million in March 2026 and attributes the increase from December 2025 mainly to the start of Jeen Defense activity. In other words, even in investor-facing framing, the company itself is signaling that the acceleration relied on opening a new defense-oriented channel, not on a wide layer of already-hard work orders sitting in the bag.
What This Means In Practice For Revenue Quality
Once the layers are lined up, the picture becomes much clearer than the headline. There is one layer of work orders already received, NIS 10.8 million. Above that there is a larger NIS 26.4 million layer tied to Statements of Work for 2026 that have not yet turned into work orders. Above that there is another NIS 27.5 million that is allocated to 2027 and beyond. And above all of that sits a NIS 61 million management forecast for 2026 that also requires additional revenue that is still unsigned.
So the 2026 revenue base is better read as four floors:
Floor one: a more advanced layer of work orders already received, though even that is not presented as binding backlog under the regulations.
Floor two: a broader SOW layer, where the framework exists but the customer has not yet issued the actual work order.
Floor three: a meaningful volume that already sits outside 2026 and is allocated to 2027 and beyond.
Floor four: a material part of 2026 guidance that still rests on expected revenue that is not signed at all.
That is why the real debate around Jeen is not truly about the size of the order figure. It is about the quality of conversion. The company may well close that gap, especially if it keeps expanding with existing customers and if Jeen Defense succeeds in turning frameworks into work orders. But as of the report date, a large part of that path is still not hard enough to be called a locked revenue base.
Bottom Line
Jeen's 2026 order numbers are not misleading, but they require a much more aggressive decomposition than the headline gets. As of March 2026, only NIS 10.8 million of the quantified 2026 layer had already received work orders. Another NIS 26.4 million still rests on Statements of Work without work orders, and the NIS 61 million revenue target requires another NIS 23.8 million of revenue that is not yet signed.
In other words, Jeen enters 2026 with strong demand, but not with a revenue base that is as firm as the headline may suggest. This will be a year in which the proof does not come from another backlog chart. It comes from the pace at which frameworks turn into work orders, and from the company's ability to show that the language of SOW is becoming the language of recognized revenue.
Disclosure: Deep TASE analyses are general informational, research, and commentary content only. They do not constitute investment advice, investment marketing, a recommendation, or an offer to buy, sell, or hold any security, and are not tailored to any reader's personal circumstances.
The author, site owner, or related parties may hold, buy, sell, or otherwise trade securities or financial instruments related to the companies discussed, before or after publication, without prior notice and without any obligation to update the analysis. Publication of an analysis should not be read as a statement that any position does or does not exist.
The analysis may contain errors, omissions, or information that changes after publication. Readers should review official filings and primary sources before making decisions.