Question 01
What is it?
One industrial edge product for machine data, remote service, local applications, and predictive maintenance.
Orenda Box installs beside a PLC. It reads the 5–20 signals that matter for the service problem—machine state, output, stops, alarms, temperatures, counters, and downtime—and records that operating history on site.
MES, SCADA, PLC diagnostics, and other approved applications run locally on the Box. Orenda Connect lets an authorized technician open the exact machine resource assigned to them from desktop or mobile, instead of opening the customer's whole network.
The AI layer analyzes recent production and maintenance history to rank recurring problem areas, generate service reports, create smart alarms, and recommend the next check. It can flag a developing issue before it becomes an obvious customer complaint.
- Machine context: selected PLC signals become runs, stops, alarms, trends, downtime, and OEE
- Local operations: MES, SCADA, diagnostics, and approved edge applications run beside the machine
- AI maintenance: risk patterns become reports, smart alarms, and recommended checks
- Remote service: technicians open only the approved machine resource through Orenda Connect
Question 02
Who is your customer — and what do you know that others do not?
We start with export-oriented builders of PLC-controlled food and packaging machines that remain responsible after every delivery.
The buyer is the owner or after-sales service leader at a 20–500-person machine builder producing approximately 5–10 machines per month. When a customer reports a stop, the service team often starts with a telephone description and screenshots, then sends a senior technician without the machine history needed to diagnose the issue remotely.
Our insight is that this buyer does not need another connection tool. It needs an OEM-ready service product: hardware, PLC context, local applications, controlled access, AI analysis, updates, and recovery in one package that can be standardized on a machine model.
An İzmir tortilla-machine builder tested competing products before testing Orenda's complete workflow. Orenda covered the full machine-side platform it needed, and the builder signed a letter of intent. The next milestone is a paid machine-model standardization.
Distribution is built into the model. Machine builders attach Orenda to compatible new machines. Automation providers sell, install, and support it through their existing project teams. The first automation partner has already ordered three Box batches.
The customer is not buying remote access. The customer is buying a service product that can ship with every machine.
The customer insight
Question 03
What is the white space?
The market has powerful access tools and broad edge ecosystems. Orenda turns the pieces into one machine-builder-ready product.
Remote-connectivity leaders are built to reach industrial endpoints. Industrial-edge leaders provide broad platforms for data and applications. Predictive-maintenance vendors sell analytics projects after the machine data is integrated. A mid-sized machine builder still has to select, integrate, provision, support, and maintain the complete stack.
Orenda productizes that stack as one Box, one machine-model configuration, and one required subscription. It combines selected PLC context, local MES and SCADA, resource-specific service access, AI maintenance, provisioning, updates, and recovery.
We are not trying to out-portfolio Siemens or out-scale TeamViewer. We win when a machine builder wants a compact service layer it can integrate once and sell with the next machine. The İzmir test is the first signal: after testing alternatives, the builder chose Orenda as the complete platform and signed an LOI.
Defensibility compounds through accepted machine-model configurations, supported PLC integrations, trained resellers, and the growing fleet of subscribed Boxes.
Category map
| Alternative | Primary job | Orenda's wedge |
|---|---|---|
| TeamViewer Tensor / Schneider Secure Connect | Remote connectivity to PLCs, HMIs, and industrial systems | Connectivity plus machine history, local apps, AI maintenance, and Box lifecycle |
| Siemens Industrial Edge | Broad industrial data, application, and device ecosystem | Compact OEM package priced and configured to ship with a machine |
| Predictive-maintenance projects | Specialized analysis after data integration | PLC data, local record, smart alarms, reports, and service workflow in one deployment |
The white space is not another dashboard. It is the service and AI layer that a machine builder can ship as part of the machine.
Category position
Question 04
Why now — and how big?
Industrial companies want AI-driven service, but most machines still lack the structured history that makes AI useful.
Deloitte found that 92% of manufacturing executives expect smart manufacturing to improve competitiveness, while only 29% report AI or machine learning deployed at facility or network level. The implementation gap is machine context: useful signals, recorded history, and a workflow that turns analysis into a service action. Orenda supplies all three beside the machine.
Europe contains a dense, reachable target base. VDMA represents 3,500 mainly medium-sized machinery companies, and European machinery generated almost €900 billion in 2025. Orenda's 12-month target of 20 integrated builders is only 0.6% of VDMA membership.
At 5–10 machines per builder per month, 20 integrated builders create 100–200 new Box placements every month, or 1,200–2,400 per year. Across the €1,000 standard and €1,200 Global SIM products, that is €1.2–€2.88 million in annual hardware revenue and €960,000–€2.196 million in hardware gross profit. Installed-base retrofits, integration work, and required subscriptions add on top.
Question 05
Show, do not tell.
In 101 seconds, a technician moves from “the line stopped” to a ranked first check and controlled machine access.
The demo starts with a stopped tortilla line. Orenda MES surfaces 10 recorded breakdowns, an 84.4 risk score, a 16.95-point OEE decline, and 6.1 hours of downtime in Oven Zone 2.
A live model call turns that operating history into a maintenance analysis: recurring problem areas, risk indicators, a service report, smart alarms, and the recommended first check. The workflow then moves to Orenda Connect, where the technician opens only the assigned machine resource.
- See the machine state and production history
- Rank the highest-risk area from recorded context
- Generate the maintenance report and first recommended check
- Open the approved machine resource through Orenda Connect


