FounderLoopBlog
Architecture

Built onAgent Switchfor the Flip the Switch hackathon by WeMakeDevs and DevTools Academy

Architecture

Switch connects the chat rooms. One FounderLoop agent turns qualifying messages into decisions the founder can make in Slack.

  1. Source chatA customer or teammate posts in a connected chat room.
  2. SwitchDelivers the room event to the agent.
  3. FounderLoopChecks the source, classifies the signal, and adds context.
  4. Founder in SlackAccepts, rejects, or comments on the private card.
  5. Verdict in SlackThe right private channel gets the decision and source link.
Product, Sales, or Support receives the verdict through Switch. General requests stay in the founder channel. Read how it works.
The FounderLoop cycle: a user says it, evidence is kept, the founder decides, the team is told. FounderLoop

Switch documentationSwitch on GitHubswitchagents.aiFlip the Switch hackathon

Without Switch

What FounderLoop would build instead

    With Switch

    What FounderLoop builds today

      Simulated story: nothing is sent anywhere

      How it works

      FounderLoop is a Node.js agent that listens to authorized Switch rooms over a WebSocket. Ordinary messages can trigger the flow without a mention, and source rooms are read-only for the agent.

      Verify the message and add context

      Every founder card includes the verbatim quote and a link to the exact message. FounderLoop holds a signal if it can’t verify that link. Product checks the roadmap in Google Docs, Revenue looks for account context in a Leads Sheet, and Commitment surfaces incidents or explicit promises from trusted staff. An optional General route covers direct requests for the founder.

      Decide in private Slack

      The authorized founder can accept, reject, or comment with a Slack button or a text command. FounderLoop records one decision per card and sends the verdict with the same source link. The card closes when Switch acknowledges the verdict.

      Keep a record across restarts

      SQLite stores the source evidence, decision, and delivery queue. If a send may have succeeded, FounderLoop holds it for an operator to check before retrying.

      Explore the FounderLoop implementation on GitHub for the full routing logic, integration details, and setup. Read the setup guide on this site.