Workeros — How else do we make it intuitive?

Net-new levers (beyond activation, the minimalism cuts, and avatars). For each: Yes / Maybe / No + a note.
1 · Plain language
De-jargon the labels for non-technical operatorsREC

"Tools" → Integrations, "MCP" → Developer access, "Source" → behind Advanced. (Brain stays Brain — your call.) The ICP shouldn't meet dev terms.

now
RunSourceToolsMCP
clearer
RunIntegrationsAdvanced ▾
2 · Outcome-first
Show what a run DID, not its status codeREC

Everywhere (overview, runs, cards): lead with the human outcome ("scored 14 leads") instead of "run_ab12 · completed". The product's promise is outcomes.

now
run_ab12c3completed
outcome-first
Lead Scorerscored 14 leadsdone
3 · Recovery guidance
When something fails, say exactly what to do nextREC

A failed run links its cause to the fix inline — "HubSpot expired → Reconnect" — instead of a raw error. No dead-ends.

Pipeline reportfailed
⚠HubSpot connection expiredReconnect
4 · Action feedback
Every action gives clear confirmationREC

Connect an app, create a worker, save a setting → a short toast so the user always knows it worked (and what happened). No silent successes.

✓ Gmail connected — workers can send email now
5 · First-time hints
Gentle inline "what's this?" on unfamiliar thingsMAYBE

A dismissible (?) next to jargon (Brain, triggers, approvals) → a one-line explanation. Not a wizard, not a tour — just answers where the user looks. Shows once.

Brain?
Folders of files your workers read before they act — like company memory.
6 · Findability
Make search/⌘K visible, not hiddenMAYBE

The command palette exists but is a hidden shortcut. A visible "Search or ask…" bar makes the fastest path discoverable for non-power users.

Search workers, runs, or ask Emily…⌘K