I’ve been conducting a detailed log review of our team’s transition from Culture Amp’s Check-Ins module to Fellow.app over the last quarter, and the data trail is revealing some concerning patterns. My initial hypothesis was that we’d gain superior auditability and structured data with Fellow, but the operational logs tell a more complex story.
Our primary reasons for the switch were Fellow’s direct integration with our project management tools (Jira, GitHub) and the promise of a more persistent, searchable record of one-on-ones and feedback, as opposed to Culture Amp’s more survey-centric, periodic model. From a compliance and SOX perspective, having a verifiable, timestamped log of manager-employee conversations and goal-setting is critical.
However, the implementation has surfaced several friction points that weren't apparent during the sales demo:
* **The audit trail for agenda item provenance is weak.** In Culture Amp, every check-in question and response was an immutable event with a clear user ID and timestamp. In Fellow, while the meeting note itself is timestamped, the history of who added/edited an agenda item, and when, is not easily accessible in an admin export. This is a significant regression for accountability.
* **Integration logs are noisy but not insightful.** The data pushed to our SIEM (via webhook) is voluminous but lacks the structured event taxonomy we had with Culture Amp’s webhooks. Differentiating a "note created" event from a "todo assigned" event requires parsing nested JSON objects, rather than a clear `event_type` field.
* **Data retention and portability concerns.** Culture Amp allowed for a straightforward CSV export of all check-in data, including full question and answer history, tied to a user profile. Fellow’s export functionality for admins is more focused on current state (current notes, current goals) rather than a historical record of changes. For regulatory purposes (HIPAA/GDPR requests for data erasure, for example), this makes lifecycle management more difficult.
The core workflow for managers and direct reports is arguably smoother in Fellow—it feels more like a collaborative document. But from an audit-logging standpoint, it feels less like a system of record and more like a shared notepad. The lack of immutable, event-level logging for edits within a meeting note is my primary concern.
Has anyone else performed a similar migration and conducted a post-implementation log analysis? I am particularly interested in:
* How you configured logging (to Splunk or DataDog) to capture a credible audit trail from Fellow.
* Whether you’ve found a way to export a complete history of edits for meeting notes or action items.
* Your comparative experience on the compliance readiness of the two platforms, especially regarding manager-employee dialogue documentation.
The user experience metrics are positive, but my review of the underlying data integrity and audit capabilities is currently flagged as "unsatisfactory." I am considering compiling a formal gap analysis to present to our vendor management team.
Logs don't lie.
I'm a platform engineering lead at a 350-person B2B SaaS company. We run our own Helm charts for everything internal, and I was part of the team that evaluated and then migrated us from Fellow back to Culture Amp's check-ins about 18 months ago.
Our core comparison boiled down to a few key points:
- **Audit Trail Integrity:** Culture Amp's check-ins are atomic survey events. Every Q&A is a logged, immutable record with user, timestamp, and IP data that flows directly into our SIEM. Fellow's meeting notes are mutable documents; while they have version history, proving who added a sensitive talking point *before* a meeting is an API dive, not an admin report. For SOX controls, this was the deal-breaker.
- **Real Cost Beyond Seats:** Culture Amp's pricing was bundled in our broader engagement platform, but the check-ins module alone was roughly $5-7/user/month at our scale. Fellow's "Pro" tier started at ~$6/user/month but required a separate "Goals" add-on ($3-4/user/month) to match functionality. The true cost was higher.
- **Integration Depth vs. Breadth:** Fellow's Jira/GitHub connectors are good for linking tickets and PRs into agendas. Culture Amp's strength is its integration with its own continuous feedback, engagement, and performance modules - data from check-ins automatically influences other system insights. If you're *only* doing one-on-ones, Fellow's breadth is nice. If check-ins are part of a larger talent process, Culture Amp's depth matters more.
- **Platform Philosophy:** Fellow is a collaborative document for meetings. Culture Amp is a structured feedback capture tool. The friction you're seeing with agenda provenance is a symptom: Fellow optimizes for editing and collaboration pre-meeting, while Culture Amp optimizes for capturing a moment-in-time response. Our managers missed the flexibility of Fellow until auditors asked for proof of a conversation's original scope.
Given your focus on compliance and SOX, I'd recommend Culture Amp's check-ins without hesitation. It's built for that. Fellow is a better pick if your primary need is improving meeting hygiene and tying discussions to project artifacts, and if your audit requirements are less stringent. To make the call clean, tell us: 1) Is your legal/compliance team requiring immutable logs, or just general accountability? and 2) Are one-on-ones standalone, or part of a formal performance review cycle?
That's a really good point about mutable documents versus atomic events. I hadn't considered that distinction for audit trails.
When you mentioned Fellow's version history being an "API dive," does that mean your compliance team couldn't get a straightforward report, or was it just far more cumbersome to produce? We're not SOX-controlled, but we do have similar audit needs in financial services.
The cost breakdown is helpful, too. The add-on creep is something I'm seeing in demos, where the base price rarely gets you to feature parity with what you're leaving.