Case study
Secure Intake Portal
An engineering and product look at how the Secure Intake Portal was designed and built — and the security choices behind it.
Overview
A focused intake tool for small professional-service firms.
Secure Intake replaces scattered emails and basic contact forms with one secure workflow: clients submit details and documents, and staff manage everything from a single admin dashboard.
Problem
Intake was leaking detail.
Small firms relied on basic contact forms and email threads to start client work. Documents arrived late or not at all, context got lost between staff, and there was no single place to see where each new client stood. The handoff from first contact to active work was messy and easy to drop.
Solution
One secure workflow.
A public intake form feeds structured submissions into an admin dashboard. Clients can upload supporting documents directly or via an upload-later link. Staff track status and priority, leave internal notes, and manage attachments — all backed by authenticated access and a clear record of key actions.
Tech stack
Built on a pragmatic stack.
Frontend
React, Vite
Backend
Java, Spring Boot
Database
Postgres, Flyway
Auth
JWT, BCrypt
Storage
Private AWS S3
Hosting
Vercel, Render, Neon
Security choices
Decisions made with sensitive data in mind.
Screenshots
A look at the interface.
Real product screenshots will be added here. The cards below are placeholders, not final screenshots.
Roadmap & lessons learned
What's next, and what we'd carry forward.
- Tighter notification and reminder flows for upload-later links.
- Configurable intake fields per firm without a redeploy.
- Richer reporting on intake volume and turnaround time.
- Lesson: scoping the workflow tightly up front kept the build focused and shippable.
Curious how this would map to your workflow?
We’ll walk through what you have today and where a small, focused tool could help.