Profit.co

Core OKRs

Every key result is a KPI you must define first – goal creation is slow and form-heavy.

• The add menu offers a KPI or an initiative, not a key result – each key result means creating a KPI with its own name, category, measurement type, and unit.
• None of our three test metrics were in the built-in KPI library, so each was defined from scratch.
• Units are rigid – tracking a per-month count meant naming the KPI "qualified demos per month".
• Objectives support owners, teams, visibility, and parent alignment at creation, and teams come pre-created.

Check-ins

Check-ins are the smartest moment in the product – our 48 was flagged At Risk against the plan line automatically.

• The check-in captures a value, a lifecycle stage, and a health status, and computed that 48 was 14.3% below the planned 56 for the date – setting At Risk on its own, with an override.
• Comments support rich attachments, including audio and video.
• The history view is graph-first and busy – the comment is hard to read and today's value takes effort to find.
• The progress graph did not refresh immediately after our update.

Reporting & dashboards

Reporting is deep but reads like an advanced spreadsheet – and presentation mode is a download, not a view.

• The Cockpit offers pre-made department dashboards, but its KPI board claimed we had no OKRs defined with KPIs when we did.
• Presentation mode generates a downloadable slide deck rather than presenting inside the app.
• Proprietary charts like the progress quadrant add concepts your team will have to learn.
• We found no cascading view and no way to browse OKRs by person – profiles show manager and department, not goals.

Tasks & initiatives

Tasks and initiatives are separate systems – and our initiative landed as a non-contributing key result.

• Initiatives are another tracked goal type rather than a simple piece of work, and a separate Tasks module exists alongside them.
• The initiative we added appeared under "non-contributing key results" on the objective.

AI & MCP

AI requires your own API key and was out of reach on our trial – while an MCP connector is documented for Claude and ChatGPT.

• Nothing about AI appears in the app or the billing screens of a trial account, so the two standard AI prompts had nothing to run against.
• The documented AI drafting features require bringing your own LLM API key rather than shipping natively.
• Profit.co's site documents MCP integrations, including Profit.co in Claude and in ChatGPT.

Enterprise controls

The enterprise controls run deep – at the cost of real complexity.

• User access and email domains can be restricted, and there is a public API.
• Roles and permissions are granular to the point of being hard to navigate, and settings are organized two different ways.
• Objectives can attach to multiple teams – untangling an accidental multi-team attachment meant editing the objective by hand.
• We found no importer for existing OKRs, though sample OKRs are generated for you at signup.

Integrations

The connector catalog is the broadest we've tested so far, but wiring one up is not intuitive.

• The catalog spans 21 listed integrations, from Slack and Jira to Snowflake, BigQuery, and Tableau.
• Working out how to actually connect a data source from the settings took real effort.