Browser-only workflow examples
A planning library of workflow patterns to study and adapt.
20 example patterns for agency teams. These are planning references, not deployed automations, service promises, or proof that a connection is active.
Weekly performance intelligence
LowIntended value: reduce the recurring weekly reporting pass
Read-onlyExample pattern- Planning note
- Planning note: a possible starting point for a founder-led activation
- Example connection targets
- Google Ads · Meta · GA4
Cross-client anomaly detection
MediumIntended value: surface drift before a client notices it
Read-onlyExample pattern- Planning note
- Planning dependency: review weekly performance intelligence first
- Example connection targets
- Google Ads · Meta
Optimisation proposal preparation
MediumIntended value: turn observations into a reviewable action queue
InternalExample pattern- Planning note
- Planning dependency: four weeks of accepted briefs
- Example connection targets
- Google Ads · GA4
Budget pacing review
MediumIntended value: prepare daily pacing exceptions for review
Spend-adjacentExample pattern- Planning note
- Planning dependency: define a proposed spend approval boundary
- Example connection targets
- Google Ads · Meta
Attribution discrepancy review
HighIntended value: explain channel disagreement before the client asks
Read-onlyExample pattern- Planning note
- Planning dependency: complete a tracking integrity review
- Example connection targets
- GA4 · Google Ads · Meta
Executive account summaries
LowIntended value: one readable page per account for the founder
Client-visibleExample pattern- Planning note
- Planning dependency: define a proposed external-send approval boundary
- Example connection targets
- GA4 · Slack
Deliverable quality assurance
MediumIntended value: route client work through a documented review
Client-visibleExample pattern- Planning note
- Planning note: a possible starting point for a Client Delivery lane
- Example connection targets
- Drive · Notion
Evidence-backed client reporting
MediumIntended value: trace report claims to their sources
Client-visibleExample pattern- Planning note
- Planning dependency: define the deliverable review first
- Example connection targets
- Drive · GA4
Brand compliance review
LowIntended value: catch brand drift before client delivery
Client-visibleExample pattern- Planning note
- Planning dependency: gather the client brand rules
- Example connection targets
- Notion
Client onboarding coordination
MediumIntended value: reduce kickoff dependence on one person remembering
InternalExample pattern- Planning note
- Planning dependency: gather the onboarding SOP
- Example connection targets
- Linear · Slack · Drive
Scope and requirement validation
HighIntended value: flag scope changes for human review
InternalExample pattern- Planning note
- Planning dependency: identify the signed scope source
- Example connection targets
- Notion · Linear
Revision and approval management
LowIntended value: organize feedback outside message threads
InternalExample pattern- Planning note
- Planning dependency: define the proposed approval route
- Example connection targets
- Linear · Slack
Account research
LowIntended value: reduce founder research work
Read-onlyExample pattern- Planning note
- Planning note: a possible starting point for a Pipeline lane
- Example connection targets
- HubSpot
Contact validation
LowIntended value: keep guessed addresses out of the CRM
Read-onlyExample pattern- Planning note
- Planning dependency: define an account-research review
- Example connection targets
- HubSpot · Close
Personalised outreach preparation
MediumIntended value: hold drafts for human approval before sending
Client-visibleExample pattern- Planning note
- Planning dependency: define a proposed external-send approval boundary
- Example connection targets
- HubSpot · Notion
Meeting preparation
LowIntended value: prepare meeting context for review
InternalExample pattern- Planning note
- Planning dependency: identify a calendar connection target
- Example connection targets
- HubSpot · Slack
Content brief production
LowIntended value: reduce delays in preparing content briefs
InternalExample pattern- Planning note
- Planning dependency: gather the brand guidance
- Example connection targets
- Notion · Search Console
Source and claim verification
MediumIntended value: hold unsupported claims for human review
Client-visibleExample pattern- Planning note
- Planning dependency: define a proposed unsupported-claim rule
- Example connection targets
- Notion
Workflow exception triage
MediumIntended value: route exceptions for human review
InternalExample pattern- Planning note
- Planning dependency: name a proposed escalation path
- Example connection targets
- Slack · Linear
Tool and integration monitoring
LowIntended value: surface connection failures before downstream work
Read-onlyExample pattern- Planning note
- Planning dependency: name two or more connection targets
- Example connection targets
- Slack
Product direction - earned authority
Illustrative authority stages, not active grants.
These 20 patterns are browser-only examples. The authority stages below are product direction, not current capability. This page does not connect, configure, deploy, certify, or grant authority to anything.
- ObserveProduct direction: a team would read and propose without changing systems.Illustrative starting state, not a live grant
- DraftProduct direction: work would be produced and held for review.Illustrative requirement: runtime and review lane operating
- Execute in sandboxProduct direction: actions would run against non-production systems only.Illustrative requirement: independently reviewed rehearsal evidence
- Execute with approvalProduct direction: production actions would require enforced approval boundaries.Illustrative requirement: independent review passing consistently
- Future: execute unattendedProduct direction: routine actions would complete without a human, with exceptions escalating. Not available today.Illustrative requirement: a sustained record without boundary breaches or missed escalations
- Own the laneProduct direction: the desk would hold authority over its lane end to end. Not available today.Illustrative requirement: independently verified consequence coverage