The minister isn't the one you have to convince

The minister is rarely the one you actually have to convince. That's the thing I keep saying to founders who walk in certain that the meeting which lands the file is the one with the minister. The minister signs. The program gets run, written, and graded by people most founders have never named — and that's where the file is really decided.

Behind a federal minister sit two groups doing opposite jobs. Political staff — the Chief of Staff, the Director of Policy, the sector advisors — are partisan, serve at the minister's pleasure, and control the calendar. They're the gatekeepers: they weigh whether your ask carries political risk and whether it's worth the minister's time. What they can't do is direct a department or move a program. Public servants do that. The Deputy Minister, the Assistant Deputy Ministers, the Directors General, the analysts under them — non-partisan, permanent, holding the pen. They write the memoranda, design the grant criteria, evaluate the bids. When the minister gets a recommendation, one of them wrote it.

So a founder can spend a year charming political staff, never reach the program side, and still lose. The department writes a note advising against you, and the minister defers to the people who actually understand the file. The reverse fails just as cleanly: win the analysts, skip the politics, and the file sits with nobody willing to spend capital on it. You need both rooms, and you make a different case in each. To political staff: here's why this is worth the minister's attention, and here's the riding it lands in. To the program side: here's why it pencils out, here's the production line behind the number, here's where your own criteria already point this way.

What I keep seeing is founders aim wrong twice over — too high, and too political. The reachable, decisive level isn't the minister, and it usually isn't the Deputy Minister either. It's the Assistant Deputy Minister or the Director General who owns the program. Senior enough to shape the file, junior enough to take your meeting. And you can find them by name — GEDS, the Government Electronic Directory Services, is where I'd start (confirm the current listing there; departments reorganize). Work out who runs the specific program you care about, not the department in the abstract.

Here's the part I find genuinely encouraging, because it tilts toward the founder. The official across the table from a program ADM is trying to stress-test policy against reality — that's the whole job. A hired voice reads talking points. A founder talks about the line that runs three shifts, the part shortage that moved the timeline, the jobs in a named place. When a public servant can pressure-test the policy against a real operation and get straight answers back, the conversation changes. That isn't a soft point about authenticity. It's that the person who built the business is carrying information the program side can't get any other way — and they're graded on getting it right. That's leverage you already hold and a hired voice never will.

So here's what I keep telling founders: the read is the work. Knowing who holds the pen, who guards the door, and which name three rungs down actually decides — that map is most of the game, and it's the part Bayview builds. I don't lobby, and I don't take the meeting for you. I work out who decides, build the materials to the standard the program side grades against, and tell you what to put in front of each room. You walk in as yourself and talk about your own production line, because that's the voice the whole process was built to reward — and it lands harder coming from you than from anyone I could send.

If there's a federal, provincial, or municipal program you're trying to move, book a call and I'll tell you who actually decides before you spend a single meeting. And if you want the full map across all three orders of government — the lobbying rules, the timing that locks decisions months before a budget — I wrote it all up in the full version.