A real run, start to finish · October 2026

Finding Canada's naval suppliers with LoQuery

One question, ten facts per company, and a list you can check line by line. This page follows one live research run exactly as it happened, screen by screen, and explains what LoQuery is doing at each step and why it matters.

Question
Naval vendors
River-class destroyer and the Patrol Submarine Project
Discovery
20 rounds
210 pages read · 99 sources · 49 sites
Candidates
201
found and listed for review
Columns
21
from the ten criteria typed in
Discovery time
19 min
to the review list
Researched
150
all answered · 2 h 32 min start to finish
THE QUESTION

What we asked, in our own words

Canadian vendors — companies based or operating in Canada — that supply, or are positioned to supply, naval solutions, parts, systems or services to Canada's River-class destroyer programme (the Canadian Surface Combatant) or the Canadian Patrol Submarine Project: hull and structures, propulsion and power, combat systems and sensors, communications and electronics, weapons integration, training and simulation, in-service support and maintenance, and engineering services.

What to find out for each company:

  1. Company name and Canadian headquarters (city and province)
  2. What it supplies and its category (hull / propulsion / combat systems / sensors / communications / weapons / training / in-service support / engineering)
  3. Programme relevance (River-class, submarine, or both) and its role (prime, tier-1 or tier-2, potential supplier)
  4. Existing contracts or announced work on either programme: awarding body, value, date
  5. Relevant past naval and defence work
  6. Key capabilities and certifications (Controlled Goods, ISO 9001 / AS9100, clearance, in-house engineering)
  7. Company size and ownership
  8. Industrial and Technological Benefits (ITB) or Value Proposition commitments
  9. The most recent news (last 12 months) tying the company to either programme
  10. Official website and the source links used
You decide what matters.The criteria you type become the columns of the answer. LoQuery does not invent the question for you.
It searches from your browser.A small Chrome extension runs the searches and page reads on your machine, in your name.
Every answer keeps its receipt.Each filled cell points at the page it came from, so you can check it instead of trusting it.
You pay for what a run uses.The balance is shown before, during and after; the estimate is shown before you commit.
STAGE 1 OF 14

Where you start

You are signed in. Three things in the header tell you the state of your workspace: whether the browser extension is connected, your balance, and the sessions you ran before.

The signed-in LoQuery workspace: Extension Active badge, balance, the two research modes
The workspace as it opens. The small numbered dots are explained in the strip under each picture.
What you see

The header with the extension status and your balance, and the two ways to ask: name the things yourself, or describe them and let LoQuery find the matches.

What LoQuery is doing

Checking that the extension in this browser is live, because that is where the searching will happen.

Why it matters

The searches and page reads run from your own browser, not a shared scraping service. Your balance is yours to watch: a run spends from it and nothing recurs.

STAGE 2 OF 14

Telling LoQuery what you want

Two boxes carry the whole brief: the question, and the facts you want for each result. Everything else has a sensible default you can leave alone.

The research board before typing: What to discover, What to find out for each, Sites to avoid, the 20-round note, Advanced, Start
The board before anything is typed.
What you see

The two text boxes, the list of sites LoQuery keeps out of its sources when it can (Wikipedia, Reddit, social media by default), and a plain sentence about how discovery runs.

What LoQuery is doing

Nothing yet. It waits for a question. Start Research stays off until one is in.

Why it matters

"What to find out for each" is the contract: those facts become the columns of your table. The sites-to-avoid list is yours to edit.

The Advanced panel: Standard, Turbo and Economy models with prices, the discovery budget of 20 rounds, three reasoning switches
Advanced, opened. Prices are shown per million tokens and as a typical cost per research.
What you see

The model choice with its price printed beside it, the discovery budget (20 rounds, up to 300 pages), and three reasoning switches that are on by default.

Why it matters

No hidden pricing: the standard model is about $0.59 per research, the fast one about $1.22, and you can change the discovery budget before or during a run.

