Guide · updated

    Build a client portal with vibe coding.

    A client portal is a private space where each client signs in and sees only what belongs to them: files, project status, invoices, messages. It is one of the best first projects for vibe coding.

    01

    What a client portal needs

    • Sign-in for each client, and a separate one for your team.
    • A rule that each client sees only their own records. This is the part that matters most.
    • Files: upload, download, and who can see which one.
    • Status: where each project or request stands, without an email.
    • Messages or comments attached to the work, so nothing is lost in inboxes.
    • Optionally invoices and payment.

    02

    Which tool for which part

    PartWhat to use
    Screens and logicA prompt-to-app builder such as Lovable or Replit
    Data, sign-in and file storageSupabase, or the data and auth built into the builder
    PaymentsStripe
    Email noticesA sending service such as Resend

    03

    The access rule to get right

    The most common fault in a vibe-coded portal is that the screens hide other clients' data but the data itself is open. Anyone who knows where to look can read all of it.

    The rule must live where the data lives: in the database (row-level security in Supabase) or on the server, never only in the screen. Before a real client logs in, sign in as one test client and try to open another client's record by changing the address. If it opens, the portal is not ready.

    04

    Three ways to get one

    • Start from a template: pick an app close to your use on the templates shelf and adapt it.
    • Build it yourself: describe the portal to a builder, one screen at a time, starting with sign-in and the access rule.
    • Have it built: an expert builds or reviews it, which is worth it as soon as client files are involved.

    Questions

    How long does a first version take?

    A simple portal with sign-in, a client list, files and status can be working in days. Getting the access rules, emails and edge cases right is what takes the rest of the time.

    Is it safe to keep client documents in it?

    It can be, if access rules are set in the database, files are in private storage and someone has tested it as an outsider. Have it reviewed before real documents go in.

    Can it connect to my CRM?

    Usually yes, through the CRM's API or an automation tool. It is a common request to hand to an expert.