ExecutionOS

Four connected areas: Strategy (your plan and focus areas), OKRs (AI-suggested, editable objectives), Campaigns (trackable goals with priority, milestones and owners), Execution workflows (the department-level work that delivers those goals), and an Integrations Feed for signal from your other tools.

Yes, it's designed to work alongside the rest of the PerkFlow platform. If you opt in to these other modules, ExecutionOS integrates with shift handovers in Coverlap, workforce cost modeling in HeadTally, and performance reviews, so the same data doesn't have to be re-entered module by module.

Once your strategic plan and focus areas are set, ExecutionOS proposes OKRs aligned to them, based on your own data. You review and edit every suggestion before anything launches as a live goal — nothing goes live automatically. You can also launch OKRs from scratch, without using the AI suggestions feature.

You give it a short summary of your monthly, quarterly, or yearly objectives, then select the Primary Focus Areas you want your team to focus on — categories like People & Culture, Customer Success, Operational Efficiency, Innovation & Profitability, Growth & Revenue, and Sustainability & ESG. Every OKR, campaign, and execution flow gets tagged back to one of these focus areas.

A Campaign is the goal itself — for example 'Cost Optimization,' with a priority level, a due-date window, milestones, and a progress percentage. An Execution workflow is the actual department-level work that delivers that goal, such as 'Procurement Execution' under Cost Optimization — with its own steps, assignees, status, and progress.

The goal it's tied to and its measured impact (for example '+6% impact' or '−12% risk'), a priority level, how many of its steps are complete, a due date, the people assigned to it, its status, and a progress percentage.

Teams whose strategy and OKRs live disconnected from the work that's supposed to deliver them — a plan in a slide deck, goals in a separate tool, and actual tasks in yet another, with someone manually reconciling the three before every leadership review. ExecutionOS is built for whoever owns that reconciliation today (often an ops lead, a chief of staff, or a PMO) and for the leadership team that currently can't see, without asking, whether a given campaign is actually moving because of real execution work.

Most of those tools do one layer well, not all four connected. General project tools (Asana, Monday, ClickUp) are built around tasks and boards. Asana's Goals feature only unlocks on its top-project tier; and even then, goals aren't generated from a strategic plan or automatically linked to the tasks underneath them. Dedicated OKR tools (Quantive, Betterworks, and similar) track objectives well but don't include the department-level execution work — you'd still run a separate PM tool alongside them and reconcile the two by hand. ExecutionOS's difference isn't that we do PM better or we do OKRs better in isolation. It's that Strategy, OKRs, Campaigns, and Execution workflows are one connected system by default, so a goal's real progress comes from the work that's actually logged against it, not a status someone typed in before a meeting.