# Show it once. Stepwork does it the same way every time.

> Stepwork works in the websites and systems your team already uses. It logs in, clicks, types, and copies like a person would. No integrations, no code, no vendor sign-off.

Source: https://stepwork.com

## Trusted by

- Talkdesk
- Calm
- AngelList

## How it works

- **Show your task once:** Do the task yourself, once. Stepwork records every click, field, and page.
- **Create a variable:** Does part of it change each time, like a name or an account? Make that a variable. Give it a list and it does every row.
- **Run it forever:** Run it on demand, on a schedule, or from Slack. It works in the background, 4–5× faster than by hand, and keeps a record of every step.

**A few examples from the catalog:** Onboarding, Offboarding, Access reviews, Compliance checks, Vendor reviews, Evidence collection, License checks, Insurance checks

## If your team does it on a screen, Stepwork does it too.

Stepwork uses the same logins and screens your people use. That covers old in-house systems, supplier and government portals, and apps with no integration at all.

Works with 30,000+ apps

_Visual: Vendor logos: Google Workspace, Okta, Microsoft 365, AWS, LinkedIn, Zendesk, HubSpot, Salesforce, GitHub, Workday, Vanta, Slack, Notion, Serval, Jira, Linear, Snowflake, 1Password, Airtable, Figma, ServiceNow_

## Evidence, not assurances

See exactly what Stepwork did on screen: what ran, who started it, every click it made, and how it ended.

Captured in every run:
- A screenshot of every step it took
- Every step logged with the time it happened
- The exact reason when something fails
- Audit-ready records, mapped to the SOC 2 controls you agree on

_Visual: A completed run record_

## AngelList automated the work APIs couldn’t reach

Repeatable IT and back-office work now runs on its own: shown once, then executed in the same apps the team already uses.

- **30–40 hrs** saved every week
- **24/7** running in their infrastructure

## Important work shouldn’t be improvised

Many AI tools pick their own steps each time they run. When the work is granting access, paying an invoice, or filing a record, every step has to happen in order and leave a record. Stepwork follows the steps you recorded. That is what deterministic means.

- **A different path each time:** The AI picks its steps as it goes, so the same task can end differently from one run to the next.
- **Your recorded steps, every time:** Stepwork follows the steps your team recorded. Same input, same steps, same result.

## Automate the whole process, not one step of it

Chain flows together, add decision rules, call your APIs, and require approvals where they matter. Stepwork runs the process end to end.

- **Weekly idle account digest (Easy):** Find Okta users inactive for 90+ days, turn the table into a visual digest, and post it to IT.
- **Reclaim idle paid seats (Medium):** Find idle paid seats, apply policy, downgrade each qualifying seat, and report the savings.
- **Offboarding with evidence pack (Complex):** Deprovision a leaver across systems, route admin accounts through security, collect evidence, and report exceptions.

## Built for work you cannot afford to get wrong

Isolated execution, credentials that stay in your vault, access scoped by role, and a record of every run.

**Compliance:** GDPR, SOC II, NIST (Coming soon), ISO 27001 (Coming soon)

- **Runs in an isolated container:** Flows execute in an isolated browser container, either on a machine in your environment or in a Stepwork cloud container. Nothing runs directly against a user's everyday browser session.
- **Your passwords stay in your vault:** Stepwork reads credentials from 1Password when a flow runs. It stores a reference to the vault item, never the password itself.
- **Scoped by role, isolated by organization:** Administrators, managers, and members see and do different things. Data is scoped to your organization, and single sign-on connects Stepwork to the identity provider you already run.
- **A record you can hand to a reviewer:** Each run keeps its steps, outcome, and any failure reason, along with who triggered it and whether it ran on a schedule.

## See it run on a process you already repeat

Bring one. We will show you what it looks like as a flow and what each run records.

---

This is the Markdown version of https://stepwork.com, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
