Portals and internal apps
Your daily work in one interface that fits your business.
- Area
- Web and commerce
- Starting point
- Quote for your project after the first conversation
What a portal or internal app brings together
Orders in an Excel spreadsheet, job reports on paper, documents on the server and approvals by email: everyone knows where something is, just not all the same thing. A portal or internal app brings what your team needs every day into one interface with clear access rights. Customers or employees see exactly what is meant for them.
Portals for customers and team
We build a customer portal, a staff app or an admin interface, depending on who will work with it. You describe the tasks that are cumbersome today, and we turn them into screens that we review together.
Overviews of orders and documents
Orders, documents, job reports and approvals appear in overviews that fit your workflows, with status and responsibility. Your business decides which details matter and in which order work is done.
Define roles and access
Roles determine who sees what and who may change what: the fitter their own assignments, the office manager all orders, the customer their documents. You define the roles; we implement them.
Example scenario (fictional)
Portals and internal apps in practice
A caretaking company with several properties and field staff currently manages assignments by phone and paper job reports. In the internal app, staff see their assignments for the day and record the job report with a photo on site; the office sees open tasks per property. Property management companies, as customers, can view the job reports and invoices for their properties in the portal.
How you can tell it fits
- A good fit if spreadsheets and email approvals run your day-to-day work and nobody knows the current status.
- A good fit if customers regularly ask for documents or the status of their order.
- A good fit if standard software does not fit your workflow and you need something of your own.
What is included and what is not
A custom application is built in clearly defined steps; we define the first step together, and extensions follow as needed. Hosting, access and the question of which data belongs in the application stay with you and are listed separately.
Starting point
We prepare a separate quote for this.
A single existing workflow can also be a sensible starting point. You describe it, and we tell you what we can solve properly to begin with.
Quote for your project
after the first conversation
The first conversation costs nothing. Before we start, the quote sets out:
- the scope
- your input
- the sign-off
- the price
Licences, hosting and additional services are listed separately.
Two questions before you start
Is a custom application not much more work than standard software?
If standard software fits your workflow, we recommend it. A custom application is worth it where you would otherwise have to adapt to the software every day; in the first conversation, we tell you openly what we would recommend.
Can we start small?
Yes, for example with one overview or the workflow that causes the most trouble today. Once that part works day to day, further areas are added.
The first conversation costs nothing.
Abbas and Shervin take the time to understand how your workflow runs today.
Write directly to abbas@fehablabs.ch or shervin@fehablabs.ch, or use the form.