OpsPal Client Portal & E-Signature

The problem

Clients asked the same questions every week. What did you work on? How many hours are left? What do I owe? Where is the agreement? The answers were spread across the CRM, invoices, and email threads. Sending status updates by hand took time and still left clients guessing.

What I built

A client portal on its own subdomain, invite-only, where each client sees their own projects:

• A work log that shows every session and which bucket it counts against: in scope, retainer, a courtesy allowance, a purchased hour block, or a change order.
• Balances. Hour blocks and the courtesy allowance update as work is logged, and the database refuses to overdraw them.
• Requests. Clients submit requests in the portal instead of in scattered emails.
• Quotes, agreements, and payments. Proposals, e-signature, and payment links in one place. Card payments and wires settle through the same ledger.
• A timeline and a daily digest, so nothing important happens silently.

How it works

A client’s sign-in proves who they are and nothing more. Every read and write goes through a server-side function that looks up the client’s company first and returns only that company’s records, so a client can never query the database directly. A global switch and a per-project flag control what is visible, and new clients get access only by invitation.

Billing checks, digests, and documentation sync run as scheduled jobs inside the database.

Stack

Astro on Cloudflare Pages, Supabase (Postgres, row-level security, server-side functions, scheduled jobs), Stripe.

Where it stands

Live for OpsPal clients since September 2026.