What MetaOpus does
One record of requirements, consultants, partners, submissions and outcomes — and what that makes answerable.
A staffing desk runs on six things at once: the requirements arriving, the consultants available, the partners who carry work, the submissions in flight, the clients deciding, and whether any of it converted. MetaOpus keeps all six on one record.
What that changes
Because a submission knows the requirement it came from, the partner that carried it and the outcome it reached, questions that used to need somebody's memory have answers with counts behind them — which source produced a placement, which partner absorbs effort and returns nothing.
What it does not do
- It does not invent what a posting did not say. When a requirement states no rate or engagement type, it is recorded as not stated.
- It does not replace an applicant tracking system on its own. Where one is the system of record, MetaOpus connects to it.
- It does not show a rate to a consultant. Consultant logins never receive one, in any screen or email.
Frequently asked
Is this an applicant tracking system?
No. Where an ATS is your system of record for candidates, MetaOpus connects to it rather than competing with it. What MetaOpus adds is the market side — which requirements arrived, which partner carried them, and what any of it converted to.
Do we have to move our existing data in to start?
No. A desk is useful from the first consultant and the first requirement. History can follow later, and how far back it reaches depends on your plan.
Can a consultant see what we are paid for them?
Never. Consultant logins do not receive a rate in any screen, any export or any email. That is a property of the product, not a setting somebody can switch off by accident.
Was this helpful?
More in Getting started
Still stuck? Tell us what you are trying to do — a person answers, and we would rather fix the product than explain it twice.