00Services
Customer and partner portals end the status-chasing phone call.
A customer portal is the outside-facing surface of your operational system: structured requests in, documents and live status out, with each account seeing only what it is permitted to see. Built properly it is a permissioned view onto the system already doing the work, not a separate product.
01Definition
A portal is a view onto the system, not a second copy.
If the portal holds its own copy of the truth, it will be wrong within a month.
Where the data lives decides whether a portal works. A portal that maintains its own status field, updated by hand, becomes another thing to keep in sync — and quietly stops being trusted. A portal built as a permissioned view shows the same record the internal team is working from, at the moment they are working on it. That is an architecture decision, and it is why portals belong on top of custom operational software rather than beside it.
02What it replaces
Time goes to questions the system should be answering.
Each of these is a person doing work a system should do. Together they are the business case for the build.
- 01“Where is my job?” phone calls, answered by someone opening a spreadsheet and reading a row out loud.
- 02Documents sent as email attachments, with no version of record and no way to tell which copy is current.
- 03Requests that arrive as free text and need two follow-up emails before the work can even be scheduled.
- 04Partners and subcontractors who cannot see their own history, so they ask you to reconstruct it.
- 05Status that is accurate only as long as someone remembers to update the shared sheet.
03What Aptixx builds
Four parts make a portal, and they only work together.
Requests, documents, status, and access are one system. Ship three of them and customers keep phoning about the fourth.
Structured requests
Intake that asks for what the work needs, validates it at submission, and lands as a record in the queue rather than an email someone has to transcribe.
→ Work starts complete instead of half-specified
Secure documents
Certificates, reports, drawings, and signed records held against the job they belong to, with a version of record and access tied to identity.
→ One copy of the truth, and a trail of who read it
Status visibility
The stage each job is at, drawn from the same operational system that moves it — so the portal cannot drift out of date the way a status spreadsheet does.
→ Customers stop calling to ask
Role-aware access
Customers, partners, and internal staff see different things because they are permitted different things. Access is enforced at the data layer, not by hiding links.
→ One portal, several audiences, no leakage
Aptixx applies role-aware access everywhere, not just in portals: in the marine survey platform, public signup is disabled and the first administrator is bootstrapped by an operator, so every account traces back to a person who authorized it.
04Bilingual and multi-entity
Two languages and several entities still share one record.
Some portals serve people who do not all read the same language, inside organizations that operate as several legal entities under one roof.
Aptixx scopes bilingual, multi-entity case-management systems for regulated service businesses. The design questions come first, and they are structural. One record of the case with two language surfaces, not a translation layer bolted on. Entity boundaries that decide which staff and which documents belong to which file. A single history that reads correctly in either language when it is reviewed. Deciding that in discovery costs a conversation. Deciding it after launch costs a migration.
05How to start
Scope the operational system first, then the door into it.
A portal is the second phase of most builds. It comes first only when the system behind it already holds a record worth showing.
A paid discovery sprint is where that gets decided: what your customers need to see, which internal record supplies it, what has to change before it can, and what the build is worth. See the Aptixx case studies for how the same approach played out in marine surveying and regulated cultivation.
The fit call takes 20 minutes and costs nothing. The sprint fee is fixed before it starts, credits toward the build, and every artifact it produces is yours.
Next step
Bring the questions your customers keep phoning to ask.
Twenty minutes on what they need to see, where that record lives today, and what a portal would take. No obligation on either side.