# Both sides of the market can now see their numbers

Contractors get their bid funnel on every tier.

Published 2026-07-23 By Aditya Kannan & Piotr Gospodarczyk

Tags: [product-updates](https://handee.ie/news/tag/product-updates/) [facility-teams](https://handee.ie/news/tag/facility-teams/) [analytics](https://handee.ie/news/tag/analytics/) [contractors](https://handee.ie/news/tag/contractors/)

Version 1.3 gave operators a view of their pipeline: where work orders sit, how long each stage takes, what is ageing past the point where somebody ought to care.

It gave vendors nothing.

That is a strange gap in a two-sided system. An operator with a slow pipeline raises a ticket. A vendor who stops seeing the point of bidding does not raise anything. They just open fewer RFQs, and the first symptom anyone else notices is the operator's unquoted dispatch rate creeping up several weeks later, by which point the cause is invisible.

Version 1.4 instruments the other side, and sharpens the operator view where it was blunt.

## Contractors: your bid funnel, on every tier

Every vendor organisation now has a conversion funnel covering the work that reached them and what they did with it: dispatches received, quotes submitted, quotes won, and the win rate those three produce. Choose the date range you want to look at.

The funnel is split by how the work arrived.

**Marketplace** work is the open route: you request a bid, the operator approves or denies it, and an approved request puts you in front of the job. That path carries its own number, the bid approval rate, calculated over decided requests only. Requests still sitting with an operator are excluded rather than quietly counted as losses.

**Direct** work is the invited route: an operator dispatched to you specifically.

The two paths fail differently. A poor marketplace approval rate is a problem with how you present the organisation before anyone reads a price. A healthy approval rate with a poor quote win rate is a pricing or turnaround problem. A blended number tells you something is wrong and nothing about where.

**This is free on Standard.** It was originally built behind Premium, and we moved it. Charging the supply side for the visibility that keeps it engaged trades marketplace liquidity for a subscription line, and that is a bad trade for everyone in the network, operators included. Vendors list free, and now they measure free.

## Facility teams: on-time completion, split by priority

The operator Advanced Analytics dashboard gains on-time completion, reported by priority rather than as one blended figure, with a chart.

A single portfolio-wide on-time percentage is close to useless. It moves mostly with routine volume, because routine jobs are the bulk of the work and the easiest to close inside target. A high-priority job running late is exactly the job that generates the phone call, and it is precisely the one a blended average absorbs without a flicker.

Split by priority, the figure starts answering a question you can act on: are we missing targets everywhere, or only where it costs us?

As with the rest of the analytics work, nothing new needs to be logged. It reads the status history the system already records as work moves through its lifecycle. Advanced Analytics remains part of the Growth plan and above.

## The bug we found while doing this

Building the vendor funnel meant running vendor-side queries under the database role a real vendor actually uses, rather than the permissive one convenient in development. Which is how we found that our row-level security policies on quotes and invoices were hiding vendor records from the vendor that owned them.

Other tenants were correctly walled off. The vendor's own rows were walled off too.

That is the characteristic failure of isolation done at the database layer: it does not error. The query succeeds and returns nothing, and an empty table looks exactly like a quiet week. Both policies are corrected in 1.4, and vendors see their own quotes and invoices.

A release note could fairly call that a policy adjustment. In practice it was records a customer owned and could not read, which is why it is written up here rather than left in the changelog.

## Privacy, in short

Handee now publishes a [Privacy Policy](https://app.handee.ie/support/privacy) and a [Cookie Policy](https://app.handee.ie/support/cookies), both readable without an account, alongside the support policy and service levels published in 1.3.

We also added acquisition analytics to the public site, which is why those documents exist now. Consent is denied until you grant it, and withdrawing it is one click from the footer. No analytics tag runs anywhere behind a login, because our dashboard URLs carry tenant identifiers and single-use tokens that have no business reaching Google. The reasoning is set out on [our parent company's site](https://wisdomengineers.ie/insights/measuring-without-collecting/).

## Where this leaves the product

Compliance gating was the point of Handee from day one, and it remains the point: work does not reach a vendor who is not currently verified for that site's jurisdiction and trade. Measurement is what makes the rest of the promise checkable. An operator can see where the portfolio actually stands. A vendor can see whether bidding here is worth the effort.

We ask to be judged on the human time recovered on the work you hand over.

Operators start free. Two seats, ten work orders, ten facilities, no card. Vendors list free on Standard, funnel included.

[Get started for free today](https://app.handee.ie/auth/register)
