Most Washington IT leaders I talk to assume the same thing: getting outside help with a Copilot or Power Platform rollout means a procurement cycle measured in quarters. A statement of work, a competitive solicitation, an evaluation committee, a protest window, and an engineer who finally shows up two budget cycles after the problem stopped being urgent.
That belief is wrong, and it is quietly the reason a lot of agencies have funded AI licenses sitting idle. You do not need a full RFP to bring in a GCC specialist. In a lot of cases you do not need a competitive bid at all. Washington’s own procurement rules build a no-bid lane for exactly this kind of work, and almost nobody on the buying side uses it on purpose.
Your Licenses Are Funded. Your Adoption Is Not. The Clock Is.
The technology fight is over. Microsoft 365 Copilot reached the Government Community Cloud (GCC) in December 2024 and GCC-High in December 2025. Researcher, Analyst, Agent Builder, and Copilot Studio publishing to Teams and Microsoft 365 went live across the gov clouds through early 2026. The compliance boundary is real, the agentic tooling is here, and the licenses are funded.
In most agencies, almost nothing about the actual work has changed. Gallup’s Q4 2025 data puts public-sector AI use at 43 percent “a few times a year,” with only about 21 percent using it daily or weekly. A MissionSquare survey of state and local employees found 46 percent using AI at work but just 17 percent daily. In one local-government survey, roughly 60 percent of staff said they had received no AI training from their employer at all. The commercial numbers are no kinder: around 40 percent of Copilot deployments stall within six months, and fewer than one in six pilots ever reaches production. The technology works. The rollout does not.
Two clocks are running on top of that. Microsoft’s government Copilot add-on carries an approximate 8 percent price increase effective July 1, 2026, so the cost of an idle license goes up whether or not anyone touches it. And OMB’s M-25-21, issued April 2025, put federal agencies on the hook for Chief AI Officers, governance boards, compliance plans, use-case inventories, and explicit workforce upskilling; state and local agencies are moving the same direction even where the memo does not bind them. “We will get to it” is now a line item with a deadline attached.
The Procurement Myth That Is Costing You the Most
Here is the reframe. The single biggest reason agencies stall on getting help is not budget and it is not policy. It is the false belief that any outside engagement automatically triggers a competitive solicitation. It does not.
Washington’s Department of Enterprise Services runs a Direct Buy policy, with the current version effective September 1, 2025, that does exactly what the name says: it lets state agencies acquire goods and services directly from a vendor with no competitive process. The thresholds are the whole point, so here they are in plain numbers.
- $10,000: any vendor, no competition, when no qualifying master contract applies.
- $13,000: when buying from a Washington microbusiness or small business as defined in RCW 39.26.010.
- $40,000 (Direct Buy Level 2): when the vendor is a Washington small business or a certified veteran-owned business.
- $50,001 to $100,000 (Direct Buy Level 3): permitted with documented due diligence showing the price is reasonable.
Read that again. A Washington state agency can engage a qualifying small business for a body of work up to $40,000 with no competitive solicitation, and up to $100,000 with light, documented due diligence. No RFP. No evaluation committee. No protest window. The lane already exists; the bottleneck is that buyers forget it is there.
Local governments operate under different statutes, so check your own bid limits, but the door is just as open. Under the sole source exemption and RCW 39.04.280, a city or county can skip competitive bidding when the governing body documents the basis, and most jurisdictions set their own direct-purchase limits well into the tens of thousands. MRSC is the canonical reference for how those exemptions apply to Washington municipalities.
If your work also touches federal dollars, the math shifted in your favor recently. The federal micro-purchase threshold rose to $15,000 and the simplified acquisition threshold to $350,000 effective October 1, 2025. Below the micro-purchase threshold, a contracting officer can buy directly. Veteran-owned small businesses without a service-disabled rating are not sole-source eligible at the federal level, but the Federal Acquisition Regulation explicitly directs prime contractors to use them as subcontractors, which is its own low-friction path onto a federal effort through an existing prime. If you want the full picture of how a Washington government GCC AI and automation specialist fits these vehicles, that is worth a longer conversation than a blog post.
What a No-Bid Engagement Actually Looks Like
None of this helps if the work does not fit under the ceiling. Most of the highest-leverage GCC AI work does, by design.
A targeted training workshop for staff who hold Copilot licenses and have no idea how the gov-cloud version actually behaves lands well under the small-business Direct Buy ceiling, and it comes out of a training budget rather than a capital line. An AI readiness assessment, a short fixed-price look at where your environment really stands before you scale, fits the same way. Even a scoped first build, two or three prioritized workflows stood up and handed off to your team with documentation, can be structured to sit inside the no-bid range instead of waiting on a year-long acquisition.
That is the path I built Puget Sound AI around, because it matches how government actually buys when it is not forced into a cycle that helps nobody. The point of a first engagement is not to lock you into a megacontract; it is to put working software in front of your people fast enough that the next decision is easy.
How to Keep a No-Bid Engagement Audit-Clean
The Direct Buy lane is not a loophole, and treating it like one is how an agency ends up explaining itself to an auditor. Keep three things in order and it stays clean.
- Document price reasonableness. A short memo comparing the quote to your experience or a rate benchmark covers the due-diligence requirement, especially at the Level 3 range.
- Capture vendor status. Record the contractor’s UEI and CAGE and note its small-business and veteran-owned status; that is the basis for the higher Direct Buy ceiling and it belongs in the file.
- Do not split the work. Repetitive purchases that quietly add up past the threshold are the one thing DES calls out by name. If the scope is genuinely going to grow into a large program, plan the competitive path for that phase rather than stacking direct buys.
An engineer who has lived inside government procurement will scope the first engagement to fit the threshold honestly, not game it. That is the difference between a clean file and a finding.
The Work That Earns the Engagement
I have spent the last several years engineering production AI and automation inside GCC environments under exactly these constraints. The kind of systems that recover orphaned and misassigned Microsoft 365 licenses through contextual inference and hand real budget back to the agency. Records classification that uses local small-language-model inference and vector retrieval to sort documents against statutory retention at a scale no human team touches. Citation-bound policy and personnel agents that answer staff questions with the source document attached, so the answer is auditable instead of a confident guess. Natural-language admin agents that turn a plain-English request into the correct Graph or PowerShell call. Reusable MCP tooling layers underneath all of it.
That is FTE-years of recoverable labor and license reclamation, built in the real cloud, not a slide deck. The capability is the point; the engagement is just the wrapper that gets it in front of your team without a six-month detour.
Why GCC Breaks the Commercial Playbook
This is where the cheap, generic help falls apart. The gov clouds are not commercial Microsoft 365 with a flag taped on. Web grounding is off by default, which is the correct posture and also why an untrained user’s first prompt feels like a letdown. Security Copilot, the tool a commercial consultant reaches for first, is not available in the US gov clouds at all. Feature parity lags commercial by months, so half the governance advice floating around the internet describes controls that have not reached your tenant yet.
And the real day-one security risk is not the model inventing things. It is oversharing. Every overshared SharePoint site, every “everyone except external users” group slapped on a library in 2019, every folder with broken inheritance nobody has looked at since, all of it was technically reachable and practically buried until Copilot showed up and started reading everything a user can see. A consultant who learned on commercial Copilot will confidently configure things that do not exist where you work. Architected to operate within Microsoft’s FedRAMP-authorized GCC boundary and aligned to NIST 800-171 and CMMC control objectives is the baseline here, not a bonus, because in this work compliance is the design rather than the afterthought.
Who You Are Actually Hiring
I am Jacob, founder of Puget Sound AI. Navy veteran, Microsoft 365 and AI engineer, and the person who scopes and builds the work rather than a sales layer standing in front of one. Puget Sound AI is a veteran-owned small business based in Puyallup, which means engaging it can support your agency’s small-business and veteran goals while fitting cleanly inside the Direct Buy thresholds above. You talk to the engineer who writes the code, every time.
If your Copilot usage reports are flat and the price increase is coming regardless, the fix is closer and cheaper than the RFP you were dreading. Start with Copilot and Power Platform training built for government environments, or book a GCC AI scoping call and we will work out exactly what fits under your no-bid ceiling and what does not.