Echo / Build with AI
Build a client portal with AI.
Plan project updates, private files and deliverable approvals in one client workspace. Use this example brief and launch checklist to scope your first build in Echo.
Start with the client’s next action
A client portal is a private workspace where a customer can find project updates, review deliverables and provide feedback. A useful first version answers three questions: what is happening, what needs my approval, and where are my files?
For a design studio, start with a project list, a milestone timeline and a deliverable review page. Keep invoicing, live chat and complex scheduling out of the first version unless they are essential to the client workflow. Echo can help plan and build the web application; you still need to connect services and review it before inviting clients.
Define access before designing the dashboard
Use separate roles for studio administrators, team members and clients. A client should only read projects assigned to their organisation. A hidden navigation item is not an access-control rule: check permissions on the server whenever records or files are requested.
Model organisations, users, memberships, projects, milestones, deliverables and feedback. A deliverable belongs to a project and has a version. Record the reviewer and review time so approval refers to an identifiable version, rather than an attachment that can change underneath it.
Example brief: a design studio client portal
Build a responsive client portal for a small design studio. Administrators create client organisations and projects, assign members, set milestones and upload versioned deliverables. Clients see only their organisation’s projects, review a deliverable, leave feedback and approve or request changes. Use sample records clearly marked as demo data.
Include a project dashboard, milestone timeline, deliverable detail page and team settings. Each screen needs loading, empty, error and no-permission states. Do not mark a file uploaded or an approval saved until the server confirms it. Keep billing and chat out of scope. Ask me about the identity provider and file storage before connecting them.
Review the plan and connect real services
Paste the brief into Echo and review the Plan before building. Resolve invitation behaviour, membership removal and who may approve a deliverable. Agree on whether one approval is enough or whether a project needs multiple reviewers.
Build the first workflow, inspect the preview and connect your chosen database, identity and file storage services as required. Use private file storage and expiring authorised download links where appropriate. Sample data can demonstrate the layout; it does not prove that account isolation or file access is implemented.
Acceptance checks before inviting a customer
Test with an administrator and two clients from different organisations. Try opening the other client’s project URL directly, requesting its files and submitting feedback to its deliverables. Each attempt should be rejected by the server, not merely hidden in the interface.
Check duplicate submissions, failed uploads, expired invitations, deleted memberships and old deliverable versions. Confirm that approval persists after a reload and that notifications reflect saved changes. Review authentication, backups, data retention and accessibility before launch. Browser build checks are useful, but they are not a security audit.
Keep a path beyond the first version
After the review-and-approval workflow works, add features based on actual client requests: notifications, invoice links, search or additional review roles. Add one complete workflow at a time so you can verify its permissions and failure states.
Echo provides source export and GitHub sync so your team can inspect the project and continue development. Keep the deployment configuration and service accounts documented alongside the code.