Delivery proof, not developer surveillance.
Scopeworth handles delivery metadata such as tickets, pull requests, calendar events, and AI work signals. We are deliberate about what we collect and what stays outside the product.
Every report carries a confidence score.
If the data is messy, Scopeworth says so and shows what to fix.
Scopeworth tells you when the data is messy
Read only access to the tools you already use.
Connected tools
Six commitments we hold the product to.
Collect only what is needed
Scopeworth reads just enough delivery signal to produce a useful report.
Make assumptions visible
Where data is incomplete, the report shows confidence and inferred values. No quiet guesses dressed as facts.
Prefer metadata over source content
Where a question can be answered with metadata (titles, statuses, timing), we avoid reading source code content.
Use least privilege integrations
OAuth scopes are kept narrow. Read only by default, write access only when required.
Keep client and project data separated
Reporting boundaries follow the way agencies actually bill: by client, project, and engagement.
Avoid individual surveillance metrics
Scopeworth produces project, client, and team reporting. It does not produce individual rankings or scoring.
What Scopeworth does NOT collect by default.
Scopeworth focuses on client, project, and team delivery proof. It is not designed to rank engineers or create review leaderboards.
No keystrokes or screen recordings
Scopeworth never records keystrokes, screens, webcams, or microphones. These are not delivery signals.
No individual productivity rankings
Reports are project, client, and team level. There are no individual scorecards, leaderboards, or review outputs.
No private message content by default
Where messaging tools are connected, Scopeworth uses coordination metadata, not message bodies, unless a customer opts in.
No source code content by default
PR metadata, review timing, and merge activity feed reports. File contents stay outside by default.
No time on task surveillance
No background timers, mouse movement tracking, or active hours measurement. Cost is modeled from delivery signal, not user activity.
No HRIS or payroll integration
Scopeworth uses role based cost bands by default. Exact salaries are never required, and HRIS systems are never connected.
Read what's needed for the report.
Reports are built from delivery metadata: tickets, pull requests, releases, calendar events, and AI tool signals. Where a question can be answered with metadata, we don't pull file contents.
Narrow scopes, read only by default.
Integration scopes are kept as narrow as the provider allows. Read only is the default. Any write access is opt in.
Treat client and project data with care.
Delivery data carries client confidentiality. We separate data along the boundaries that agencies actually bill on, and we don't combine it across customers.
Reports visible to the right people.
As the product matures, role based access will let agencies expose specific reports without sharing everything.
Enterprise controls, in the order we ship them.
These are planned, not yet generally available. We sequence them by what design partners actually ask for first.
- On design-partner requestSSO / SAML and role-based access to specific reports.
- NextAudit logs for sensitive actions and configurable data retention.
- As we scaleData residency options and tighter per-integration permission scopes.
- After formal auditSOC 2 readiness — published here once complete.
We don’t claim certifications we don’t hold. As we go through formal audits, we’ll publish the results here.
Found something? Let us know.
If you believe you’ve found a security issue with the website or product, please reach out via the contact page with details and reproduction steps. We’ll respond within one business day and work with you on resolution.
Have specific security requirements?
Tell us about your environment and we'll walk through what we have today and what we're shipping next.