Question 06
What does the desired future state look like?
By August 2027, 20 machine builders ship Orenda as a standard component and 10 trained resellers deliver it without founder-led field work.
At full attach, the builder channel adds 100–200 Box orders and 100–200 required subscriptions each month. That creates €100,000–€240,000 in monthly hardware revenue and €80,000–€183,000 in monthly hardware gross profit.
Ten resellers qualify sites, install and commission Boxes, onboard customer teams, and provide first-line support. Orenda owns product supply, quality assurance, software, training, and second-line support.
Stock changes delivery from a constraint into an advantage. Standard units dispatch immediately from tested inventory. A defined 20-unit batch is assembled, tested, and ready to dispatch within 14 days instead of today's one-to-two-month lead time.
Question 07
Where is the demand?
The first channel has already reordered twice: 20 Boxes across three billed batches, 15 paid, and the first 10 live.
From April through July 2026, the same automation partner accepted three Box batches: 10 units billed at €8,500 after the launch discount, followed by 5 units at €5,000 and another 5 at €5,000. That is €18,500 in net product billing from one repeat buyer.
Fifteen of the 20 Boxes are paid. The first 10 shipped on 28 July 2026 and are deployed and active. The reseller channel has completed the path from first order through reorder, payment, shipment, deployment, and live use.
The first invoiced cohort also demonstrates attractive product economics. Against €4,000 of manufacturing and packaging cost, €18,500 of net billing creates €14,500 in hardware gross profit—a 78.4% margin after the launch discount.
The machine-builder route is next. The İzmir tortilla-machine builder tested competing products, then tested Orenda's hardware, remote service, machine integration, and AI workflow before signing an LOI. The next commercial milestone is a paid standardization project.
One partner. Three batches. 20 invoiced. 15 paid. 10 live.
Demand in one line
Question 08
What are the economics?
Each Box produces €800–€915 in hardware gross profit, followed by required subscription revenue.
A standard Box sells for €1,000. Manufacturing and packaging cost €200, leaving €800 in hardware gross profit and an 80% hardware gross margin.
A Global SIM Box sells for €1,200. Manufacturing and packaging cost approximately €285, leaving approximately €915 in hardware gross profit and a 76.3% hardware gross margin.
Every Box requires Orenda Connect. Current published plans are Launch at €14.50 per month, Growth at €39.50, and Scale at €99.50. Each deployment therefore adds €174–€1,194 in annualized subscription value.
Machine-model integration is charged separately; current proposals price engineering at €450 per day. The commercial stack is simple: integration revenue when a model is standardized, high-margin hardware revenue on every machine, and recurring software revenue across the active fleet.
Per-Box unit economics
| Unit | Revenue | Manufacture + package | Hardware gross profit | Margin |
|---|---|---|---|---|
| Standard Box | €1,000 | €200 | €800 | 80.0% |
| Global SIM Box | €1,200 | ≈€285 | ≈€915 | ≈76.3% |
| First 20 invoiced | €925 average | €200 | €725 average | 78.4% |
Question 08B
How does revenue compound?
Integration earns once, hardware earns on every machine, and subscriptions stack across the active fleet.
A paid standardization creates one accepted configuration for a machine model. The reseller can deploy that configuration repeatedly without restarting the engineering project.
One builder producing 5–10 machines per month adds 60–120 Box sales per year. That creates €60,000–€144,000 in hardware revenue, €48,000–€109,800 in hardware gross profit, and 60–120 new Connect subscriptions.
Across 20 builders, the model reaches 1,200–2,400 new units and subscriptions per year. At the current Growth price, that annual cohort represents €568,800–€1,137,600 of annualized subscription value. Installed-base retrofits and plan expansion compound on top.
The subscription base accumulates instead of resetting: 100 active Growth-plan Boxes equal €47,400 in ARR; 1,000 equal €474,000 in ARR. More users, applications, and vendor workflows increase revenue without another hardware sale.
- Standardize once: paid integration creates the reusable machine-model configuration
- Deploy repeatedly: each compatible machine produces €800–€915 in hardware gross profit
- Remain connected: every active Box carries recurring Orenda Connect revenue
- Expand in place: more users, applications, vendor access, and installed-base machines raise account value
Question 09
What is the wedge — and how does the model resolve?
The wedge is a paid OEM standardization package that a reseller can copy to the next machine without founder engineering.
The package contains one €1,000 standard or €1,200 cellular Box, 5–20 selected PLC signals, one local operating view, one approved remote-service resource, one AI maintenance report, one machine-model template, and a written acceptance test. Integration is charged separately and the Box carries a required Connect subscription.
The İzmir LOI is the first target conversion. The program objective is to deliver the first useful service workflow within five business days of a site-ready installation and complete acceptance within 14 days.
The model resolves when the builder pays, accepts the reusable configuration, places the next Box order, and a trained reseller completes the repeat installation. At that point one engineering project has become a repeat hardware-and-software channel.
The wedge is not a pilot that ends. It is the first paid configuration of a product the builder can ship again.
Resolution logic
Question 10
Is this the business you were meant to build?
The founders combine machine-side engineering, distributed systems, and the firsthand service problem that created Orenda.
Ömer encountered the problem while leading manufacturing-software work at Dera Technology. After a machine left the factory, diagnosis started with calls and screenshots because the service team lacked one complete view of the machine. Orenda is the service platform he needed in those projects.
Ömer Akgül studied computer engineering and electrical engineering. His background spans Aselsan cryptography work, semiconductor architecture at Yongatek, embedded systems, industrial software, customer projects, field deployment, and commercial delivery.
Suna Ayhan brings enterprise and distributed-systems experience from Softtech, SabancıDX, and Microsoft. She leads the product architecture and software quality behind Orenda's device, access, application, and update platform.
The founders have worked together since co-founding the Creatiny student club. They spent approximately three years developing Orenda, moved to full-time execution, built the hardware and software stack, invoiced the first 20 Boxes, and completed the first international deployment.


