Skip to content
CogniYukti

For staffing and IT services

The bench is a number somebody works out on Friday.

By the time it reaches a spreadsheet it is a week old, and the expensive people are somewhere in the middle of the list.

CogniYukti makes the bench a screen, ordered by what the idleness has cost, with the open requirement one click away.

  • Bench priced daily
  • Projects, timesheets and margin
  • Contractors paid in the same product

Bench · today

Sorted by cost

  • R. Venkatesan

    41 days idle

    Integration lead

    Meridian Health · integration lead

  • A. Bandyopadhyay

    28 days idle

    Data engineer

    Takahashi Foods · data platform

  • J. Okonkwo

    34 days idle

    QA automation

    No open requirement matches yet

  • M. Halvorsen

    52 days idle

    Junior developer

    Northwind · support pod

The longest idle is not the top row. The most expensive one is — which is the whole reason the list is worth opening on a Tuesday.

Illustrative

Idle, and what idle costs

A bench is not a list of names. It is a daily cost with a date on it.

Two facts decide what you do on a Monday: how long this person has been sitting, and how much that has added up to. Everything else — their skills, their last project, the rate they were on — is context for those two.

CogniYukti computes both from the daily cost and the date each person went on bench, so the screen is current when you open it rather than when somebody last updated a file. The list is sorted by cost accrued, because the alphabet has never once been the right order for this.

Rolling off

  • Consultant Ain 12 days
    Java · Spring Boot · off project 04 Oct
  • Consultant Bin 19 days
    Data engineering · off project 11 Oct

Known today. Not discovered when the first idle day is already billed to you.

Open, and already yours

  • Backend engineer ×2Existing account · starts 06 Octmatches Consultant A
  • Data platform engineerNew logo · starts 20 Octmatches Consultant B

Both sides live in the same product, so the question is a filter rather than a phone call on Friday.

Illustrative
  • Banded by how long

    Fresh, warming, hot and critical — so a sixty-day problem does not look the same as a six-day one at a glance.

  • Redeployment is the point

    The person at the top of that list is a candidate for the requirement that came in this morning, already in the system with skills and rates on the record. Nobody has to remember they exist.

  • Notice period as a planning fact

    Sixty days is the difference between a start date you can promise and one you cannot. It is a field on the candidate and a limit on the role.

Submission to invoice

Three businesses stapled together, and the staples leak.

A staffing firm sources, delivers and bills. In most firms those are three tools keyed by a name typed slightly differently each time, and the margin quietly disappears between them.

StepThree toolsOne record
  1. SubmissionATS · name typedOne candidate record
  2. PlacementSpreadsheet · name retypedSame record, fee attached
  3. InvoiceAccounting tool · name retypedDrafts from the placement
  4. PayoutReconciled by handCommission accrues on the same row
The margin does not leak at any one of those steps. It leaks in the join between them, which is the part nobody owns.
Illustrative

Delivery

A signed scope becomes a project, not a new spreadsheet.

The work that follows a placement is where services firms actually make or lose money, and it is usually the least instrumented part of the business.

SOWs and milestones

The statement of work is an object with milestones under it, so a change request is a recorded event rather than an argument in email.

Timesheets and expenses

Tied to the scope that authorised them, approved by the person who owns it, and reimbursed through payroll rather than a separate claim tool.

Profitability, live

Per project, while it is running. Not a number assembled at year end when nothing can be done about it.

Leakage alerts

Effort going in that nothing is billing for, surfaced as a view rather than discovered in an audit.

Resources and skills

Who is available, what they can actually do, and what they are committed to — the same records the bench screen reads.

Contractors, paid properly

Contractor records, invoices and payments beside permanent payroll, with PF, ESIC, PT and TDS in the core rather than exported.

Volume

Campus and bulk hiring without a parallel process.

A drive is an event with cohorts under it, enrolled in audited batches. The people who come out are the same records everything else uses — which is the point at which a campus hire can be onboarded, put on a project and paid without leaving the platform or re-importing anything.

The same is true of the partner firms you source through. They submit against the requisitions you assign them, through their own portal, and their invoices arrive the same way. At quarter end you can see which vendor's submissions actually converted.

Illustrative
On benchDays · costOpen requirementFit
Consultant A71 · ₹6,30,000Senior Java — PuneDirect evidence
Consultant B44 · ₹3,52,000Data platform — HyderabadDirect evidence
Consultant C33 · ₹2,80,500SAP FICO — MumbaiGap: notice period
What a redeployment decision looks like with both halves on one screen.

Questions we get asked

The ones that decide it.

Does the bench figure update on its own?

It is computed from the daily cost and the bench start date, so it is current whenever you open the screen. There is no weekly rebuild and no owner of the spreadsheet.

We place contractors and hire our own staff. Two systems?

One. Mode is set per requisition, so client-billed roles and internal hires live in the same list with different behaviour, and your own employees are in the people module of the same product.

Can we see project profitability before the project ends?

Yes. Timesheets, expenses and change requests roll into a per-project view while it runs, with leakage surfaced rather than discovered.

What about the people we source through partner vendors?

They arrive through the vendor portal as submissions against your requisitions, and their invoices come in the same way. Vendor performance is one of the standing views.

Do you handle multiple legal entities?

Yes — entities, their statutory registrations and their invoicing are first-class, which matters once a group has more than one company.

Book a demo

Show us your bench.

Bring real bench rows and one live requirement. The interesting part of the demo is watching the two meet.

  • Load a handful of real bench rows with their daily cost
  • Put a live requirement in and watch the redeployment match
  • Open a project and show me margin while it is running
  • Run a contractor invoice through to payment
  • Show me submissions and conversion by partner vendor
  • Run payroll and show me the statutory returns