Calgary → Phoenix Working Board
Working draft · prepared for Samantha Hay & Calgary Economic Development Evidence as of July 27, 2026
DARK HORSE WORKS Calgary → Phoenix working board
The record {{ recordCountLabel }}
Calgary → Phoenix · September 28–October 1, 2026

What would make Phoenix worth the trip for each company?

A working read of the mission and the Greater Phoenix gateway landscape, built from public materials and one intermediary conversation. Nothing here is your view yet.

The assignment may sound like

“Get meetings for the visiting companies.”

The more consequential decision may be

“Which local relationship moves each company forward, and what counts as forward?”

Our current thesis · working hypothesis

A full calendar can still be a weak mission.

The higher-value job may be to give each company a credible next step, or clear no-fit learning, through the right local gateway, without consuming partner goodwill on weak matches.

This is not a proposal or a final diagnosis. It is a prepared starting point for a better first conversation.

Where a Phoenix execution partner may help
  • {{ h }}
    •

We are not claiming to know every buyer or guarantee meetings.

Three sections, one card at a time. Confirm what is right, correct what is not, and it collects in the record for you to download. The evidence ledger sits behind every factual claim.

Some of this is wrong. You are the only one who can say which parts.

Current read→Gateway map→Bridge→Evidence
{{ spine.kicker }}

{{ spine.title }}

{{ spine.intro }}

{{ spine.sub }}

{{ spine.progress }}
reacted
{{ stepLabel }}
{{ row.label }}

{{ filterCount }}

{{ cur.num }} {{ cur.statusGlyph }} {{ cur.statusLabel }} {{ cur.meta }}

{{ cur.headline }}

{{ t.label }}

{{ cur.note }}

Your correction · on the record

{{ cur.claim }}

{{ s.label }}

{{ s.text }}
{{ b.label }}
  • {{ i }}
    •
Sources {{ s.id }} ↗ {{ cur.sourceNote }}
{{ cur.questionLabel }}

{{ cur.question }}

On the record

Nothing in this section matches that combination. That is itself worth discussing: it may mean the route runs through a city-level team, a corporate, or a relationship you already hold. .

{{ a.text }} · added
The question bank

What we would most like to learn

Take the ones that are useful and discard the rest. Typing is the slow way to answer twenty questions. If it is easier, read them aloud and record a voice memo on your phone, then send it over or play it back when we talk. We will work from what you say, not from a form.

{{ q.title }}

  1. {{ it }}
    2.
Recommended hierarchy, for discussion

Access is the means. Momentum is the mission. Corridor is the potential compounding asset.

Recommended crux · provisional

How do we route a diverse cohort to the few Phoenix relationships most likely to produce a meaningful next step, without substituting meeting volume for fit?

The first conversation should test the crux, not defend it. Where it could be wrong is card {{ cruxWrongCard }} in this section.
{{ spine.nextSection }}
The cohort · the hinge

Every route on this board starts with a company we cannot see.

The gateway map routes “a company.” The bridge begins with “define the company-level win.” Neither is real until we know who is travelling and what each one needs. This is the one artifact we would ask you for first.

What a company sheet holds

Seven lines per company. Enough to route, qualify, and know what not to book. Anything more is a form; anything less and outreach is guesswork.

  • {{ f.label }} {{ f.why }}
Worked example ▬ Illustration, not a delegate

Invented to show the shape. We have no delegate list and will not guess at one.

{{ e.label }}

{{ e.value }}

Routed on those seven lines: soft landing before buyers, so ASU AISLE and GPEC ahead of a customer meeting. Change one line and the route changes.

Start one, if it is useful

Sketch a company you already have in mind and we will route it live on the call. Or skip this entirely and send the roster in whatever form it already exists. A spreadsheet you already keep beats anything typed here.

{{ c.label }}
Until we have this

The gateway map stays a hypothesis and the bridge stays a shape. Neither can become a plan, and we would rather say so than build an itinerary on an assumption about who is in the room.
Bridge · the fourth lock

From a diverse cohort to credible next steps.

Three movements, in order. Choose the future you are actually buying. Test whether we have named the right obstacle. Then look at the path that follows if we have.

Movement one · choose the future

Which of these is closest to the mission you are trying to run?

{{ futureChoiceLabel }}
{{ f.rank }} {{ f.id }}

{{ f.title }}

{{ f.read }}

What it looks like
  • {{ l }}
    •
Risk

{{ f.risk }}

Our working hierarchy: Access is the means. Momentum is the mission. Corridor is the potential compounding asset. Access is still necessary as the operating output, and corridor value is worth capturing where it emerges, but neither should be promised before scope is known.

