All examples

Illustrative example

A 10-person engineering consultancy

A client portal that replaces the email thread

Clients submit requests, upload documents and follow progress in one place, and the team works from a single queue.

Client requests

  • New request: site inspectionPortal
  • Building permit, 3 documentsClient upload
  • Report ready for client reviewTeam
  • Report approvedClient
Typical stack
Next.js, PostgreSQL, n8n, Gmail/Outlook, Slack/Teams

The situation

Projects are run over email.

Clients send documents as attachments, ask for status updates, and approve reports by replying to a thread. Files end up in several inboxes and on a shared drive with no clear latest version. New clients and new employees are set up by hand, from a checklist that lives in someone’s head.

What we would build

  1. 01

    A web portal where clients log in to submit requests, upload documents and see the status of each project

  2. 02

    A single work queue for the team, with an owner and a deadline on every request

  3. 03

    Approval steps for reports, recorded with who approved and when

  4. 04

    Onboarding workflows that create the client workspace, folders and accounts from one form

  5. 05

    Notifications by email and chat, so nobody has to check the portal to know something changed

What changes

  • Clients check the status themselves instead of writing to ask
  • Documents live with the project, in one current version
  • The team sees who is working on what, and what is waiting for the client
  • A new client or colleague is set up the same way every time

Show us one process. We will show you what it could look like.

The analysis is free, takes about an hour of your time, and ends with a written summary you keep.

Prefer to read first? See examples