Irondell — digital systems
Three systems.One business.
The ERP that operates it, the website that grows it and the app that carries it — architected together, on one foundation.
Collection
- Order placed
- Payment cleared
- Packed
- Out for delivery
- Delivered
A business does not experience its software as three products.
It experiences one operation: an order arrives, someone acts on it, a customer is told, a number moves. Irondell builds the ERP, the website and the app as one architecture, because that is how the business already works.
- ERPOperations
- runs the business internally
- WebsiteExperience
- presents it and converts demand
- AppMobility
- carries it to customers and crews
One order. Six systems that don’t speak.
This is how most businesses actually process a sale. Every hand-off below is a place where information is re-typed, delayed or quietly lost.
- 01Website formExported by hand
- 02Email inboxSomeone must notice it
- 03SpreadsheetOn one person’s laptop
- 04WhatsAppNo record kept
- 05Accounting toolRe-typed monthly
- 06Delivery sheetNever reaches the customer
In a Irondell system there are no hand-offs.
One record, written once, read by three surfaces. The customer sees the same truth the workshop does, at the same moment the accountant does.
What the three surfaces share.
Not an integration between three products — one data foundation with three ways in. This is the architecture every Irondell engagement is drawn against.
| Shared entity | ERP | Website | App |
|---|---|---|---|
| Customer identity | R/W | R/W | R/W |
| Orders & bookings | R/W | R/W | R/W |
| Inventory & availability | R/W | READ | READ |
| Workflows & routing | R/W | — | READ |
| Staff & permissions | R/W | — | READ |
| Payments | R/W | R/W | R/W |
| Notifications | R/W | — | READ |
| Reporting | R/W | READ | — |
Read / write per surface is decided per client during architecture. The table above is the pattern, not a fixed contract.
The system behind the business.
Not software your team adapts to. An operational system architected around how your business already runs — then made faster than it was.
Below is a working Irondell console. Advance the order or reassign it: you are changing a real record held in this page, and the website and app further down read the same one.
On modules
Modules are composed per client. Customers, orders, inventory, staff, approvals, documents, reporting and automation are common starting points — not a fixed bundle every business receives.
Nadia Hafez
12,400 EGP
Atelier Coat — Camel, M
- Placed
- Paid
- Assigned
- Packed
- Shipped
- Delivered
Live component, not a screenshot. Concept data — no client is depicted.
A website that does more than represent the business.
The public surface of the same system. Prices, availability and bookings are not copied here — they are read from the record your operation is already keeping.
Switch between concepts to see the same architecture carry a different art direction per industry. The retail concept reads its price and stock from the console above.
Three Irondell-owned concepts. Brands, prices and availability are illustrative.
In their pocket, on your system.
A customer app, a crew app, or both. What it does depends entirely on your operating model — what it never does is disagree with the ERP.
The timeline and the notification below are derived from the same order. Nothing here is scripted; advance the order and this surface answers.
Atelier Coat — Camel, M
- Placednow
- Paid
- Assigned
- Packed
- Shipped
- Delivered
Irondell system demonstration — the same order as the console above.
One record. Three surfaces. No hand-offs.
Every surface below is live and shares one state. Advance the order once and watch the operation, the storefront and the customer’s phone change together — because there is nothing to synchronise.
The order arrives from the website and opens in the operations queue.
Nadia Hafez
12,400 EGP
Atelier Coat — Camel, M
- Placed
- Paid
- Assigned
- Packed
- Shipped
- Delivered
Atelier Coat — Camel, M
- Placednow
- Paid
- Assigned
- Packed
- Shipped
- Delivered
Irondell system demonstration. All three surfaces above are live components sharing one in-page record — concept data, no client is depicted.
What this becomes, per industry.
Irondell-owned concepts, not client work. Each one is a sketch of how the three surfaces would divide the work for a business of that shape.
- ERP
- Patients, charts, scheduling, practitioners, consumable stock, billing
- Website
- Treatments, practitioner profiles, direct booking with live availability
- App
- Appointments, reminders, results, follow-up, payment history
Design, operations and engineering, in one engagement.
Irondell is not a design studio that subcontracts the hard part, or a software house that outsources taste. The same team draws the data model and the type scale.
- 01UnderstandAn operational map of how the business really runs
- 02MapEvery hand-off, bottleneck and exception, named
- 03ArchitectThe shared data model and surface boundaries
- 04DesignOne visual language across all three surfaces
- 05EngineerWorking software in review-able increments
- 06ConnectPayments, accounting, messaging, existing tools
- 07LaunchMigration, staff training, supervised go-live
- 08EvolveNew modules and markets, same team
What we build in-house
- Business operating systems
- Web applications
- Mobile applications
- APIs & integrations
- Workflow automation
- Data modelling
- Authentication & permissions
- Payments
- Cloud infrastructure
- Analytics & reporting
- Notifications
- Security & access control
Listed as outcomes rather than frameworks. You are buying an operation that works, not a stack.
Scoped to your operation. Priced to its scope.
There is no package price because there is no packaged system. What an engagement costs follows from what it has to do.
- A scoping conversation costs nothing
- Fixed, written proposals before any commitment
- Phased delivery — the system earns trust as it is built
What moves the number
- Operational complexity and workflow depth
- Number of users and roles
- Integrations with systems you already run
- Data migration and history
- Application scope — customer, workforce, or both
- Automation, security and infrastructure requirements
- How long we keep building after launch
The beginning
The system your business should have been built on.
Tell us how your operation runs today. We will show you what it looks like as one system.