Sales and invoicing
Quotes, orders, deliveries, invoicing, payment tracking and reminders. From the first customer contact to cash collected, with no re-keying and no forgotten invoice.
Division 02 · IBWAH Tech
Your platforms, apps and software.
We design and develop web platforms, mobile applications and business software. From a product facing your customers to the digitisation of your internal processes.
+15
web and mobile products shipped
+10
internal processes digitised
What we build
Web platforms, mobile applications and business tools.
We build platforms open to your customers as readily as consumer mobile applications or management software reserved for your teams. The common thread: a product that holds up in real conditions, in the field and over time.
- Web platforms
Websites and web apps, customer or supplier portals, marketplaces, internal portals, back offices. Reachable from any workstation, with nothing to install.
- Mobile applications
Android and iOS apps, consumer or business. Designed to stay usable when the connection is poor or absent.
- Business software
Management tools shaped around your actual organisation, not the other way round. Roles, permissions, approval flows and your own vocabulary.
From the notebook to the dashboard
The same information, but reliable, shared and available in real time.
Our specialty
And one specialty: what still runs on notebooks and spreadsheets.
In most of the companies we work with, the information exists, but it is scattered. A notebook in the warehouse, a spreadsheet in accounting, phone messages for urgent orders. Everyone works from their own version of the numbers.
The cost is twofold: time lost re-entering and reconciling, and a loss of visibility over your own business. You no longer know exactly what is left in stock, what has been invoiced, or where an order actually stands. That is the precise point we address.
- A single source
One database, one version of the numbers, available to those who need it.
- Data entered once
What is captured once is never retyped: the invoice follows from the order, not from a copy and paste.
- Immediate visibility
Dashboards that answer the questions you actually ask yourself every week.
Process digitisation
The processes we digitise
We step in where manual work costs the most. A project rarely starts everywhere at once: we prioritise the most painful process first.
Operations and inventory
Inbound and outbound, stock counts, reorder thresholds, work orders, material consumption and traceability. You know what you hold and where production stands.
People and reporting
Employee records, attendance, leave, variable payroll inputs, and dashboards by activity, site or period. The numbers you decide on, available when you need them.
And beyond. The list is not exhaustive: any process running on manual entry or scattered files falls under the same approach.
Submit your project
How a project runs
Ship a useful first version early, then widen
We do not build for six months to deliver a product nobody uses. You see it and test it very early.
01
Framing
We start from real usage: who will use the product, for what, and under what conditions. Where an internal process is involved, we observe it as it is actually practised rather than as procedures describe it. We then set the scope of the first version.
02
Design
Data model, user journeys and mockups of the key screens. You validate concrete interfaces before a single line of code is written.
03
Iterative development
Regular releases you test as we go. Adjustments happen along the way, while they are still cheap, rather than at final acceptance.
04
Go-live and support
Deployment, migration of existing data where there is any, user training, documentation and a period of close support. A product only succeeds once it is adopted.
Frequently asked
What people ask us most
No, and we advise against it. The projects that fail are almost always the ones trying to cover everything from day one. We ship a first version built around the main use, then widen once it is adopted.
It is a design constraint we take seriously. Simplified screens, your own vocabulary, fewer clicks, hands-on onboarding. A product more painful than the current way of working will not be used, and the project has failed.
If you are starting from something existing, it is migrated: spreadsheets, exports from an older system, sometimes manual capture from paper ledgers. Migration is part of the project and is prepared during development, not the day before go-live. For a product built from scratch, the question does not arise.
Ownership of the code, hosting and maintenance terms are set explicitly in the contract before work begins. We favour arrangements that do not lock you in and that leave you in control.
Yes. A period of close support follows go-live, then a support arrangement matched to your actual usage: fixes, enhancements and version upgrades. Your business changes, and the product has to follow.
Yes, after auditing what exists: code, data, hosting, documentation. We tell you frankly whether it is better to continue or to restart on sound foundations, with the cost and schedule difference between the two options.
IBWAH Tech
What product do you have in mind?
Describe the intended use and who it is for. We will tell you what can ship first, and what can wait.