Customer and project portals

Customer portals for documents and approvals

A customer needs to supply missing information, review a draft or see the status of an order. A customer portal brings these tasks together in an accessible area. Through Kotodama, I develop portals suited to the way your business works with customers.

This could be an agency project portal or a service area for a specialist provider. We start with one complete case: which person needs to find which information and what decision follows?

Discuss your portal workflow
One document · clear responsibilitiesWho sees what?
Your team
DRAFTProject
documents
Internal note
Prepare and revise
Your clients
VERSION 02For
approval
Review and decide
Approval requestedThe approved version remains traceable.
Example role-based views. Access and approval rules are defined for each project.

From project start to an approved version

One possible process begins with an invitation. The customer adds the required information and provides documents. Your team reviews them, asks questions and later submits a version for approval. The status shows who needs to act next.

A draft and an approved version must be distinguishable. We clarify whether approval can be withdrawn, what happens after a change and which information notifications contain. A portal is only useful if these decisions remain understandable.

Every user needs the right access

Customer organisations must only see their own content. Within a team, project managers and staff may have different responsibilities. We record roles and permitted actions before development.

Invitations, lost access and departed employees are part of the process too. For files, we specify allowed formats, sizes and access rules. Special requirements for confidential data and retention need to be raised early.

When an existing customer area is enough

An existing project tool or shared document area may already support your workflow. We check that option before agreeing to custom development. Your own rules, different approvals or necessary system connections may justify a custom project.

A portal can be part of a web app. A configurator may be included for selecting and calculating an offer. CRM, accounting and document interfaces are assessed using the access actually available.

The scope and price of a portal project

Roles, the number of project types, document processing and approval rules determine the work involved. Data migration and connections to other programs add to it. A customer login alone therefore does not define a meaningful fixed price.

You bring an example project, document types and responsibilities. The quote lists agreed functions, acceptance cases and handover. Hosting, backups and ongoing support are specified before launch. We also test unauthorised access attempts using different accounts.

Questions about working together in a portal

Do our customers need to install new software?

A browser-based portal can be opened through a link. We agree on login and supported devices; short introductory materials can be produced if needed.

Can the portal use our branding?

Colours, logo and interface are developed for the project. Access under your own domain is clarified during technical setup.

Can we export data later?

Required exports and file access belong in the agreed scope. We clarify which information is included and the format in which it remains usable.

Rafael HagerYour contact
Rafael Hager

The first step

Which approval or document goes back and forth today?

Which documents, questions or approvals currently go back and forth between you and your customers?

All software services ↗