Custom Dashboard Development: Turning a Business Workflow into a Working Portal

On this page

A dashboard depends on the records behind it. Before an owner can see "jobs completed this week", someone needs to create a job, assign it, update its status and confirm completion. Custom dashboard development often includes that workflow as well as the reporting screen. This guide traces one example from enquiry to report and shows how it becomes a portal with roles, approvals, history and useful numbers.

Start with one workflow, not a list of screens

This example is illustrative, not a client project. Brightside Facilities is a regional commercial cleaning company with office staff, several crews and contract clients. Its workflow is:

  1. Enquiry. A request arrives by web form, email or phone. It becomes a record with a source, site address, service type and status of New.
  2. Quote. An amount and document are attached. The status becomes Quoted, with an expiry date.
  3. Job. The client accepts. A job is created with a schedule and links to the original enquiry and client record.
  4. Assignment. An operations manager assigns a crew. Scheduling conflicts are checked before the assignment is confirmed.
  5. Status updates. The crew lead marks On site and Done from a phone. The office can review the update and ask for corrections.
  6. Report. At month end, approved completed jobs feed the client's report and an export for invoicing.

Office staff, an operations manager, a crew lead and a client contact each need a different view. Write your own version in six lines before commissioning a portal. Include exceptions such as a rejected quote or a cancelled job, even if they are outside the first release.

The parts of the portal, mapped to the example

Roles and permissions. Office staff manage enquiries. The operations manager assigns and approves jobs. Crew leads see their assignments and update permitted fields. Client contacts see their own sites and reports. Write a grid of roles against actions, including who may delete, export or invite another user. Give each role only the access it needs.

Records and statuses. A quoted enquiry and a scheduled job are related records with different responsibilities. Each status needs an owner and clear rules for moving to the next step. Keep a link to the original request so staff can understand how the work began.

Search and filtering. Useful filters include status, client, crew, date and site. Saved views such as "my crews this week" or "quotes expiring soon" can be more useful than a general search box. Start with the questions staff need to answer repeatedly.

Approvals. A quote above an agreed amount might require manager approval. A completed job might need an office check before invoicing. Record who approved it, when and what was approved. Include what happens when it is rejected or the approver is unavailable.

Audit history. Record meaningful changes with their actor and time. Decide what needs to be retained and who can read the history. Audit logging is easier to plan alongside the workflow than to reconstruct after a dispute, but its scope and storage still need estimating.

Reporting and exports. Define each metric rather than relying on its label. Does "completed" mean a crew marked Done or the office approved it? A monthly report and CSV export should use the same definition. A dashboard helps people inspect records; it does not make inaccurate data correct by itself.

Integrations and automation. A web form may create an enquiry, an email may notify a crew and an accounting integration may receive invoice lines. Each connection needs a direction, failure handling and an owner for errors. Payment or e-commerce integrations add their own states and reconciliation work. Begin with the connections that remove a real manual step.

Access boundaries. Restrict access on the server and, where appropriate, in database policies. Hiding a button is not an access check. PostgreSQL row-level security can restrict which rows a role can read or change, but some privileged roles bypass it. Policies and server-side access paths both need testing. See PostgreSQL's row security documentation.

A sensible first release

For this example, suppose the immediate problem is internal coordination. A possible first release includes:

  • Enquiry and job records with agreed statuses.
  • Three internal roles: office admin, manager and crew lead.
  • Assignment and conflict checks.
  • Mobile-friendly crew updates.
  • Office approval and one monthly report.
  • A CSV export, assignment emails and a reviewed import of the current spreadsheet.

The client portal, accounting integration, photo attachments, recurring-job templates and payments could follow. That is a choice for this example, not a rule for every business. If clients must approve quotes themselves, their portal may belong in the first release.

Choose one workflow people can complete from start to finish. A small usable release is more informative than ten screens with missing connections. The admin-panel guide covers screen requirements, while spreadsheets vs a custom dashboard helps assess whether custom development is needed yet.

What changes the scope

These factors affect cost and timeline. Their impact depends on the starting point, so they belong in discovery rather than a generic price promise:

  • The number of roles, including permissions that vary by client or location.
  • Approval chains and exceptions.
  • Existing data quality, history and import volume.
  • One-way versus two-way integrations, retries and reconciliation.
  • Audit history, retention and export requirements.
  • Offline use or unreliable field connections.
  • Multiple businesses sharing one application.

Ask for an estimate that separates the first release, optional features and ongoing running costs. For custom CRM development, for example, a simple lead-and-follow-up workflow is a different scope from replacing sales, support and accounting systems at once.

The same approach in other portals

These are use cases to scope, rather than a list of claimed completed projects:

  • CRM and sales dashboards: lead, qualification, proposal, decision and handover.
  • Booking and staff scheduling: request, assignment, cover, approval and hour export.
  • Property and rental management: enquiry, viewing, tenancy, maintenance and renewal.
  • Multi-location operations: a shared workflow with local permissions and owner reporting.
  • Membership portals: application, approval, active membership and renewal.
  • Marketplace administration: listing review, publication, reports and resolution.
  • Subscription management: plan changes, invoices, payment failures and cancellation.

Each needs records, responsibilities and exception handling before its dashboard can be useful. A client portal developer needs to understand those rules as well as the screens.

Two relevant projects and my contribution

Clinical Stack is a staff scheduling product for multi-location clinics. It includes administration, staff mobile-web access, request approvals and payroll-ready hour reporting. I migrated it from Bubble to Next.js and Supabase while it stayed live, designed the Postgres schema with row-level security per practice, built the scheduling validation engine and WhatsApp integration, and wired Stripe billing. Payroll-ready exports do not mean an integration with a payroll system.

Spinfluence is a Bubble restaurant-engagement product with review analytics and multi-location accounts. My work included the diner flow, review analytics, rule-based replies, team management, a customer list and Stripe subscriptions. It is a relevant example of several operational views within one product, without treating every user as a platform administrator.

Tell me about your workflow

Send your goal, what you use today, the essential workflow and your desired timeline. Include who needs access and any systems that must exchange data. I can then propose roles, records and a first release, including whether a Next.js dashboard, Bubble application or existing tool fits the requirements.

Use the contact page, or read about management systems and dashboards for the service details.

Questions people ask

What is the difference between a dashboard, an admin panel and a portal?

A dashboard summarises information. An admin panel lets authorised staff manage records. A portal gives a group, such as customers or staff, access to relevant information and actions. One application can combine all three.

Should the client portal be in the first release?

Include it when client participation is essential to the workflow. If the immediate need is internal coordination, it may be sensible to stabilise that process first.

Can the portal import our existing spreadsheet?

An import can be included in the scope. Review the columns, duplicates, missing values and record relationships first, then test and reconcile the imported data.

Next.js or Bubble for a dashboard?

Compare the workflow, integrations, access requirements, budget and maintenance needs. Both require careful implementation. Next.js offers control over custom code and architecture; Bubble offers visual development within its platform.

How are access boundaries enforced?

Use server-side authorisation and appropriate database rules, and test access as different users. Review exports, background jobs and privileged service access as well as normal screens.

Have a project like this in mind?

Tell me what you're building