diff --git a/.github/workflows/sponsors.yml b/.github/workflows/sponsors.yml
new file mode 100644
index 00000000..a5d8eea8
--- /dev/null
+++ b/.github/workflows/sponsors.yml
@@ -0,0 +1,18 @@
+# see https://github.com/JamesIves/github-sponsors-readme-action
+name: Generate Sponsors README
+on:
+  push:
+    branches:
+      - master
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout 🛎️
+        uses: actions/checkout@v2
+
+      - name: Generate Sponsors 💖
+        uses: JamesIves/github-sponsors-readme-action@v1.0.8
+        with:
+          token: ${{ secrets.SPONSORS_TOKEN }}
+          file: 'README.md'
diff --git a/README.md b/README.md
index 3fda33e0..337e6314 100644
--- a/README.md
+++ b/README.md
@@ -15,10 +15,16 @@ A simple terminal UI for both docker and docker-compose, written in Go with the
 
 ![Gif](/docs/resources/demo3.gif)
 
-This Just In: Github Sponsors is matching every donation dollar-for-dollar for the next twelve months so if you're feeling generous consider [sponsoring me](https://github.com/sponsors/jesseduffield)
-
 [Demo](https://youtu.be/NICqQPxwJWw)
 
+## Sponsors
+
+This project would not be possible without the help of its very generous sponsors! If you want to support Lazydocker's development, please consider [sponsoring me](https://github.com/sponsors/jesseduffield)
+
+<!-- sponsors --><!-- sponsors -->
+
+## Elevator Pitch
+
 Minor rant incoming: Something's not working? Maybe a service is down. `docker-compose ps`. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: `docker-compose restart`. Okay now let's try again. Oh wait the issue is still there. Hmm. `docker-compose ps`. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with `docker compose logs --follow myservice` but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run `docker-compose up myservice` and in that terminal window if the service is down I could just `up` it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do `ctrl+P,Q`, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
 
 What a headache!