Clients

The outward-facing side of the system: a branded portal where clients see status, approve, upload, and ask. Document requests with reminders, approvals with a paper trail, shared information, invoices. Whoever your customers are, this is where they meet your system.

  • Owns
  • Portal access
  • Requests
  • Shared documents
  • Approvals
  • Shared status

A few of the views inside Clients.

Inside the app

What lives in Clients.

One app owns the whole domain. These are the workflows, views, and features inside it, rather than a separate tool for each.

  • Branded portal per client or customer
  • Document requests with reminders and checklists
  • Approvals on quotes, changes, deliverables, and invoices
  • Order, job, and project status without a phone call
  • Secure messaging on the record
  • Invoices and payments visible and payable
AI inside the app

What your agent does in Clients.

  • Answers status questions from the record before a human is asked
  • Requests missing documents and chases them until the checklist is complete
  • Posts what needs approval and nudges the right person
  • Drafts the client update from what happened this week, for approval

Every person gets their own agent; teams can share one. Sensitive actions wait for approval, and every action is logged with the data it used and the outcome.

Built with AI

Need it different? Describe it.

Add a field, a stage, a rule, a view, or a workflow inside this app. It's built on the same records and permissions, as open code you can change again.

Add a "clients" view for my team: only what's mine, due this week, with the agent's drafts on top.

See Clients on your data.

Book a demo and bring a real example. We'll show you the app on your data, with the agent doing the work.