About
A buyer who learned to build, and now does both.
I spent 18 years buying, 12 of them on oil and gas EPC projects, and I have spent the last four building the system that corporate supply chain runs on. Same problems, different instrument. Below, the buying years first and what I build now second.
My procurement background and my computer science degree work together directly, and the degree came first. My 2003 dissertation was an information system for managing and controlling material resources at a university, the same intersection of procurement and software I work at now, twenty-three years on.
The logo says Nulla Dies Sine Linea, my motto - no day without a line. That is the same idea applied to myself. Something gets written, built or learned each day, even when it is small.
CIPS-qualified buyer
I have been a buyer since April 2004. Six years of it was on site with international groups and local companies, then twelve years as Package Responsible Buyer on oil and gas EPC projects with Kvaerner and Aker Solutions, under NORSOK standards and NIB2016 conditions. Package Responsible Buyer means I owned my packages end to end, from requirements with engineering through to close-out.
Five projects: Sakhalin-1, Edvard Grieg, Nyhamna, Njord A and Northern Lights, 82 commodity packages in all. Nyhamna was my largest scope, where I held a USD 60 million bulk procurement budget across 35 packages. I stayed to close-out on three of the five and was among the last of the team on each, and in EPC close-out is where the difficult commercial work sits. I took the CIPS Diploma in Procurement and Supply in 2014.
I have also built tools to run my own buying since my first procurement job: an orders and suppliers application in Visual Basic and Access, a multi-user version giving my group live order status on Sakhalin-1, and Excel macros controlling discrepancies across thousands of line items on Nyhamna. The CV has every project, figure and category group.
Buyer who builds web apps for buyers
A large part of the buying job was fighting systems that do not talk to each other. I had to remember what was located where, and ask colleagues where to find this and that about a supplier. So I moved into building when the need was there.
Since September 2022 I have been the sole developer of the supplier management portal at Aker Solutions, and I own it end to end: architecture, deployment, support. It holds supplier master data, qualification data, performance evaluations with the supplier's own response recorded alongside, quality records and frame agreements. It has 1,300+ registered users across the organisation's locations worldwide, 100+ of them daily, and has been live in production for four years. It is an internal system, reached only from the corporate network and never exposed to the public internet.
I start by finding where the current process creates the most friction, talk to the people who deal with that friction daily, and go from there: fix what is broken, adjust, repeat.
Nobody has to explain the domain to me. No requirements workshops, no variation orders, no six months between what a buyer described and what a developer built. I work agentically with AI tooling, which is what lets one person with domain knowledge and pre-AI development experience cover ground that used to need a team.
The point is not that the data looks better in one place. It is that a buyer sees what he would never have known to search for. Nobody goes looking for a welding non-conformance raised three years ago on another project by a colleague he has never met. Now it is there when he opens the supplier. The CV has the integrations, the security and the current Azure migration.