A workflow catalog, a connections layer, and structured memory — all reachable inside claude.ai by typing /verslay_run.
Each one is shipped today and reachable inside claude.ai by typing /verslay_run.
135 ready-to-run workflows. Quality-graded. Shared.
Click a card. claude.ai opens with /verslay_run <slug> pre-loaded. The MCP server runs the workflow and streams the output back.
Every workflow is a prompt you wrote, stored in a Doc somewhere, with no version history.
12 agents compose into 8 multi-step workflows.
Trigger Morning Briefing once: inbox-scanner → calendar-scanner → crm-scanner → triage-router → report-formatter → distributor.
You chain prompts manually — paste outputs into the next prompt, switch tabs, paste back.
26 services. One OAuth proxy. Multi-shop Shopify.
Connect Shopify once, add 3 stores under sub-keys, switch via dropdown inside any use-case.
Connectors are per-user, single-account-per-service. Three Shopify stores = three reauths.
5 named domains. Read by every run automatically.
Set brand voice once in Memory → Brand. Every text-drafting use-case reads from it.
Memory is unstructured. You re-paste context into every prompt that needs it.
Every workflow is graded before it ships.
coming_soon → beta → live. Promotion needs ≥ 3 successful audits, judge ≥ 85, zero regressions.
Your prompt is whatever you wrote. No grade. No history. No signal it works.
Clearly labelled — no "soon™" ambiguity.
Your Monday briefing runs without you remembering to open Claude.
Use Claude's Automation feature to fire /verslay_run <slug> on a schedule. Verslay-side cron, audit trail, retry, alerts shipping next.
Compliance + audit + the "show me what AI ran on Acme this quarter" moment.
Run history lives in your Claude chat threads only. Structured receipts (input · output · who · sources · status) shipping next.
A new hire's first run already knows your brand voice, top accounts, past drafts.
Memory domains are per-user today. Owners will publish memory state to all teammates next.
Owner / operator / viewer roles. Shared connections, catalog, run history.
Verslay is single-tenant per account today. Multi-seat workspaces with roles shipping next.
Every row uses only verified Live-Today capability.
Paste 8 URLs → prompt → copy → Notion → format → share
/verslay_run competitive-deep-dive → topic → posts to Notion
Per lead: paste context → prompt → copy → Gmail → send (×50)
/verslay_run lead-research → CRM context + brand voice → 50 Gmail drafts
Pull Stripe manually → paste → prompt → copy → Notion → format
/verslay_run weekly-digest → pulls Stripe + HubSpot → drafts to Notion
Reconnect Shopify per store, swap context manually each time
One connection · 3 sub-keys · pick store from dropdown
Re-paste a brand-voice paragraph into every prompt
Set Memory → Brand once. Every run reads it.
Train them on prompt-writing → review every output
Send catalog URL → "Try Use-Case" → /verslay_run pre-loaded
Five Live-Today layers and four shipping next, all reachable by typing /verslay_run inside claude.ai.
Click a card. claude.ai opens with /verslay_run pre-loaded and runs.
Run this yourselfSix agents fire in sequence. One trigger. One output.
Run this yourselfOne connection. Three stores. Switch via dropdown. No reauth.
Run this yourselfClaude is the assistant. Verslay is the operating layer that points it at your business.
One slash command, 135 ready workflows, 26 connected services, structured memory.
/verslay_run. Pick a workflow.That's the whole experience. Browse the catalog, connect once, and run packaged business operations from inside Claude.