# What bidding on a giga-project helideck taught me

> We priced an elevated helideck package on a giga-project with a small team and a set of agents. We submitted. Here's what the work actually felt like.

25 Sept 2026, by Ali Asif.

The tracker had 106 rows, and I was still adding to it the week before the bid closed.

Each row was a supplier or a package we needed a price for: lighting, steel, insurance, certification, installation. For the elevated helideck package on a giga-project, we'd opened conversations with a long list of firms. By the last week, six of them had signed our NDA and sent it back, and for each of those we'd staged a scope request for me to review. Only one had sent anything resembling a quote, and it was a counter-proposal asking us to define the full scope for them.

That is what pricing a multimillion-dollar package with a small team feels like. It isn't dramatic. It's a very long list, and the list wins if you don't keep hold of it.

## The pack

The tender pack ran to more than 260 files: drawings, specifications, schedules and forms. An elevated helideck isn't a single product. It's a structure, a surface, lighting, fire protection, access, markings, approvals and a design that has to satisfy several standards at once. Reading the pack properly is a job on its own.

This is where the agents earned their keep. I run 26 agent roles across Northlane and my other work, and for this bid one of them held the whole tender pack in its memory: the open questions, the drawings, the quantities. Another handled supplier sourcing. An estimator agent owned the price history, so nobody guessed a rate. They read, took off quantities, drafted the supplier requests and chased replies. I approved every price and every outbound message myself.

Doing that reading by hand with a small team would have eaten most of the schedule. The agents took the first pass.

## What I got wrong

I'd assumed the hard part would be the price. It wasn't. The hard part was keeping the chain of custody for each number: which quote it came from, when that quote expired, what scope the supplier had actually priced. In a bid that size, one line priced against the wrong scope can swallow the margin you spent weeks building.

I also underestimated how little control I'd have over the slowest supplier. The final number can only be as good as its weakest quote, and a bid is only as fast as its slowest reply.

## The result

We submitted. The result isn't mine to announce, so this note is about the work, not the outcome.

Whatever the result, I can tell you what I'd do again: keep a single supplier tracker and put every number against its source.

I can also tell you what I'd change. I'd start the supplier conversations earlier, because NDAs take time and the clock on a bid doesn't stop for them.

## Why I still bid

Losing a bid like this costs a few weeks of a small team's attention. What you keep is worth more than it looks. The supplier relationships are real, and so are the price data and the pack itself, which our estimator and the other agents now know how to read. The next helideck bid starts further along than this one did.

There's a quieter hope too: that a buyer who has seen a complete, well-organised submission remembers it. I can't prove that moves anything. It's what I tell myself on the days the answer is no, and it's a belief, not a result.

If you bid for a living, here's the one habit I'd steal. Plan the timeline around your slowest supplier, not your fastest.

Canonical: https://heyaliasif.com/writing/2026-10-13-moves-what-bidding-on-a-giga-project-helideck-taught-me