The board with the naval-vendor question and the ten criteria typed in
The brief, typed in. The ten criteria go in one comma-separated line.
Start Research enabled, with the note Stop any time
Ready. "Stop any time." is written under the button, and it is true throughout.
STAGE 3 OF 14

The run starts

The page splits in two: your brief stays on the left, the live run opens on the right. From here on you watch the work, and you can steer it.

The run panel appearing: Setting up, elapsed 0:05, active agent Orchestrator
Five seconds in.
What you see

A header that names the current stage, an elapsed clock and the agent at work. Below it, a board that will hold one card per company, and the steering controls.

What LoQuery is doing

Reading your question, setting the discovery budget you chose, and preparing the first searches.

Why it matters

You are never looking at a spinner. The panel says what is happening, and "Tell LoQuery in your own words" lets you redirect it in plain language while it runs.

STAGE 4 OF 14

The price, before it adds up

The Research Cost Estimate dialog: about $0.03 per item researched, the balance, Stop Research, Add credits, Got it
The cost dialog, measured on past runs.
What you see

What research costs per item (about three cents, sometimes six or more), a note that discovery itself costs money even when it finds little, your balance, and three buttons.

What LoQuery is doing

Estimating from its own past runs. The run has already begun by the time the dialog shows, and Stop Research ends it at once.

Why it matters

You see the shape of the bill before the work is done, in dollars, next to your balance.

STAGE 5 OF 14

Discovery, watched live

LoQuery turns the question into search queries, reads the pages the searches return, and pulls candidate companies out of them, round after round. You watch the list grow and you can stop it, pause it, or send it to research at any point.

Discovery, first minutes: Wave 1 broad search, 0 found, the controls and the stage bar
Ninety seconds in: the first wave is searching.
Discovery mid-run: the question as tags, the funnel of queries to pages to selected items, the found-so-far list with a remove cross per item
Round 7: 84 candidates, each with the site it came from.
What you see

How LoQuery understood the question (as tags), a funnel line that says how many queries and pages produced the list, and every candidate with its source and an × to drop it.

What LoQuery is doing

Four waves of searching: a broad search, a focused expansion, a deep dive and a last pass, up to the 20 rounds you allowed. This run used all 20 and read 210 pages across 49 sites.

Why it matters

Nothing is hidden. You can see the yards and primes arrive (Irving, Seaspan, Davie, Lockheed Martin Canada, Thales Canada, Babcock Canada, TKMS Canada, Ultra Maritime, OSI Maritime, BMT Canada, Kraken Robotics) and you can see where each came from.

STAGE 6 OF 14

What LoQuery holds back, and why

Not every name it reads becomes an item. Some are held for a second look, some are rejected with a reason, and some are left for you to decide.

Candidates not confirmed as items yet, each with Keep and Leave out buttons; the steer-this-run card
Your call: Keep or Leave out, name by name.
What you see

Names that LoQuery is not sure about, with the one-line description it found and two buttons. Below them, the steering actions you can use right now.

What LoQuery is doing

Verifying the uncertain names on its own (in this run, Gastops was held, then confirmed and added), and rejecting off-topic ones with a written reason, for example "aerospace supplier, not a naval solutions provider".

Why it matters

A rejection with a reason can be found and reversed. A guess cannot.

Sources Discovered expanded: each page read with the names it yielded
Every page read, and the names it gave. The Canadian Defence Review Top-100 page alone gave 44.
Worth knowing. That Top-100 page is a list of defence companies of every kind, and LoQuery accepted its 44 names in one pass. Aerospace and land names (Bombardier, Airbus, Bell Textron, Top Aces) came onto the list that way, and the second-pass check caught only some of them. The review step in stage 7 exists for exactly this: you decide what stays before any research is spent.
STAGE 7 OF 14

Discovery ends and waits for you

