Customer portal
Your client watches the work itself.
They open the portal and see the statement of work, what has been approved, progress against the technical requirements they asked for, and the invoice for it. None of it is assembled for the occasion: it is read from the record the work already lands on, so it is as current as the work is. At the end of the engagement the work becomes theirs, with a signed record of what was delivered.
The features
Everything in Customer portal
- Customer portalClient portalDocuments, signing, progress, invoices and tickets, in one place.Read the page
- Customer portalApprovalsAnything that cannot be undone stops before it happens.Read the page
- Customer portalAudit trail and evidenceWho did what, on a sealed record, exported when someone asks.Read the page
The client sees the work itself
Meridian opens the portal and sees the statement of work, what has been approved, progress against the technical requirements they asked for, and the invoice for it. All of it drawn from the record the work already lands on, so nobody assembles it on a Thursday night.
- The statement of work and the requirements it is measured against, in one place
- They comment beside the line they mean and get an answer by name
- Invoice them from the same portal, with what is still owed beside it
- Pass your AI costs on at your own markup, or absorb them
- They see what you shared, and nothing else
One record, exported rather than assembled
Six months later somebody asks who did what. You do not reconstruct it. Every action landed on one record as it happened, sealed so a later edit would show, with the AI agent and the human it acted for on the same line.
- Both names on every action: the AI agent that ran it and the person it works for
- Sealed, so a later edit to the record shows
- Exported when somebody asks, not written up for the occasion
- Controls are attested on a cadence, with a written reason, and the attestation expires
Hand over the work, and its record
At the end of the engagement the project becomes Meridian’s: the software, the parts list, and the documents, with a signed record of what was delivered and hashed so a later edit would show. That is the difference between a deliverable and a deliverable somebody can answer for two years later.
- A signed delivery record they keep, hashed so a later edit to it would show
- Hours by kind, each approved by somebody other than the person who logged them
- Take all of it to another firm without asking us
Tell us about the engagement you are scoping.