Electronic invoice management: all in one panel
No customer of the service could see the state of their own invoices, so every question became a support ticket.
Web apps inside the systems you already have
Web apps, portals and B2B e-commerce that have to fit inside the systems a company already has: permissions, integrations, and where the software runs.
Where we have already done it
VoIP Software: Complete Traffic Management
Voice traffic pulled out by hand into an Excel sheet, with customers going from 400 to 2,000.
New metal scrap marketplace
Scrap was traded on the phone and settled on a spreadsheet, with no way to know who you were dealing with.
When is a web app worth it?
When the people using it sit at a browser and have to see data that lives in other systems. A web panel can show your customers where their requests stand, instead of making them write to support. It is updated in one place, and nothing gets installed on company computers.
A company web app goes into a place where there are already systems, users and rules about who sees what.
We develop web applications for work: portals for customers and suppliers, control panels, e-commerce and marketplaces between companies. If you are still deciding between a web app and a native app, it depends on what the people who work have in their hands: we cover it on the apps page.
Permissions, data, users from other companies
In the panel we built for A-Cube each user sees only the operations they are allowed to perform. Permissions change over time and every screen has to respect them, which is why the panel starts from the role of whoever opens it. It is written in React, on the platform’s APIs.
The software we wrote for Vituma, a telecommunications operator, reads call flows from the exchanges and calculates the cost on the customer’s price list. For security and privacy reasons it runs in a private space of the customer’s: the choice was made before writing the code, because it changes the architecture.
And there are web apps used by people from different companies, like a B2B e-commerce. Zeggio Rottami asked us for a marketplace that would bring together supply and demand in the sector: sellers, buyers, factories and hauliers on the same platform. Trading was allowed only between verified companies, with an accreditation process and the tracking of operations. Before, that trading went through the phone and spreadsheets.
The questions we ask first
On the first call we ask four, because they change the architecture more than the choice of framework:
- Who opens the application, and with which credentials that already exist.
- Which systems have to read from it or write to it, and who wrote them.
- Where it has to run, and who will work on it after us.
- How many people use it at the same time at the worst moment of the day.
How we work
In phases, each with a date, and the next phase is decided on the results of the one before. The method in full also explains the guarantees after release.
Source, documentation and environments stay yours: if one day your team takes the application forward, there is nothing to buy back.
What happens if it goes wrong?
Guarantees- The code is yours
- You can stop at any phase
- If something does not work, we fix it
- Maintenance can have guaranteed times
- The project does not rest on one person
Frequently asked questions
What is the difference between a web app and a website?
A web app is for working: it keeps state, handles permissions, writes to a database and connects to other systems. A website is for reading.
When do you need a native application instead?
When the work needs the camera intensively, rapid-fire barcode reading, working without a network for hours, or access to specific hardware such as industrial terminals.
Does a web app work without a connection?
A web app installable on the phone works offline too and syncs when the network comes back. It is the middle road for projects that sit between the browser and the native app.
How much does a web app cost?
The price is moved mostly by two things: how many systems it has to read and write, and how many users use it at peak hours. A web app connected to an ERP with a hundred simultaneous users is not in the same range as a portal for twenty customers. The order of magnitude is on «How we work».
Is a B2B e-commerce a web app?
Yes. Price lists and conditions per customer, recurring orders and the connection to the management system are application work, and they are built as a web app.
Tell us about the project you have in mind.