diff --git a/.wakatime-project b/.wakatime-project
new file mode 100644
index 0000000..6989299
--- /dev/null
+++ b/.wakatime-project
@@ -0,0 +1 @@
+@recaptime-dev/squad
\ No newline at end of file
diff --git a/README.md b/README.md
index db57166..a91c429 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,9 @@
-# Welcome to the hub for squad members
+# `@recaptime-dev/squad` - hub for squad members
+
+[![@recaptime-dev/squad profile badge](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Frecaptime-dev%2Fsquad%2Fmain%2Fbadges-api%2Fprofile-badges%2Fsquad.json
+)](https://recaptime.eu.org/team-profiles)
+[![Open Collective backers and sponsors](https://img.shields.io/opencollective/all/recaptime-dev?style=for-the-badge)
+](https://opencollective.com/recaptime-dev)
 
 Most of the squad members have developer to maintainer access (depending on the department they're currently in)
 to most of the repositories in both Mauiunm GitLab instance (here) and GitLab SaaS, alongside GitHub.
@@ -11,19 +16,23 @@ to most of the repositories in both Mauiunm GitLab instance (here) and GitLab Sa
 
 _Last updated as of 2023-06-28_
 
-* **Squad Leads (Executive Team)** (@recaptime-dev/squad-leads): @ajhalili2006
-* **Recently onboarded crew**: N/A
+* **[Squad Leads (Executive/Leadership Team)][leads]** (@recaptime-dev/squad-leads): @ajhalili2006
+* **Recently [onboarded][onboarding] crew**: N/A
 * **Currently active**: @ajhalili2006
 * **On break/vacation**: N/A
-* **Currently/recently offboarded**: N/A
-* **Email**: `squad [at] crew dot recaptime dot eu dot org` [^2]
+* **Currently/recently [offboarded][offboarding]**: N/A
+* **Email**: `squad [at] crew dot recaptime dot eu dot org` [^2] [^3]
 
+[leads]: https://squad.lorebooks.eu.org/organization/teams/leadership
+[onboarding]: https://squad.lorebooks.eu.org/handbook/onboarding
+[offboarding]: https://squad.lorebooks.eu.org/handbook/offboarding
 [^2]: This will actually forward your email to everybody at the team, excluding any community vounteers unless opted in.
+[^3]: Technically we use `yourfriends@` in the past, but we're migrating off that since then.
 
 ## Quick links
 
 * **Chat**: [Matrix space](https://matrix.to/#/#community.recaptime.dev:envs.net), [Keybase](https://keybase.io/recaptimedev), [Discord]( https://discord.gg/5dURUcM)
-* **In other code forges**: [sourcehut](https://sr.ht/~recaptime-dev), [Jetbrains Space](https://recaptime.jetbrains.space), [GitHub](https://github.com/recaptime-dev)
+* **In other code forges**: [sourcehut](https://sr.ht/~recaptime-dev), [Jetbrains Space (internal)](https://recaptime.jetbrains.space), [GitHub](https://github.com/recaptime-dev), [GitLab SaaS](https://gitlab.com/recaptime-dev)
 * [**Squad Wiki**](https://squad.lorebooks.eu.org) ([internal version - use your Internal SSO account to access](https://internal.squad.lorebooks.eu.org))
 * **Community Code of Conduct and other policies**: <https://policies.recaptime.eu.org>
 
@@ -31,9 +40,10 @@ _Last updated as of 2023-06-28_
 
 > **Note**: These also apply to anyone outside Recap Time Squad.
 
-* Remember that tagging `@recaptime-dev/squad` will trigger email notifications to ALL users under the subgroup, which might overwelm things on the backend easily.[^1] We recommend directly mentioning the individual members themselves.
+* Remember that tagging `@recaptime-dev/squad` will trigger email notifications to ALL users under the subgroup, which might overwelm things on the backend easily.[^1] We recommend directly mentioning the individual members themselves (or the ).
 * Only tag everyone in case of:
   * emergency async meetings, especially as required by @RecapTime/legal team.
   * important org-wide announcements that might affect the operations of the organization
+* For GitHub users, simply ping the @RecapTimeSquad admin account.
 
 [^1]: That mistake was happened in GitLab SaaS at <https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19861#note_242645866>, but @ajhalili2006 might forgot what issue is it for that within GitLab team's namespace.