Internal portals
& dashboards.

The information is there.
Finding it should not
be another job.

We build portals and dashboards that bring the right information into one place. Your team or customers can see what is happening and, where needed, take the next step.

To answer a simple question, someone opens a spreadsheet, checks an inbox and asks a colleague. Customers call for updates your team already has.

Book a first call See an example
01 / Where it helps

What could your portal
or dashboard help people do?

Your business may work across teams, languages and currencies. A shared view should make the relevant details clear without asking everyone to learn all the tools behind it.

01

A workspace for your team

See incoming work, assign it to a colleague, deal with missing details and follow a task through to completion.

People can see who is responsible and what is waiting.

02

A portal for your customers

Let customers find their documents, check a request and complete the next step without calling for an update.

Each customer can only access their own information.

03

A dashboard for decisions

Bring the numbers you use into one view, with their source, currency and last update.

Your team can check what is behind a number and spot missing information.

These are examples of possible projects. We agree the tools, access and checks with you before building.

02 / How it could work

An invoice needs attention.
Finance can deal with it here.

This example shows a colleague correcting invoice details through a portal connected to the existing accounting tools.

  1. 01

    Sign in

    Show the work this person is allowed to see.

  2. 02

    Open

    Find the task and original invoice.

  3. 03

    Correct

    Prepare the change and explain why.

  4. 04

    Review

    Ask for approval where it is needed.

  5. 05

    Save

    Check the correction was saved and show the result.

Did that change actually save?

If a connection fails or a record has changed since it was opened, the screen should explain what happened and what to do next. It should not show success just because someone pressed the button, or create a duplicate when they try again.

The portal gives people a place to work. Automation can take care of recurring steps behind it. Both can be part of the same project.

03 / Planning the first version

Who is using it?
What do they need to do?

We start with a useful task for a specific group of people. That gives us a reason for each screen, chart or button we build.

Questions that shape the first version
AreaWhat we ask
PeopleWhich employees, customers or partners need it?
InformationWhich tools hold the details, and which version should we show?
Timing and currencyHow recent must the information be, and how should CHF/EUR figures appear?
ActionsWhat can people change, approve or undo?
UsefulnessCan someone complete the task and see that it worked?
04 / Projects and reading

See the thinking
in practice.

These projects include dashboards for reviewing customer feedback and cleaning activity. They show different ways to make information useful. Your portal would be built around its own users and tasks.

Dashboard / Customer feedback

See what customers keep talking about.

Alongside a weekly feedback report, a dashboard shows which topics are mentioned most each week, helping the product team review recurring themes.

See the feedback project Dashboard / Inspection pilot

Give managers a way to review the work.

During the pilot, a dashboard let managers review cleaning activity by location, worker and period. The pilot informed further work. It was not a production-wide inspection rollout.

See the inspection pilot
05 / How we work together

Make a first version
people can try.

We agree what the first version should do, how to check it and who will look after it. Then we work through it with your team.

  1. 01

    Understand the task.

    We look at who does the work, what they need to see and where they get stuck today.

  2. 02

    Walk through the screens.

    Using examples, we check the usual task, empty results and things going wrong, along with the languages and currencies you need.

  3. 03

    Connect and test.

    We connect the tools and check access, old information, failed changes and whether saved results reach the right place.

  4. 04

    Prepare the handover.

    We document access, data sources and support, and agree how your team will manage changes.

06 / Access and upkeep

People see what they need.
Changes are easy to follow.

Check access behind the screen.

We test which records and actions each role can use, including keeping customers’ information separate.

Know where data goes.

We identify the app hosting, connected tools, exports and backups, including where customer and employee information is processed.

Agree what the numbers mean.

We work with the person responsible for each measure, keeping currency, time period and source clear.

Keep your team in control.

You own the agreed code and accounts. Handover covers managing access, dealing with failed connections and making changes.

07 / Questions before you start

Portal and dashboard questions.

How is a portal different from automation?

A portal gives a person a place to see information and take action. Automation handles recurring steps between tools. A portal can show work waiting for approval or the result of an automation.

Do we have to replace our tools?

We start by looking at the tools you already use and what they can share. Often the useful first step is a better way to work across them.

Can employees and customers use it?

They can be included in the same project with different access. We test what each group can see and change, including keeping each customer’s records separate.

Will the numbers update live?

We agree how current they need to be for the decision you are making and check what the source tool supports. The dashboard should show when information is old or unavailable.

Can it support our languages and currencies?

We agree the languages, number formats and CHF/EUR handling. We test labels, source content and calculations with examples from your work.

Can people change records through it?

Where the connected tool allows it, yes. We check inputs, record who changed what and confirm the result was saved. Some actions may need another person’s approval.

What happens if a connection stops working?

The screen should show what is unavailable, avoid false confirmations and explain the next step. We agree who handles unresolved problems.

What does a first project cost?

First projects start from CHF 4,800 for an agreed portal or dashboard scope. We confirm who will use it, what they need to do and which tools it connects to before estimating timing. Hosting, software and support costs are set out in the proposal.

Other services

What else could help?

Need help with another part of the work? Find the service that fits.

What should your team
be able to do in one place?

Tell us who needs it, what they need to see and where the task gets stuck. We’ll explore a useful first portal or dashboard together.

Book a first call