Hey everyone! I've been pushing Fellow on our marketing team for the last quarter, trying to get us away from the endless Google Doc meeting notes that *nobody* can find. The big question we had was: can a tool built for engineers (with all its API talk) actually work for our non-technical crew?
Short answer: **Yes, but with some crucial caveats and a bit of setup.**
Our content, social, and demand gen teams are now using it daily. Here’s the real breakdown:
**The Good (Why they adopted it):**
* **The Google Calendar integration is magic.** Seeing the agenda right there in the sidebar cut the "wait, what are we talking about?" pre-meeting chatter by like 80%.
* **Templates are a lifesaver.** We built simple ones for campaign kick-offs, content brainstorming, and post-mortems. Non-tech folks just click a button and have a structured doc. Example of a simple template field we use:
```json
{
"Campaign Goal": "",
"Target Launch Date": "",
"Key Metrics (KPIs)": "",
"Open Questions / Blockers": ""
}
```
* **Assigning action items is dead simple.** The "Who / What / When" right in the notes, with notifications, means things don't vanish into the ether.
**The Hurdles (Where we stumbled):**
* **"Private Notes" caused confusion.** At first, people thought only *they* could see them, not realizing the whole participant list could. Had to do a mini-training on that.
* **The API/Webhook talk in settings is intimidating.** I (as the most techy person) had to own the connections to our other tools. The native integrations (Slack, Jira) are fine, but anything custom requires Zapier/Make.
* **Rate limits on the API** bit us once when I tried to sync all historical action items to a spreadsheet. Had to add delays in the automation.
**For non-technical teams, the key is:**
1. **Appoint a "champion"** who can handle the basic integrations and template building.
2. **Start with templates IMMEDIATELY.** Don't let people face a blank page.
3. **Use the native Slack/Jira/Google Calendar integrations only.** Avoid the API unless you have someone who can own it.
Overall, it's been a win for keeping us aligned. The value isn't in the fancy tech features, but in forcing a lightweight, consistent structure on our conversations. The reliability of the webhooks (for sending action items to Slack) has been solid, which is huge for adoption.
Would love to hear if other teams have found clever ways to connect Fellow to non-dev workflows (like HubSpot, Asana, or Airtable) without coding!
chloe
Webhooks or bust.