A 32 person consultancy in Madrid was running monthly print spend of approximately 720 euros, with colour share at 38% of pages. After rolling out pull printing with PIN release, monthly spend fell to 425 euros and colour share dropped to 22%. The change cost less than 400 euros to implement and paid back inside the first month.
The consultancy had not seen a volume spike. Monthly page count had been stable at around 9,400 pages for a year. The cost line had still grown 18% over the same period. The increase came from a quiet rise in colour share, from 26% to 38%, mostly driven by client deliverable documents being printed in colour where mono had previously sufficed.
Colour click rates ran at 0.072 euros against mono at 0.011 euros. A 12 percentage point rise in colour share over fixed volume added roughly 130 euros monthly. The pattern was invisible on the invoice because total page count had not changed; only the mix had shifted.
Pull printing introduced a release step at the device. Users send their job to the print server as usual, then walk to any MFP, tap an ID badge or enter a PIN, and choose which jobs in their queue to release. Three behavioural changes followed.
The consultancy measured an 11% baseline of jobs sent but never collected. Drafts that the user changed their mind about, accidental clicks, jobs sent before realising the document needed a final edit. These previously hit the printer regardless and ended up in recycling. Under pull printing, they expire in the queue and never reach paper.
The release screen shows job metadata including page count, duplex setting and colour mode. Users routinely noticed colour mode set on documents that did not need it. The release screen offers a one click conversion to mono before final release. About 20% of colour jobs convert at this step.
The consultancy paired pull printing with a default driver setting change to mono and duplex. Users who never opened the print dialog now produced mono duplex output by default. This addressed the larger structural drift; pull printing addressed the residual drift on jobs where users had specifically chosen colour.
The headline 40% saving on colour print cost is the most visible outcome. The underlying picture includes three other lines: an 11% reduction in total pages (the never collected jobs), a 9% reduction in paper consumption (combined with the duplex default), and a small reduction in toner replenishment frequency.
Across all four lines the total monthly print spend fell from 720 euros to 425 euros, a 41% reduction. The colour line within that fell more than 40% because it carried both the page reduction and the share reduction.
The rollout took two weeks end to end. The consultancy used a free tier of an open source pull printing software for the first month to validate the approach, then upgraded to a paid licence once the value was clear.
| Week | Action | Owner |
|---|---|---|
| 1 | Pull printing server install on existing office server | IT (external consultant, 4 hours) |
| 1 | Driver configuration update on all 32 client devices | IT consultant via MDM |
| 1 | Default driver settings switched to mono duplex | IT consultant |
| 2 | 15 minute team briefing on pull print workflow | Office manager |
| 2 | 30 day baseline measurement | Office manager |
The 30 day measurement after rollout produced four data points that informed the decision to upgrade to paid licensing.
| Metric | Pre rollout | First month | Change |
|---|---|---|---|
| Monthly pages printed | 9,400 | 8,370 | −11% |
| Colour share | 38% | 22% | −16 pp |
| Jobs converted from colour to mono at release | n/a | 21% of colour jobs | — |
| Total monthly print spend | €720 | €425 | −41% |
Pull printing software contracts run 12 months minimum, so the consultancy held a five month review to confirm the change was sustainable. Three findings emerged.
The initial drop held. Some drift back was anticipated, but by month five the figure sat at 22 to 24%, roughly where the rollout settled. Users had internalised the colour decision rather than reverting once novelty wore off.
Two staff who work primarily on client facing visual materials asked for their personal driver defaults to remain on colour. The request was granted with a per user override. The 30 person majority kept the new defaults.
One concern at rollout was that more steps at the device might increase user error and service calls. Five months of data showed no change in ticket frequency. The pull printing software worked reliably enough that it became invisible after the first two weeks.
The consultancy moved from a free open source tier to a paid managed offering at month two for support and reporting reasons. The paid licence runs at 4 euros per user per month, totalling 128 euros monthly across the 32 staff. Against the 295 euros monthly saving, the net positive comes to roughly 167 euros, or close to 2,000 euros annually.
| Line | Monthly amount |
|---|---|
| Print spend before pull printing | €720 |
| Print spend after pull printing | €425 |
| Pull printing software licence | €128 |
| Net monthly position | −€167 (saving) |
Pull printing addresses the discretionary part of the colour decision. It does not affect the structural part. Three categories of colour print remain unchanged at any office.
Marketing materials, presentations and pitch documents continue to print in colour. The release screen does not encourage conversion of these; they are legitimately colour documents.
Reports with colour charts and infographics print in colour because that is the source. Converting to mono would distort the content.
Some users print in colour because they prefer it. Pull printing makes the cost visible but does not override the preference. The two staff who requested override defaults fall in this category.
Three lessons from the consultancy's experience transfer broadly.
Pull printing alone catches the visible colour decisions. Default driver changes catch the invisible ones (where users never opened the dialog). Combined they produce the full saving.
The consultancy spent the first week measuring monthly colour share and total spend before any change. Without the baseline, the post rollout figures would have looked impressive but lacked the comparison that made the case for the paid licence.
The 15 minute team briefing was enough. Users understood the new workflow in two demonstrations and a short Q&A. Longer training sessions add no value and risk turning the rollout into an event when it should be a quiet operational improvement.