Put the Local Back into State + Local

A lot of firms treat SLED like a transaction. Find the solicitation. Drop the boilerplate. Hit submit. Wait by the inbox.

Then they lose. And they blame the price. Or the incumbent. Or the "weird" local procurement process.

It's none of that.

They lost because they forgot what the second word in "state + local" actually means.

Local is not a paperwork exercise. It's a relationship business.

Some firms run SLED like it's a vending machine. Put the proposal in, contract comes out. Everything runs through the document. The eval is the eval. Nothing personal.

SLED doesn't work that way.

A county doesn't want a vendor. It wants a partner that's going to be around. It wants someone who understands that the new water system isn't a line item... it's the thing the city council is going to get yelled at about for the next decade. It wants to know you'll pick up the phone in year three when something breaks.

That's not in the RFP. But it's absolutely in the decision.

The relationship starts way before the solicitation

The transactional firms wait for the opportunity to drop. The portal posts the RFP, you respond, the clock starts.

But by the time a SLED solicitation goes public, the agency often already knows who they want. Not because it's rigged... because the winner did the work months earlier. They went to the meetings. They understood the budget cycle. They knew the priorities before they showed up in writing.

You can't parachute in at solicitation time and out-relationship someone who's been in the room since the capital plan was a draft.

So if your SLED strategy is "set up a search alert + pounce," you don't have a strategy. You have a notification.

Okay, so how do you actually do the local work?

Glad you asked. Here's where most "go win SLED" advice taps out. Let's get specific.

Read the Capital Improvement Plan (CIP). Almost every city and county publishes a CIP... usually a five-year rolling document that lists planned projects, dollar amounts, and target years. It's public. It's on their website, often under Finance or Public Works. This is your pipeline before it's a pipeline. If a water treatment upgrade is funded for FY27, you have 18 months to get known before anything hits the procurement portal. Pull the CIP for every jurisdiction you want to work in and build your target list from it.

Watch the budget cycle. Local governments adopt budgets on a calendar you can set your watch to. Find the budget calendar (also public), and pay attention to when departments submit requests and when the council holds budget hearings. That's when priorities get decided and funded. A project that's not in the adopted budget isn't real yet... and a project that just got funded is your cue to start showing up.

Go to the meetings. Actually go. City council + county commission meetings are public, agendas are posted days ahead, and most stream or archive online. Watch the ones that touch your work. You'll hear which projects have political momentum, which ones are stuck, and which commissioner is championing what. You don't have to fly in for every session... but if a jurisdiction is a real target, get someone in the room (virtually or physically) on the meetings that matter.

Read the agendas and the minutes. Even when you can't attend, the posted agendas and approved minutes tell you what got discussed, what got tabled, and what got voted through. Minutes are a free intel feed on what the body actually cares about right now.

Set up the alerts that matter. Beyond the procurement portal, subscribe to the agency's news releases, the council agenda notifications, and the local business journal. Follow their social channels. You want to know about a project from the council discussion, not from the RFP.

Meet the people before you need them. Procurement officers, department heads, the economic development office. Many jurisdictions hold pre-solicitation industry days, vendor outreach events, or "doing business with the city" sessions. Show up. Introduce yourself. Ask what's coming. This is normal, expected, and completely allowed... it's not lobbying, it's market research.

Learn the politics, not just the org chart. Who got elected on what platform? Which council member ran on infrastructure, which one ran on fiscal restraint? Read the local paper. Follow the council members and the agency on LinkedIn. The politics tell you why a project exists and what the evaluators are actually worried about... which is exactly what your proposal needs to speak to.

Partner with someone who's already local. If you're new to a jurisdiction, a teaming partner with roots there isn't a shortcut, it's a must for credibility. Local subs, local primes, local engineers... they know the terrain and the buyers know them.

Do five of those things in a target jurisdiction and you'll know more about what's coming than the firm that's waiting for the portal to ping them.

You have to actually understand the place

This is where the transactional approach really hurts you.

The polished firms love to lead with scale. National footprint. Past performance everywhere. Big numbers.

SLED buyers care about here. Do you understand our community? Have you worked in a jurisdiction like ours? Do you get the politics, the constraints, the thing that's specific to us that the big firm with the slick deck completely missed?

A school district in central Ohio is not running a federal-style competition. The evaluator is a person who lives ten minutes from the building. The decision affects their neighbors. When you write like you're addressing a faceless contracting officer, you sound exactly like every out-of-town firm that's going to bill them and disappear.

The firms that win SLED sound like they belong there. Even when they're new to that jurisdiction.

The bottom line

SLED is closer-to-the-ground work. It rewards firms who treat proximity as the advantage, not an afterthought.

The CIP, the budget calendar, the council meetings, the industry days... none of that is hidden. It's sitting in public view while most firms wait for a notification.

Stop treating state + local like a paperwork drill. Put the local back in it.

That's where the work gets won.

‍