Unifying Our Toolset as a Public Benefit Company with the Teamwork Collection
Hello Community! I want to share about my company’s transition from single apps (with different seat counts per app) to the Teamwork Collection.
Last year, my company, Common Good Learning Tools, became certified as a Public Benefit company. In the U.S., that qualifies us as a social enterprise. We’re a small, primarily remote educational technology software company focused on building products for the common good - mostly improving the lives of educators and education departments worldwide. We operate like a nonprofit, often utilizing the lowest price or free tools for our own teams, allowing us to give back more to the communities we serve.
Certification allowed us to apply for the nonprofit discount and move all employees into a unified experience with the Teamwork Collection (Jira, Confluence, Loom, and Rovo). I wanted to highlight a few benefits I’ve seen from this transition over the past few months.
🧰 Our toolset is aligned and available to all
-
Before this switch, some of us who loved Confluence had free licenses, but not everyone could access our wiki documents. Some used other whiteboard tools (only free versions), so it was hard to find past brainstorming sessions and deal with free version limits such as only one board.
-
Now, Confluence is our company hub and still evolving. With smart links, we bring in resources from Google Drive, Figma, and more, giving everyone access to needed information. Whiteboards and Rovo simplify work. Recently, I fed Rovo a spreadsheet and quickly created and organized uniform stickies. I even saw how Rovo might organize my topics to gain new perspectives without needing to "rubber duck" with a colleague.
🧠 Collective knowledge is shared and accessible
-
Before the switch, some used Jira regularly, but other tools were less aligned and often contained outdated information. Google Drive was a mix of information, Jam videos and screencasts scattered, a self-hosted wiki was hard to access and locate, and our Slack version limits message history to 90 days. This made it hard to recall past conversations, find information, and make decisions quickly.
-
Now, as we adopt TWC as our main knowledge base, it’s easier to find information, curate decisions, and ensure we have tools to move quickly and impact our users.
🤳 Loom > “Can we hop on a call?”
-
Slack huddles and Google Meets are tricky across time zones. Loom makes asynchronous video communication easier. We benefit from recording Looms from Confluence pages or Jira tickets, as well as the Loom meeting recorder. Since our plan doesn’t allow Google Meet recordings, we use Loom for that. The AI summary helps facilitate quick reviews. We also love using Loom to record a meeting about a new software feature while then having Rovo start our customer-facing user guide based on context from our current guides.
⭐️ Other Benefits
- Unified billing with less people submitting reimbursements for different apps
-
Teamwork Graph allows the tools to work together and brings our information into a unified space
-
Clearer onboarding and offboarding: new teammates get access to a standard toolset on day one, and offboarding is simpler and safer
-
Better security and compliance: fewer scattered tools and shadow accounts to manage, with permissions handled in one ecosystem
-
More consistent processes: templates, workflows, and documentation live in one place, so teams can reuse what works instead of reinventing it
-
Easier reporting and visibility: it’s simpler to see what’s happening across projects when work, docs, and communication are connected
👂 I’d love to hear from other nonprofits and social enterprises:
-
Have you gone through a similar transition to a unified toolset?
-
What’s changed for your teams as a result?
-
Are there any practices or setups in Jira, Confluence, Loom, or Rovo that have worked especially well for you?
🗣️ Please share your experiences or tips in this discussion!