01 / Services
Sites and working workspaces
A company storefront, a client account, or an internal portal for a process that already exists.
When a site exists, but it cannot take a request, hand over a document, or let a staff member into the right section.
Site
Workspace
Storefront
Client
Staff member
Role
Header
Menu
Sign-in
Role
Request
Queue
What it consists of
What goes into the system
- 01
Public storefront
Pages a person opens without signing in: who you are, what you do, and where to write.
- The main screen and the sections
- A form into the right queue
- Reading from a phone, without a separate version
- 02
Client workspace
After sign-in, a person sees only their own: requests, files, statuses, and invoices.
- Sign-in, and recovery of access
- A list of one’s own requests or orders
- A file is downloaded from the record, not from an email
- 03
Staff workspace
Internal sections are cut by role. One shared password for everyone is not left in place.
- Who sees every request, and who sees only their own
- A status change, and the queue
- The comment stays on the record
- 04
Request and data
The inquiry, the user, and the file sit in one place. Email stops being the archive.
- A record with the fields people actually fill in
- Permissions on the sections
- An export, if the records system needs a file
- 05
Launch
Before deploy we walk the live paths: a request, sign-in, a status change, an error in the form.
- A check of the main scenarios
- Basic visibility in search
- Who to write to if something needs a change after handover
What we do
- 01A review of the scenarios, before any layout
- 02An interface built for the roles, not for “a pretty screen”
- 03The client side, and the server logic
- 04Basic visibility in search
- 05Check and deploy
How we proceed
- 01Scenarios
- 02Layout
- 03Build
- 04Check
- 05Launch
Stack
- Next.js
- TypeScript
- Node.js
- PostgreSQL
A guide for the timing
A short landing page takes about a month. A workspace with roles takes from a month and a half.
Outcome
A site or a workspace that opens on a phone and does not need a separate instruction for every tap.
What usually comes later
Language versions, a partner workspace, and complex permissions “like in a large system” come second, once the first system is already taking requests.