Skip to content
Aramis:Insight
OverviewThe three tools, and what each one does with what you enter

For CISOs and security leaders

Three tools, one question: does the team match the work?

Define the role the work actually needs, plan the hours and coverage it takes, and measure how the team's knowledge and judgment line up with it. Each tool stands on its own, so you can start with whichever decision is in front of you.

The three tools

Use them in any order. Nothing here requires the others.

The Requisition Compiler

A requirement written as a contract: the work, the evidence that would settle it, and the questions a panel should ask. It runs in your browser and keeps the compilation on your account so you can return to it.

Workforce planner

Your own estimates of the work, the hours the team has, and what developing, contracting or hiring would cost at their real lead times. It keeps what is uncertain visible instead of resolving it quietly, and it saves nothing.

Campaigns and results

Measured results for a published role, read at team level. Every participant is invited, agrees to be included before starting, and can withdraw.

What this will not do

  • No employer view reaches a named individual's result. Team results only, and a slice below a campaign's floor is dropped rather than masked.
  • Measurement comes only from people who were invited, agreed to be included before starting, and can withdraw afterwards.
  • The workforce planner is your own estimates, not a measurement. A closed workload gap is not adequate staffing, and hours removed are not payroll savings.
  • No tool here selects a person, recommends a dismissal, or automates a staffing decision.

No measured results here yet

Campaigns run inside an Aramis:Build organization, and those are set up by Aramis rather than self-serve during the pilot. The Requisition Compiler and the workforce planner need no organization and are open to you now.