Discovery paused, waiting for you: 201 items found after 20 rounds; research starts on its own in 4 minutes unless you choose first
After the twentieth round. Nothing is researched until you say so, or four minutes pass.
The review list of the second run: all 20 rounds done, 146 found, 26 held, Keep waiting, the funnel of 26 queries to 185 pages to 146 selected, the list with a remove cross on every name
The list to review in the second run: 146 names, the funnel that produced them, and a timer you can extend.
What you see

The end message, a four-minute timer you can extend, the full candidate list with a remove control on each name, and the choice: research the list, run more discovery, or cancel.

What LoQuery is doing

Waiting. Names it could not confirm are marked "held, not checked" and research skips them unless you keep them.

Why it matters

This is the moment that keeps the thinking human: the list is yours to prune before any research money is spent on it.

Pruning the list: only what you know for sure

The first run showed why this step matters: a directory page had put aerospace and land firms on a naval list. In the second run the list was pruned by one rule: leave out only the names known for sure not to fit, and keep every uncertain one so LoQuery researches the doubt instead of you guessing it.

Not confirmed as items yet: each name with Keep and Leave out; Vard Marine kept, Med-Eng left out
Keep or Leave out, name by name. A naval designer LoQuery was unsure about is kept; a bomb-suit maker is left out.
After the edits: Seaspan Vancouver Shipyards marked added by you at the top of the list; one extra wait used
A yard added back by hand shows as "added by you". Then Proceed to Research.
Worth knowing. The translucent strip across the top of these two pictures is the run header as it was during this run; it now sits in a fixed place with a solid background, so the list beneath stays readable. Removing a name during discovery is best done once the list has stopped moving, at the review step.
STAGE 8 OF 14

The plan behind the research

Before the first page is read for any company, LoQuery writes down what it is going to do, and shows it.

The Task Plan filled in: 21 output fields derived from the ten criteria, the research strategy, field limitations, authoritative sources, the sites avoided
The Task Plan, filled in as research begins.
What you see

Your ten criteria have become 21 named columns: headquarters city and province as two, the contract's awarding body, value and date as three, recent news as a title and a date, plus a summary, the website and the source links.

What LoQuery is doing

Deciding the order it will fill the fields in, and the sources it will prefer for this topic: defence.gc.ca, the yards' and primes' own sites, navsource, SEDAR.

Why it matters

The shape of your answer is fixed and visible before the work starts. What it will not be able to fill is listed too, as field limitations.

The run board as research begins: 0 of 201 researched, nine pages of cards, each queued
One card per company, nine pages of them, all queued.
STAGE 9 OF 14

One company, end to end

Open any card and you get the whole story for that company: the answer with its receipts, how it was found, and a second opinion on the verdict.

The item workspace for ADGA Group: every field with its value and source link, or Not Found
The workspace for one company. Filled fields carry the page they came from; the rest say "Not Found".
What you see

All 21 fields for this company. Each filled one shows its value and, under it, the page it came from. Ten of the fourteen evidence fields are "Not Found" here, and the summary says plainly that no public link to either programme was found.

What LoQuery is doing

Writing down what it could prove and what it could not, instead of filling the gaps with plausible text.

Why it matters

A blank you can see is cheaper than a guess you have to catch. The verdict for this company is "uncertain", which is the right answer for a consultancy with no naval work on record.

How we got this: the third attempt's queries per field, the pages analysed and every page considered ranked by authority
"How we got this": three attempts, from precise to exhaustive, with every page weighed.
What you see

The exact search queries for each field, the pages that were read for the answer, and every page considered, ranked Authoritative, Reliable, General or Low.

What LoQuery is doing