Movement two · test the crux

The crux is the one challenge that, if untangled, untangles the rest. Here is ours, stated once, with the four we rejected underneath.

{{ cruxStatement }}

Why this is the best current frame

It explains why the work requires more than a contact list while staying narrow enough to solve. It also generates coherent action: define the outcome, classify readiness, choose the gateway, build the relevance case, qualify the target, capture what happens next.

{{ cruxNote }}
Where this could be wrong
  • {{ w }}
    •

The first conversation should test the crux, not defend it.

The four we rejected, and why
{{ x.limitLabel }}

{{ x.limitation }}
Movement three · the path that follows

If that crux is right, a bridge could look like this.

Seven planks, each with a decision, an input, an exit condition, and the question that has to be answered before the next one starts. Open any of them.

Minimum input

{{ p.input }}

Exit condition

{{ p.exit }}

Learning gate

{{ p.gate }}

{{ p.note }}
One more question · the shape of delivery

Ten itineraries, or one room?

The planks above assume company-by-company routing. There is a different shape: bring a curated slice of the market to the cohort instead of moving the cohort through the market. It changes the economics and the risk, and it cuts against our own crux in a way worth arguing about. We cannot choose between these without the roster.

{{ shapeChoiceLabel }}

{{ sh.title }}

{{ sh.what }}

Optimizes for

{{ sh.good }}

Costs you

{{ sh.bad }}

Fits when

{{ sh.fits }}

The honest tension: if fit is the crux, a convening lowers the cost of relevance for us and raises the risk of generic relevance for them. We do not know which way that trades until we know the companies.

What we would measure, once you pick a future

A menu for later, not a scorecard for now. No numeric targets until CED defines them.

{{ m.title }}
  • {{ i }}
    •

{{ a.text }} · added
See what supports this
Gateway map · the third lock

A gateway map, not a contact list.

Route by the outcome a company needs, its sector, and its readiness. Not by name recognition. None of these organizations has been asked or has committed to participate.

{{ gwProgress }}
sorted
Start here · outcome-first routing cues

A hypothesis generator, not a routing rule. The briefs below are the evidence beneath it.

If a company primarily needs…Start by testing…Then consider…
{{ r.need }} {{ r.first }} {{ r.next }}
{{ row.label }}

{{ filterCount }}

The doors

No door in this map matches that combination. Worth discussing: the route may run through a city-level team, a corporate, or a relationship you already hold.
{{ gw.id }} {{ gw.triageLabel }}

{{ gw.name }}

{{ gw.read }}

{{ t.label }}
{{ s.label }}

{{ s.text }}
{{ b.label }}
  • {{ i }}
    •
First question to ask

{{ gw.question }}

Official sources {{ s.id }} ↗
Your read on this door

{{ a.text }} · added
Continue to the cohort
Off the spine · show the work

What supports this, and what public research cannot tell us

Every statement on the spine shows its basis and its burden. This is the ledger behind them.

Last checked · July 27, 2026

Evidence classes

{{ l.glyph }} {{ l.label }}

{{ l.long }}

Confidence labels

{{ c.label }}

{{ c.desc }}

Confidence is an editorial signal about how much weight a statement can carry into a decision. It is not a probability.

Confirmed-fact ledger

{{ f.id }}

{{ f.text }}

{{ s.id }} ↗

Official source ledger

{{ g.title }}
{{ s.id }} {{ s.title }}

{{ s.use }}

{{ s.short }} ↗

What public research cannot tell us

  1. {{ c }}
    2.

How this board should change after we talk

  • {{ a }}
    •

The board earns trust by getting more accurate, not by looking certain on day one.
Off the spine · built from your reactions

What we’ll cover when we talk

Ordered by consequence, not by the order you worked. Where you disagreed comes first: that is the most useful thing on this page. Saved in this browser only.

{{ sec.title }}

{{ sec.count }}

{{ sec.note }}

{{ r.text }}

{{ r.kind }} · {{ r.ref }}
Still open, if you want it on the agenda
Every card, in one pass

The full brief

The spine reads one card at a time. This page lays all of it out for reading offline or printing. Prepared for Samantha Hay, Calgary Economic Development. Evidence as of July 27, 2026.

{{ sec.title }}

{{ c.id }} {{ c.statusGlyph }} {{ c.statusLabel }} {{ c.meta }}

{{ c.headline }}

{{ c.claim }}

{{ s.label }}

{{ s.text }}
{{ b.label }}
  • {{ i }}
    •

{{ c.questionLabel }}: {{ c.question }}

{{ c.sourceText }}