Question 11
Why build this with Gateway X?
Orenda has the product and first paid deployments. Gateway X can help turn them into a repeatable, profitable OEM channel.
The 12-week objective is concrete: convert the İzmir LOI and one additional partner into paid projects, fix the standard offer and its economics, make one integration reusable, prepare two reseller teams, and remove the current supply delay.
Jesse Pujji can sharpen the first customer profile, standardization offer, pricing, objection library, and founder-led sales cadence. The output is a weekly partner funnel that turns conversations into paid machine-model projects.
Adam Brakhane can define the smallest valuable AI-maintenance workflow and lock its product scope, model cost, reliability standard, and price. The output is one repeatable workflow that a reseller can demonstrate and deploy.
Nak Patel can turn founder delivery knowledge into the reseller qualification process, operating scorecard, quality system, stock policy, and reorder cadence. The output is a partner capable of delivery without founder-led field work.
Program capital supports demand-gated inventory: 10 tested standard units ready for immediate dispatch and a defined 20-unit batch ready within 14 days. That replaces today's one-to-two-month supply delay with a channel-ready delivery promise.
- Weeks 1–4: complete 20 partner conversations; fix the ICP, offer, pricing, funnel, and fully loaded economics
- Weeks 5–8: convert the İzmir LOI and one additional partner; deliver the first reusable standardization
- Weeks 9–12: qualify two reseller teams; hold 10 tested units; prove a 20-unit, 14-day replenishment run
By week 12: 20 partner conversations, two paid projects, one reusable machine-model integration, two reseller teams ready, 10 tested stock units, and a 20-unit batch ready within 14 days.
The Fellowship scorecard