A precision pass first, then a broader one, then an exhaustive one with site-specific searches (the company's own site, SEDAR, the contract registers), stopping when the quality bar is met or the attempts run out.

Why it matters

You can audit the method, not just the result. A separate check then reviews the verdict and states whether it agrees with the scoring rules, and the fields are checked against each other for coherence.

STAGE 10 OF 14

When a search engine pushes back

The notice: DuckDuckGo needs a human check for one search; LoQuery keeps searching with the other engines
A real interruption from this run, and what LoQuery did about it.
What you see

Which engine asked for a human check and on which search, with three choices: open and solve it, say you solved it, or dismiss it.

What LoQuery is doing

Moving that search to the engines that are not blocked and carrying on. Nothing stalls.

Why it matters

Because the searching runs from your browser, a challenge is yours to answer if you want that engine back sooner. The run does not depend on it.

STAGE 11 OF 14

The table in your columns

Table View: verdict filters, row densities, a row with score, verdict, why, caveats and a company name with its source link
Results arrive in a table whose columns are your criteria.
What you see

Filters that count the verdicts (confirmed clean, with caveats, uncertain, off-topic or rejected, failed, cancelled), three row densities, a column chooser, and rows that carry a score, a verdict, a one-line why, notes and a source link per filled cell.

What LoQuery is doing

Filling the table as each company finishes, and saving progress as it goes.

Why it matters

This is the deliverable: a supplier table you can sort, filter, check cell by cell, and hand to someone else.

Research Timeline: each company with Passed or Below the quality bar and its number of attempts
The Research Timeline: who passed the quality bar, who did not, and how many attempts each took.
Export and Generate: CSV and JSON available, PDF and API link not yet
Export: CSV for a spreadsheet, JSON with the results and every source considered. PDF and an API link are not available yet.
STAGE 12 OF 14

Honest failures

Companies that scored low or were judged off-topic are not hidden. A "things to check" panel counts them and shows them on request, each with its reason, and every low score says which fields were missing.

What you see

Partway through this run: two companies judged off-topic (zero evidence fields filled, a structural mismatch) and several marked uncertain with four or five of fourteen evidence fields found.

What you can do

Fix the verdict if you know better, re-run the flagged fields, teach a rule for the items still to come, or leave it as an honest gap.

STAGE 13 OF 14

Stop any time, and what it costs

The Stop this research dialog: items already answered stay on the board and are saved to your session history
Stopping is one click and one confirmation.
After the stop: Stopped with the elapsed time, 12 of 201 answered, Download CSV, and the off-topic cards still visible
After the stop in the first run: what finished stays, with a CSV of it.
What you see

The run marked Stopped with its elapsed time, the count of answered items, a CSV of them, and the note that any item can still be re-run from its card.

What LoQuery is doing

Closing the books: the first run's close-out recorded what the run actually used and what was charged, against the balance shown at the start.

Why it matters

Nothing you paid for disappears when you stop, and the charge is written down next to the usage.

STAGE 14 OF 14

The finished run, and coming back to it

The run researched all 150 companies kept after pruning and answered every one, 2 hours 32 minutes after it started. This is the board's own count at the end.

The finished run: Complete, 150 of 150 answered, Download CSV, and the count by verdict: confirmed clean 3, with caveats 18, uncertain with caveats 92, uncertain with no caveats 3, mismatch 29, rejected 1, good data with an off-topic verdict 3
Every company has a result, and every result is counted by its verdict.
What you see

3 confirmed clean, 18 with caveats, 95 uncertain, 29 a mismatch, 1 rejected and 3 off-topic. The rest of the board is the table itself, one card per company.

What it means

Few companies came back clean, because ten facts per company is a high bar. Cells such as Industrial and Technological Benefits commitments and programme role often read Not Found: the run did not find a page that said them, and the table says so instead of filling the gap.

Why it matters

The uncertain rows are still a lead list with receipts. Each one is a company with the facts that were found, the page each came from, and the gaps marked, ready for someone to check.

Coming back to it

Every run is saved to your sessions. Reopening one brings back the board, all 21 columns, each cell's why, notes and source links, and each company's research attempts.

A reopened company workspace: the answer field by field, each with its source link, Not Found where no page said it, and a contract value linked to its government record
A company reopened from the sessions list: the answer, field by field, each with its receipt.