// About Quarri

Theo Leslie and David Jayatillake.

Theo Leslie

Theo Leslie

Co-founder & CEOtheo@quarri.aiLinkedIn
$1bn+turnover at FTSE-listed and global companies, leading change and transformation programmes
10+ yrsrunning strategy and change programmes
Forest to millAI implementations led across the timber supply chain
David Jayatillake

David Jayatillake

Co-founder & CTOLinkedIn
20 yrsbuilding data systems, at Lyst and Worldpay among others
25+people in data teams managed
VP of AIat Cube, joined through a semantic layer startup, Delphi Labs
// 01 · The founders

Experience, and the work at Quarri.

Theo Leslie

Change and transformation programmes led at companies turning over $1bn+, FTSE-listed among them. As Director of Strategy at Worldpay, led the internal strategy team and ran change across the business alongside McKinsey.

At Quarri, leads AI implementations across the timber supply chain, from forest management to the mill, including at a publicly listed timberland company. Each is run as a change programme: the goal agreed with leadership, then each department owning its part.

  • Co-founder & CEOQuarri · theo@quarri.ai
  • Director of StrategyWorldpay
  • VP GrowthRed Sky, a lending fintech
  • Founding team, delivery divisionA large hospitality group
  • Chartered accountantPwC

David Jayatillake

Designed the architecture Quarri runs on. Each customer has its own database, its connectors run the same way on every schedule, and every answer is drawn from one model of the business.

That model is a semantic layer, the subject of two companies founded and of regular writing and speaking. The second, Delphi Labs, joined Cube, with the role of VP of AI. The conclusion from twenty years of data work: most mid-sized operators will never hire a data team.

  • Co-founder & CTOQuarri
  • VP of AICube
  • FounderDelphi Labs, which joined Cube
  • FounderAn earlier semantic layer startup
  • Data leadershipLyst and Worldpay
// 02 · Live implementations

The scale of the work so far.

Figures from our delivered work in forestry, sawmills and wood products, rounded down. Two are estimates and are marked. We don't name our customers.

2,000+

hours of manual work a year taken out across our implementations, more than one full-time person.

Across live implementations · Estimated
10,000+

trip tickets a year read from scans into structured load records, at the current weekly volume.

A timberland manager · Estimated
3.7M+

inventory records reloaded and verified.

A sawmill
15M+

board feet of finished inventory brought into reporting.

A sawmill
430,000+

tonnes of harvest, four years of daily data.

A forestry operation
80,000+

sales orders across 19 years of history.

A lumber and millwork manufacturer
22,000+

weigh records matched to bills of lading and invoices.

A forestry operation
13,000+

closed purchase orders analysed.

A lumber and millwork manufacturer
// 03 · Why the timber supply chain

The data has grown faster than the tools to use it.

Every step of the timber supply chain runs on information: what to harvest and haul, what each mill can make from the wood it receives, what to stock, and what to sell at what price. The capture side has moved quickly. What happens to the data after it is captured has not.

The timber supply chain as it runs today: forest management, sawmills, wood products and pulp, paper and packaging, each with its own systems, data and paperwork, and spreadsheets in between

As capture improves, the problem gets bigger. Each new source arrives with its own format and its own system, and every hand-off between forest, mill and customer adds more to reconcile, with no more time to do it.

The timber industry has had less enterprise software than agriculture, mining or oil and gas, and the mid-sized operators who make up most of it, from forest managers to mills and converters, cannot justify a data team of their own. That is the gap we build for.

A peer-reviewed review of 69 studies on AI in the forest products supply chain lists seven barriers to adoption. One concerns the models; three concern the data and three the organisations that hold it. Subedi, Gautam and LeBel, Forestry 99(2), 2026. Our write-up of the paper.

// 04 · How we work with an operation

Run as a change programme, with your team building.

01

A goal before a build

One goal for the business and a measure for it, such as hours moved from data entry to checking.

02

Team leads choose what comes first

Each team names the process that takes longest and the question it cannot answer today.

03

Encoded once, run the same way

Built with the people who will run it, then run on Quarri's server the same way every time.

04

Straight about cost

If your own project management will do the job, we say so. Advice while you get started is free.

How we protect your data is on our security page.