Internal Dashboard
From €2,500An operations view built around the questions your team actually asks.
- Authenticated access
- Operational views and reporting
- Status tracking
- Role-based access
- Data from your existing systems
- Handover
Services
All servicesDashboards & Portals
A dashboard is only useful if it answers the questions your team actually asks. We build authenticated areas around the way work already runs, rather than around a chart library.
What we build
Typical projects
A dashboard is only worth building if it answers a question somebody currently answers by asking around. A portal is only worth building if it removes work your team does by hand. Both start from the workflow, not from the screen.
- Authenticated areas
- Customer dashboards
- Operations dashboards
- Reporting
- Account management
- Internal workflow tools
- Role-based access
- Status tracking
What is included
In every project
What we need from you
- Who signs in, and what each of them should see
- Where the information lives today
- The questions it has to answer on day one
- Accounts, sign-in and permissions
- Role-based access
- The views your team actually needs
- Status tracking and history
- Reporting
- Connections to your existing systems
- Testing with real cases
- Handover and documentation
Starting prices
What it costs to start
A starting point, not a quote. The scope and the price are agreed in writing before any work begins.
Customer Portal
From €3,500A self-service area so customers stop emailing to ask for things they could look up.
- Customer accounts and access
- Account information
- Documents and history
- Requests and status
- Notifications
- Handover
Concept projects
What this looks like built
Concept projects built to demonstrate the work. They are not client projects and the data in them is sample data.
Concept project
Operations Dashboard
Work in progress that only exists in people's heads and in message threads. No shared view of what is running, what is stuck, and what finished this week.
See a conceptInterface concept. Sample data shown for illustration.
Concept project
Customer Portal
Customers emailing to ask for a copy of an invoice, the status of a request, or a document that was sent months ago - and a team answering the same questions by hand.
See a conceptInterface concept. Sample data shown for illustration.
Common questions
Before you ask
- What is the difference between the two?
- An internal dashboard is for your team and is about visibility. A customer portal is for your customers and is about self-service. Some projects need both, and they are scoped together.
- Can customers see their invoices and documents?
- That is usually the point of a portal. What they can see is decided by you and enforced on the server, not hidden in the interface.
- Do we have to replace our existing systems?
- No, and usually you should not. A dashboard is generally most useful sitting on top of what you already run.
- Have you built one of these?
- The concept projects above are ours, built to demonstrate the work. They are not client projects and the data in them is sample data.
Have a dashboards & portals project in mind?
Tell us what you need it to do. We will come back with a scope, a price and a timeline, or tell you if a smaller piece of work would get you there.