A calling card for the engineer who answers to the site gate

Every page begins with his name set in spaced capitals, centred over the words Chief Technology Officer and a centred line of page links, like engraved stationery. On Home, a bordered card sits on the pale clay background with a cream block offset behind it like a second sheet. His portrait fills the narrower left panel. The right panel carries the small label An introduction, then the largest line on the page: Software ready before the site gate opens. A short copper rule separates that claim from his headline about the hour between six and seven in the morning, followed by Australia, an Open to note naming board appointments and advisory roles, and a Start a conversation link. On a phone the card turns over, so the argument arrives before the photograph.

Beneath the card, a broad quotation headed My approach gives his philosophy in the display face: a site manager at a locked gate with forty workers behind him does not care which component failed. A narrow column titled At the intersection of lists the five practices behind it, from reliability measured at the site gate and Australian data residency to technical debt in a small engineering team. A band of three figures follows, each figure above its label and context: A$47.2m of revenue, 1,850 active construction sites and 58,000 workers signing in on a typical weekday, most of them before quarter past seven.

Under Work worth discussing, Edward's three cases appear as numbered rows that open in place, so a reader chooses how deep to go. The first records eleven weeks of paused feature work to make the database enforce separation between customers, and the A$410,000 expansion a large builder delayed as a result. The second moves 430 million older site photographs to slower storage and admits that a civil contractor left over it. The third explains why he paid A$690,000 a year for a standby in Melbourne instead of a cheaper one in Singapore. His thesis, proof points, current focus and a contact panel follow.

Copper uses a warm clay ground, sand-coloured panels and a cream offset, with dark brown text and a deep copper accent for rules, numbers, dates and links. The palette recalls brick, timber and pipework more than a software company's blue, which suits a leader whose customers are builders and whose stories start in site sheds. It stays restrained enough for a nomination committee. Headings use DM Serif Display, a high-contrast serif that gives his headline and case titles the weight of a printed card. Body text, figures and labels use Manrope, a clear geometric sans-serif that keeps long passages about failover rehearsals, residency clauses and storage tiers readable. Printed, everything becomes black on white, ready for a board pack.

The Profile page, headed From the site shed to the server room and back, sets his portrait beside a biography that opens with an excavator's hours on a Newcastle job, and closes with three colleagues' perspectives, including his committee chair's. The Career page opens on a dark brown panel with cream lettering and the heading Six appointments between the site docket and the board paper. Each role sits on its own sand-coloured card with dates, team, budget and outcomes. The Board Readiness page starts with a bordered two-column brief: his contribution on one side and, on the other, a committee table, twenty-two available days and no current directorships. Exposure, two judgement examples, conflicts and governance learning follow in a single centred column.

The Card suits technology leaders whose credibility comes from a few consequential choices rather than famous employers: engineering heads at property-technology and field-service software companies, platform leaders at engineering consultancies, and infrastructure managers moving into executive roles, as well as first-time board candidates wanting a calm opening.