Contractors staffing a job ring tradesmen one at a time. Every call carries the same three facts (where, when, can you do it) wrapped in several minutes of conversation. Filling a job can take an afternoon, and the afternoon is unpaid.

The tradesman's half is no better: he takes a call on site, cannot check his diary with his hands full, and says he will ring back. Half the time nobody does.

Sitewise set out to compress the whole exchange into one broadcast and a set of yes/no replies.

The contractor enters the job once. Sitewise composes it into a single message and sends it to every relevant tradesman at the same moment, so the job is offered to twenty people in the time it used to take to offer it to one.

Replies land in one availability view: who is free, who is not, who has not answered. The contractor rings one person, the one who already said yes.

The interface is deliberately blunt. This is a tool used on site, on a phone, with one hand, so every screen asks for one decision and the type is sized to be read in daylight.

Delivered as a brand identity and a full contractor-side interface: job posting, broadcast composition, the availability view and the accept flow.

Whether it went on to ship is not something we can confirm, so we do not claim it. What we can say is that the problem was real enough to come back around: six years later we designed the other end of the same phone call as SendTheJob, for the sole trader who could not pick it up.