Files
openwork/packages/docs/non-technical.mdx
ben 61df5400d8 docs: split docs entrypoints by audience (#872)
* docs: split docs entrypoints by audience

* docs: add audience split screenshot evidence
2026-03-12 15:10:06 -07:00

72 lines
2.3 KiB
Plaintext

---
title: "Non-technical"
description: "See tasks OpenWork can take on"
---
Use this path if you want to understand what OpenWork can do before you think about CLI commands or runtime details.
---
## Start with outcomes
OpenWork works best when one worker owns one repeatable outcome. The goal is to make recurring work easier to run, review, and share.
<CardGroup cols={2}>
<Card title="Daily ops summary" icon="flag">
Watch incoming work, flag issues, and deliver a morning brief.
</Card>
<Card title="Weekly team brief" icon="calendar">
Roll up wins, blockers, and follow-ups into one update.
</Card>
<Card title="Competitor scan" icon="search">
Track launches, pricing changes, and market movement on a schedule.
</Card>
<Card title="PR review and triage" icon="git-pull-request">
Check new pull requests, sort issues, and draft first responses.
</Card>
<Card title="Social drafts" icon="message-square">
Turn changelogs or notes into ready-to-review posts.
</Card>
<Card title="Follow-up emails" icon="mail">
Draft polished follow-ups from CRM notes, meeting notes, or action items.
</Card>
</CardGroup>
---
## Start in the app
The easiest first run is the desktop app.
- Install OpenWork.
- Create one worker for one outcome.
- Run one visible task before you add more automation.
<CardGroup cols={2}>
<Card title="Use the desktop quickstart" icon="zap" href="/quickstart">
Get from install to first worker in minutes.
</Card>
<Card title="Keep workers separate" icon="shield" href="/tutorials/worker-isolation">
Use one worker per team, client, or domain so work stays predictable.
</Card>
</CardGroup>
---
## Share with teammates
One person can set up the worker, then everyone else can join the same flow.
- Fastest: send `OpenWork invite link`.
- Manual: share `OpenWork worker URL` + `Access token`.
- Best practice: keep one worker per team or domain instead of mixing everything together.
<CardGroup cols={2}>
<Card title="See the share flow" icon="share-2" href="/tutorials/share-worker-invite-link">
Remove copy and paste friction for new teammates.
</Card>
<Card title="Add repeatable jobs" icon="repeat" href="/tutorials/automations-repeatable-jobs">
Turn good one-off prompts into repeatable workflows.
</Card>
</CardGroup>