Remote Pro Ai

Inside Client OS

Fig. 01Inside Client OS

  • 9practices
  • 48hshortlist
  • 4working days to start
  • 72hfree hold
A walkthrough of the client portal
What you see from day 1, who can do what, and how delivery evidence reaches you.

What you see on day 1

Your squad, the Statement of Work and the first sprint; log in from the Client OS entry.

Screenshots

Six screens of Client OS, in the order a client meets them. Every screenshot is published only after founder approval; until then each slot carries a description of what the client sees on that screen and a “screenshot pending” placeholder. No figure below is a real client’s.

  • 01

    SLA board (Promises & security)

    One row per commitment in the Statement of Work: time to shortlist, start date, replacement window, seat availability, response times. Each row shows the commitment, the current state (on track · at risk · missed) and the evidence behind it, so the client checks the guarantee without asking.

  • 02

    Timesheets (Hours & requests)

    Hours per engineer per week against the contracted hours, with the approver’s name and the approval date. Unapproved weeks stay visibly open; approved weeks feed the invoice. The same screen holds the leave calendar and the overlap window with the client’s office.

  • 03

    Invoices (Money & contract)

    The contract, its seats and each monthly invoice side by side: invoice lines per seat, the approved hours they rest on, VAT per entity, status (draft · issued · paid) and the PDF. A seat change or extension request opens from here and shows its effect on the next invoice before it is sent.

  • 04

    Weekly health (Performance)

    A weekly summary per squad and per engineer: sprint commitments met, blockers raised, review feedback and the client approver’s own score, with the Account Director’s note for the week. Trends are shown over the rolling 90 days, never a single week in isolation.

  • 05

    Replacement log (Hours & requests → Replace)

    Every replacement request with its reason, the date raised, the shortlist proposed, the new engineer’s first day and the handover checklist. The log stays visible for the life of the contract, so the replacement commitment is auditable, not promised.

  • 06

    Governance (Settings · users, roles, audit)

    Who can see and approve what: owner, approver and viewer roles per user, SSO status, the data-handling notice from the DPA, and the audit trail of every approval, export and role change with its timestamp. The security page lists the controls that apply to the client’s own data.

Roles & permissions

Owner, approver and viewer roles; data handling follows the DPA.