Custom client portals.
One place to move work forward.

When a custom portal makes sense

A client portal is a private workspace where customers see information and take actions related to their own account or project. A custom build is useful when the permissions, workflow, or integrations do not fit an existing product.

• Clients ask for updates that your team already tracks elsewhere.
• Files and approvals are scattered across email threads.
• Your team copies the same information between systems.
• Different customers need access to different projects and documents.

If an existing portal meets your needs, we will recommend configuring it. A custom build should solve a specific gap.

From approved quote to completed project

Illustrative workflow—not a measured customer result.

1. An approved quote creates a project and assigns an owner.
2. The client receives an invitation to their project workspace.
3. Missing documents and approvals appear as explicit tasks.
4. A verified stage change updates the client view and triggers an approved notification.
5. Exceptions reach a staff member with the project context.

We confirm which events your tools expose before promising an integration. Payments, signatures, and scheduling are separate scope decisions.

Related work: The Cube Signs

Aplos built intake, a project board, and customer-update workflows for The Cube Signs. It demonstrates connecting the public inquiry process to internal project work; it is not proof of every portal feature described here.

Read the Cube Signs build · Explore other systems

What we agree before building

• Access: who can see and change each record.
• Connections: where data comes from and which system owns it.
• Acceptance: the client and staff journeys that must work.
• Ownership: code, accounts, exports, hosting, and handoff.
• Ongoing operation: support, maintenance, usage costs, and changes.

How much does a client portal cost?

Portals are custom projects priced after scope. Aplos's general custom ranges are $2,500–$7,500 for focused integrations, $8,000–$20,000 for multi-step workflows, and $20,000+ for operating systems. Those ranges are not a fixed portal quote. Roles, integrations, data migration, and workflow complexity determine the proposal.

See custom-system pricing and scope

Can you connect our existing tools?

We first check API access, account permissions, data quality, and required events. A tool's name on a list does not guarantee compatibility. A workflow integration may be sufficient when you do not need a new interface.

What should we bring to the first conversation?

One example project, the tools involved, the information clients need, and the step that causes the most chasing. Use redacted examples until we agree a secure way to review your data.