Use cases · Agencies
audit the outcome · verify activation · prove it every Friday
Studios that build and maintain client sites. Riley audits the sites, turns problems into fix cards, and hands you a record of every fix a client can check.
What Riley is usually hired for in this setup. Statuses are honest: live means it works today, and coming soon means it does not exist yet.
Riley scans your site for broken pages, errors, and basics that cost you customers, and turns what it finds into an audit you can act on.
After a fix you approved goes out, Riley will re-check the page and record that the fix actually took, closing the loop instead of assuming.
When Riley detects a problem anywhere it watches, it creates a fix card with the evidence and a proposed fix. You approve, Riley executes, and the result is recorded.
Riley assembles everything it completed into a signed weekly receipt with a public verification link, so the people you answer to can check the work themselves.
Riley will turn the ledger into a client-ready update: what was done, what changed, and what is next, drawn from records instead of recollection.
Trigger: Runs on request or on a schedule against your site.
Approval: Scanning is read only; site changes wait for approval.
Trigger: Riley detects a problem on anything it watches.
Approval: Every fix card waits for your approval before anything changes.
Trigger: Runs every week on your schedule.
Approval: Built from already-approved work; sending it to a client is your call.
Trigger: Will run on your reporting schedule or on request.
Approval: Every update is a draft until you approve it for sending.
The connections this setup usually starts with. You grant access, and you can revoke any connection at any time.
The surfaces this setup usually works from. The same rules apply on every one of them.
Connect your tools, approve the first drafts, and get a signed receipt of the work every week.