Slack2SOP
App · Beta

Four months of Slack. One clear SOP.

You already explained the job — in Slack, in pieces, to one person, over four months. Then they left and took it with them.

The premise

Every small team's real documentation is a Slack channel. It is complete and accurate and unusable: scattered across threads, out of order, addressed to one person who has since moved on. Slack2SOP reads it and produces the document that should have existed.

#ops — 4,182 messages → 1 SOP
vishno, always check the tracking first
mariaand if it's over 30 days?
vishthen refund, don't ask me
mariaok and the supplier msg?
vishtemplate 3, change the name only
Late order — refunds
Steps
  1. Check tracking before replying.[1]
  2. Over 30 days in transit → refund without asking.[2]
  3. Message the supplier using template 3.[3]
Do not
Change anything in template 3 but the name.[3]
⚠ Conflicting guidance Mar 14 said 45 days, Aug 2 said 30. Both quoted — you pick.
Every line cites the message it came from
TypeWeb app
StackNext.js + BullMQ + Postgres
Searchpgvector
StatusBeta
01

What comes back

  • Point it at a person. You get versioned SOPs back.
  • Every line cites the message it came from, so a doubtful step can be checked.
  • Contradicted yourself? It shows both and lets you pick.
02

How it's put together

  • Next.js web app with a BullMQ worker doing the extraction out of band.
  • Postgres 16 with pgvector for retrieval across the message history.
  • Deployed with Docker Compose behind Caddy — self-hostable rather than a tenant on someone's platform.

The rest of the shelf.

All of it built inside a working dropshipping store, one job at a time.

Write the SOP you already wrote.

Send us a WhatsApp number or an email and we'll show you one built from a real channel.

ecom.beer — tools and automations for ecommerce hello@ecom.beer