Three Portals, One System: Solving the Multi-Stakeholder Intake Problem

A multi-service professional firm had an intake process held together by email threads, PDF attachments, and a shared spreadsheet that three people claimed was 'the current version.' New client inquiries arrived through a web form, got forwarded to the right department (sometimes), and sat in someone’s inbox until they had time to review.

Average time from first contact to case evaluation: four to seven business days. Not because the evaluation was complex — because the handoffs were. Information passed through too many people, in too many formats, with no shared system of record. Forms got lost. Follow-up questions went to the wrong specialist. Clients called to ask why nobody had contacted them.

The firm had evaluated off-the-shelf intake software. Every option either forced clients into a rigid form experience that killed completion rates, or gave internal teams a generic dashboard that didn’t match their workflow. None of them handled the fundamental tension: three very different users who all need to work with the same underlying data.

We built three purpose-specific interfaces on top of a single shared backend. Each portal is optimized for its audience — not a compromise that tries to serve everyone with the same screen.

The client portal is designed for completion. Guided question flows, progress saving across sessions, voice input for accessibility, and contextual help at every step. The goal is zero abandoned intakes. A form that’s technically complete but abandoned partway by a large share of applicants is a failure — and intake this complex is exactly where off-the-shelf form tools fail that way.

The specialist portal is designed for throughput. Case documents arrive pre-organized. Consent capture is digital with automatic audit logging. Consultation scheduling includes availability management. Specialists move through cases in a linear flow without switching between email, calendar, and document management.

The admin portal is designed for control. Intake rules, scoring criteria, and field mappings are configurable without developer involvement. When a new service line opens, an administrator builds its intake flow in the admin portal. No code deployment. No waiting for the next sprint. (How business rules moved out of code entirely: the Blueprint pattern.)

Intake time dropped from days to minutes — a 98% reduction. Every submission lands in a shared system where specialists can begin evaluation immediately. No email forwarding, no lost attachments, no version confusion.

Zero lost forms since launch. Previously, the firm estimated that 5-10% of inquiries fell through the cracks — prospects who submitted information but never heard back because the handoff failed. With a single system of record, nothing gets lost and nothing waits in someone’s inbox unnoticed.

The less visible win was operational agility. When the firm added a new service line, the administrator configured the intake flow, scoring rules, and mappings in an afternoon. Under the old process, that would have been a multi-week project involving IT, the vendor, and a web developer. The system adapts at the speed of the business — not the speed of the development queue. Focused application builds like this are what the larger fixed-scope bands buy.