Guest’s Blog
Is SLED Contracting Worth It for Federal Contractors? by David Fine
Over the course of a rocky FY26, every federal contractor has been hearing the same thing: diversify. Look at state and local. Stop betting the company on one buyer.
It’s good advice. It’s also incomplete, because “diversify into SLED” is not one decision. It’s a different decision for a highway contractor than for a software company, and the gap between those two cases is enormous.
So instead of arguing about it, we went and counted. What follows comes from open, live solicitations across state, local, and education buyers, the ones sitting on procurement portals and city websites this week.
How many state and local contracts are there in my NAICS code?
Start with the simplest question a contractor can ask. For every open federal opportunity in my code, how many open state and local ones are there?
Same advice, opposite outcomes, and the only thing separating them is which code you happen to work in.
Are state and local contracts smaller than federal contracts?
Yes, and by more than most people expect.
We compared the median published contract value in the same NAICS code on both sides of the fence:
A federal IT services firm accustomed to pursuing four-million-dollar computer systems design(opens in new tab) contracts will find the state and local equivalent sitting around a quarter of a million. That is a sixteen-fold difference in deal size, inside the same code, for what is often very similar work.
The gap narrows as the work gets more commoditized. Janitorial services(opens in new tab) runs less than two to one. Software publishers, under three to one. But the direction is consistent. The same capability sells for less to a city than to a federal agency.
That sounds like bad news. It isn’t, necessarily. It just means you have to be honest about what you’re buying. You are not buying a replacement revenue stream at your current deal size. You’re buying more shots, at lower stakes, with lighter competition, in a market where a small win still counts as past performance.
For a company trying to build a record rather than defend one, that trade is often worth making. For a company that needs to replace a $4M contract that just went away, it isn’t. Know which one you are before you commit a business development quarter to it.
How long do you get to respond to a state or local RFP?
Federal contractors bracing for a frantic scramble tend to be surprised here. State and local solicitations stay open a median of 29 days from posting to due date. Federal, 19.
You get about ten more days. The pressure in SLED is not the response clock. It’s everything that happens before the clock starts, which is the part nobody warns you about.
Who actually buys in the SLED market?
Ask a federal contractor to picture a SLED buyer and most describe a state agency. That’s not what the market looks like.
State governments account for under a quarter of open solicitations. Cities alone outnumber them. Add counties and K-12 school districts and you have close to sixty percent of the market sitting below the state level entirely.
This matters more than it sounds. If you’ve looked at state-level procurement and decided you know how SLED works, most of the market still looks nothing like what you saw. A city of forty thousand people might post a bid on its own website, give you a phone number, and award it in six weeks. Plenty of these buyers run a handful of solicitations a year, and the process reflects that.
How local does “local preference” actually get?
Every federal contractor eyeing SLED has heard that local preference exists. Almost nobody knows where the line gets drawn.
When a solicitation carries a local preference, it’s drawn at the city limit or the county line about two-thirds of the time. State and regional boundaries are the minority.
And the tighter the boundary, the harder the rule. Preference drawn at the city limit is roughly twice as likely to be a hard requirement, an eligibility gate rather than a scoring nudge, as preference drawn at the state line.
The practical translation: “we’re going after Texas” is not a SLED strategy. Being a known, registered, physically present vendor in three counties is a SLED strategy. The geography that matters is far smaller than most federal contractors assume, which is bad news for a spray-and-pray approach and very good news for anyone willing to pick a patch and own it.
How should a federal contractor start bidding on state and local work?
Four things, in order.
Look up your own ratio first. Before you commit any BD time, count open SLED solicitations against open federal ones in your primary code. If that number is under three, the diversification case has to be made on relationship risk, not volume.
Reset your deal-size expectations before your first pursuit, not after. Going in expecting federal contract values guarantees you’ll conclude SLED “isn’t worth it” after two bids.
Pick counties, not states. Then register as a vendor in each one, because most agencies search their own vendor database before anything gets posted.
Fix your discovery problem before your proposal problem. Your win rate is not what’s limiting you here. There is no SAM.gov for state and local work. The opportunities are scattered across tens of thousands of individual government websites, and the ones you never see cost you more than the ones you lose. You can start by pulling up the open solicitations in your own NAICS code(opens in new tab) and counting how many of those buyers you’d never heard of.
The federal contractors doing well in SLED right now aren’t better at government contracting than you are. They just did the arithmetic on their own code before they committed.
David Fine is the founder of Bidscope(opens in new tab), which tracks state, local, and education solicitations across more than 50,000 government sources and matches them to contractors by capability rather than by keyword or NAICS code. Bidscope also surfaces signals on upcoming opportunities, drawn from forecasts, published budgets, and expiring contracts.
$30 Million, One-to-One Match, Five Agencies: Inside the Strategic Breakthrough Award
More thoughts on SBIR Strategic Breakthrough Awards
I keep getting lots of questions and requests about how to get one of these $30 million Strategic Breakthrough (SB) awards.
Well first, let’s break it down a few very pertinent facts:
SB awards are ONLY authorized (by PL 119-83) at the following SBIR agencies: DOD (DOW), HHS, NSF, DOE and NASA. None of the other SBIR agencies can even consider SB awards.
SB awards are FOLLOW-ON Phase II awards (based on the previously implemented Air Force STRATFI program). This means to be eligible, a company must already have an SBIR/STTR Phase II award.
Before finalizing an SB award, an eligible company must show evidence of a 1:1 match of the proposed award amount.
An SB award will come from the awarding agency SBIR budget. That is, PL 119-83 did not appropriate any new funds for SB awards, it simply allows SBIR dollars to be spent via SB without requesting permission.
MY THOUGHTS… (not facts!)
NIH & NSF have said they would likely use the new SB authority to expand their existing Phase IIB awards on a case by case basis. But both expected that IF they used the new SB authority, the award sizes would be more like < $5 million, not close to the $30 million maximum.
My personal view is that only the largest DOD components (AF, Navy, Army, MDA) will entertain anything near the $30 million maximum. Any SB award nearing $30 million would simply chew up too much of the overall SBIR budgets. Keep in mind that one $30 million award would be more than 10% of the individual NSF, NASA & DOE annual SBIR budgets.
So what should you do?
The four requirements will likely filter out most of those interested in pursuing an SB award.
If your firm DOES meet all the requirements above, then it is in your best interest to talk with your agency program staff to inquire how to pursue these larger awards.
Final thought:
This new authority gives the 5 agencies listed additional flexibility on how to use SBIR budgets to further their agency mission. I LIKE this new authority!! However, actual implementation of the authority will likely be limited in both scope (which agencies actually use the SB authority) and scale (the actual dollar amount of any resulting SB awards).
Connect with Jerry Hollister
BBCetc Website: https://bbcetc.com/
Additional Resources:
Public Law 119-83 DSIP (Defense SBIR/STTR Innovation Portal): https://www.congress.gov/119/plaws/publ83/PLAW-119publ83.pdf
SBA FAST Program: https://www.sbir.gov/community/fast
The Pilot Trap: Why Most Government Innovation Never Ships and How to Fix It By Bryon Kroger, Founder & CEO, Rise8
The Pilot Trap: Why Most Government Innovation Never Ships and How to Fix It
By Bryon Kroger, Founder & CEO, Rise8
Across government, agencies enthusiastically launch innovation labs, software factories, AI task forces, and modernization initiatives. Many generate headlines. Some even produce impressive demos. But very few make the leap from pilot to production to drive mission impact.
The main culprits? An abundance of bureaucracy and modernization efforts optimized for legacy processes instead of outcomes.
I learned this lesson firsthand when I got assigned to Air Force Lifecycle Management Center, and spent every day fighting it as I stood up and scaled Kessel Run, the U.S. Air Force’s software factory. We were trying to solve real operational problems for Warfighters using modern software delivery practices. What became immediately obvious was that the hardest part wasn’t building software, but navigating an ecosystem designed to prevent rapid deployment and direct user feedback.
That type of ecosystem creates what I call the “pilot trap.”
A team receives funding to experiment. They build a prototype. Stakeholders praise the innovation. Shiny slide decks present metrics. Maybe there’s even a successful demo day.
But somewhere between the prototype and production, momentum dies. The feedback loops slow, governance layers multiply, and delivery timelines stretch from days to months, sometimes years.
The pilot becomes another stranded artifact of a system that rewards activity over impact. The once promising concept suffers the same fate as too many other government software programs: gone before it sees the light of day.
Two things drive it, and you can fix both.
Bureaucracy Slows Delivery to a Crawl
Over decades, agencies have accumulated layers of oversight, governance, reporting structures, and procedural safeguards. Individually, many of these processes appear reasonable. Collectively, they create a nearly impenetrable software delivery environment, one where even small changes can take months to approve and deploy.
Modern software development depends on speed, iteration, and rapid feedback, while legacy bureaucratic systems optimize for control and process. This mismatch sits at the center of digital transformation.
The result is that many innovation programs get trapped in procedural quicksand before they ever reach operational scale.
I experienced this after transitioning from intelligence operations into acquisitions and helping launch Kessel Run. The technical challenges were rarely the hardest part. The real challenge was establishing continuous software delivery inside an ecosystem built around sequential approvals and risk avoidance.
The system wasn’t built for the Department of War’s desire to speed software delivery. And that same system is still in place.
Access to Users is Limited or Non-existent
Even software that makes it out of the pilot phase is often doomed once deployed because the people who build solutions are often separated from the people using them. Contractors and developers receive requirements through multiple layers of intermediaries, including committees, oversight offices, acquisition teams, and proxy users who may be far removed from operational reality.
As a result, teams design for alignment with those intermediaries instead of for the operator. Added features satisfy governance bodies and requirements expand to accommodate competing interests until the product is solving for consensus over usability.
I watched what losing that user connection costs. At Kessel Run, I dedicated a large part of our budget to putting our developers and product managers on site with operators, sitting next to the people who would actually use the software. After I left, the various stakeholders decided the travel budget was too high and cut it. That severed the connection with the users. The user-centered design we had built our reputation on collapsed because you cannot design for people you never see.
Designing for consensus instead of the operator is one of the core reasons so many pilots never reach production. The pilot succeeds in a controlled environment with limited expectations and manageable scrutiny. Once a program starts to scale, layers of oversight and competing priorities accumulate around it. The product slowly shifts away from solving user problems and toward satisfying institutional processes, and eventually it fails.
Continuous Delivery is the Key to Solving the Pilot Trap
Continuous software delivery offers a way out of the pilot trap. It shortens the distance between an idea and operational feedback, letting teams validate assumptions in real environments rather than debating hypotheticals in conference rooms.
When deployments happen multiple times per day instead of once every few months, feedback loops accelerate. Teams stop optimizing for approvals and start optimizing for outcomes. Risk gets smaller and easier to manage because changes are incremental.
Most importantly, continuous delivery puts teams back in proximity to the mission. Continuously shipping software only creates value if teams are learning directly from the people using the system. Otherwise, you just produce bad software faster.
The best software teams sit with users, watch them work in their real environment, then iterate on what they see. The closer teams stay to users, the smoother delivery gets because decisions are grounded in operational reality instead of assumptions.
Success Beyond the Pilot Phase
Getting to production isn’t the finish line. The real measure is what happens after deployment. Did users complete workflows faster? Did the software reduce their cognitive load and give them a real mission advantage? Did decision-making improve? Answering these questions tells you whether a capability is producing mission outcomes or adding another layer of complexity to an already overloaded system.
The way I measure this is net value release. If a change provides net value to the mission, ship it. That sounds obvious, but I have watched people refuse to release software that cut an operator’s workflow by 80 percent because it added one manual step that didn’t meet some checklist definition of “done.” Net value to the mission is the bar. Not process compliance.
And here is the part most modernization efforts get backwards: you don’t fix this by deciding to change the culture. You change behavior first. Establish continuous delivery, get teams shipping to real users, and the attitudes and the culture follow. Try it the other way around and nothing moves.
Our flagship education event, Prodacity, is built around this shift. It exists to have honest conversations about what it actually takes to ship software into production inside complex government environments.
Getting out of the pilot trap is just step one. What we ship, and whether it drives mission impact when it matters most, will decide the future of government modernization.
RESOURCES:
Rise8: https://www.rise8.us/
Prodacity 2026: https://www.rise8.us/prodacity/about
Navigating the New Federal Landscape: A Small Business Strategy Built on Four Critical Pillars by Kevin Plexico
The U.S. federal contracting landscape is experiencing seismic shifts. The Trump 2.0 administration has fundamentally reshaped the market, creating a stark divide between agencies poised for significant growth—DHS, VA, and DOD—and those facing potential budget cuts or even elimination, like Education, EPA, and other social service agencies. At the same time, GSA has gained sweeping new authority to drive federal purchasing toward category management and consolidated contract vehicles, while major FAR overhauls introduce changing compliance requirements alongside new regulations like CMMC and revised small business policies.
For small businesses, this convergence of forces demands strategic clarity. Scattered approaches won’t survive this environment. Success requires a disciplined framework built on four pillars that we call the 4 Cs: Capabilities, Customers, Contract Vehicles, and Compliance. Master all four, and you position yourself to thrive. Fall short in any area, and you risk striking out before you ever get to compete.
The First C: Capabilities
What unique, differentiated value does your company actually deliver? You’ll need to be able to articulate a defensible competitive position that resonates with agency missions and pain points.
Your capabilities must be clear enough to explain in a conversation and backed by concrete evidence. Do you have past performance data demonstrating results? Can you point to metrics, case studies, or customer testimonials that validate your claims? Most importantly, are your differentiators meaningful to agencies, or just different for the sake of being different?
In a market where some agencies face existential questions and others are flooded with new demands, generic capabilities won’t cut it. Agencies need specialized expertise that solves real problems. If you can’t clearly define what makes you different and why it matters, you’ll struggle to stand out in an already competitive field.
The Second C: Customers
Strategic targeting is paramount for a small business in a huge market. Rather than chasing every opportunity, small businesses must identify specific agencies and prime contractors whose missions and needs align with their capabilities. This means doing your homework:
- Which agencies are growing?
- Where is budget flowing?
- Which customers have problems you’re uniquely positioned to solve?
But identification is only the beginning. You need an engagement strategy. How will you get in front of decision-makers? What industry days, conferences, or capability briefings should be on your calendar? Who are the program managers, contracting officers, and prime contractors you need to build relationships with?
In today’s market, intentionality matters. Don’t waste resources pursuing agencies facing budget cuts when your capabilities are valued at growing agencies. Don’t pitch services to customers who prefer to buy those capabilities through established primes. Focus your limited time and resources on customers where you have a genuine competitive advantage and a realistic path to contract awards.
The Third C: Contract Vehicles
Here’s where GSA’s expanded authority becomes critical. As agencies are steered toward existing IDIQ contracts and consolidated vehicles, access to the right contract mechanisms is rapidly becoming table stakes.
Small businesses aspiring to prime contracts must take inventory. Which vehicles are your target customers using today? Which vehicles will they be directed to use tomorrow? Once you understand the landscape, you need a realistic strategy for positioning yourself—ideally as a prime contractor holder for services companies, or as a strategic teaming partner for primes who hold these vehicles.
As ad-hoc procurement opportunities get redirected to established vehicles and agencies consolidate spending through preferred vehicles, being shut out of key IDIQs means being shut out of entire markets. If your target agencies can only purchase through vehicles you’re not on, your capabilities and customer relationships become irrelevant. You’re sidelined before the competition even begins.
The time to act is now. Identify vehicle opportunities, build your pursuit strategy, and invest in positioning yourself for the next generation of contract mechanisms that will define agency buying patterns. This will require investment in compliance.
The Fourth C: Compliance
Agencies are sending a clear message through their solicitation requirements: they prefer contractors who can navigate federal regulations seamlessly. Increasingly, RFPs award evaluation points for—or outright require—approved business systems, ISO or CMMI certifications, and cybersecurity compliance capabilities like CMMC.
For small businesses, compliance infrastructure is a valuable strategic asset. Companies with DCAA-approved accounting systems, DCMA-approved purchasing systems, and mature cybersecurity postures win contracts. Those without these credentials struggle to compete for prime opportunities, regardless of their technical capabilities.
The bar is rising. What was once a nice-to-have is becoming mandatory for serious prime contractors. Small businesses that view compliance as a checkbox activity rather than a competitive differentiator will find themselves locked out of high-value opportunities. Those that invest strategically in compliance maturity open doors to contracts their competitors can’t even bid on.
Small Businesses Must Master All Four Cs Or Strike Out
The federal contracting market has never been more dynamic or more demanding. With fewer opportunities in shrinking agencies, higher stakes in growing ones, and increased competition across the board, there’s no room for weakness in your strategy.
The 4 Cs are interconnected pillars that must all stand strong to support your strategy. Excellent capabilities mean nothing if you’re targeting the wrong customers. The right customers won’t help if you lack access to their preferred contract vehicles. And even perfect alignment on capabilities, customers, and vehicles falls apart if you can’t meet agency compliance requirements.
Small businesses that build strategies tightly focused on executing across all four dimensions don’t just survive this market transformation—they thrive in it. They win contracts while competitors wonder what happened. They build sustainable businesses while others chase one-off opportunities.
In federal contracting, close isn’t good enough. You need a successful strategy at every stage. The question is: will you master the 4 Cs, or will you strike out in the new era of government contracting?
Why is Strategic Pricing So Important to a Bid by Marsha Lindquist
Why is Strategic Pricing(R) so important to a bid?
Most contractors approach Strategic Pricing(R) like it is an afterthought. It is not if you want to win. Plain and simple there can be nothing more important to a proposal than the pricing. Because pricing too often is a deciding factor in a win, (even if it is low price technically acceptable) it makes sense that it should take center stage. Rather than the approach which too many contractors take “Now that we have finished the technical response, let’s get the pricing done,” choose to do what makes sense. Get a Strategic Pricing(R) approach as part of the capture process.
Strategic Pricing(R) Plan
We often hear that a contractor must win an opportunity. However, the focus on developing a Strategic Pricing(R) plan is left to the end and without much thought about what will get the price to the right target. If money is everything to a bid, and it is, then devote your attention to your Strategic Pricing(R). To think money is not important is foolhardy. What is your process for establishing Strategic Pricing(R) in your organization? Here are the three most important Strategic Pricing(R) processes.
Strategic Pricing(R) Processes
First, start early. Engage the pricing team in the capture stage. That means you start your Strategic Pricing(R) planning and actions before the RFP comes out. Otherwise, you began too late.
Second, engage the entire pricing team. This includes pricing specialists, outside consulting for the price to win, competitive assessment, and pricing strategists, along with the finance and accounting staff, capture team, proposal team, human resources, and procurement – add these people to the executive management team to bring in the importance of pricing to the forefront.
Third, begin assessing the deliberate choices you have to consider and the long lead items necessary to dig into the details. Be generous in choosing all the elements necessary to make an informed decision.
If you do just these three actions, you will be ahead of your competition.
Resources:
LinkedIn: https://www.linkedin.com/in/marshalindquist1/
LinkedIn Corporate: https://www.linkedin.com/company/granite-leadership-strategies/?viewAsMember=true
Serving Without the Uniform: How Trust, Credibility, and Focus Drive Success in GovCon by Larry Pokroy
Summary
This episode of GovCon Unscripted offers a candid, practitioner-level examination of what it truly means to transition from military service into government contracting leadership—and how to grow responsibly, credibly, and sustainably without relying on rank, title, or pedigree. Rather than focusing on surface-level GovCon tactics, the discussion centers on mindset, reputation, relationships, and disciplined differentiation as the core drivers of long-term success.
The central message is: service does not end with the end of the uniform—it evolves. In GovCon, impact is no longer command-driven; it is trust-driven. Leaders who understand this shift—and operationalize it—are better positioned to build durable pipelines, credible partnerships, and organizations that win and perform with competence and integrity.
1. Transition Is an Internal Shift, Not a Resume Exercise
A key insight from the discussion is that the hardest part of transitioning from uniformed service into GovCon is not learning acquisition terminology or building a civilian resume—it is recalibrating how influence and authority work.
• In the military, authority is institutional and hierarchical.
• In GovCon, authority is informal, reputation-based, and earned over time.
Leaders who fail to make this shift often struggle early, assuming proximity to mission or prior service alone will translate into trust. The podcast reinforces that credibility in GovCon must be demonstrated repeatedly through judgment, consistency, and delivery—not inherited from prior roles.
2. The Critical Mindset Shift: From Command to Credibility
The conversation emphasizes that GovCon success is governed by a different operating system. Results are shaped less by direction and more by how leaders show up across long sales cycles, uncertain procurements, and complex partner ecosystems.
Key mindset shifts highlighted include:
• Playing the long game rather than chasing short-term wins
• Viewing reputation as a strategic asset
• Understanding that every interaction contributes to—or erodes—future trust
This shift is particularly important for growth-stage companies, where impatience can drive poor pursuit decisions and credibility damage.
3. Relationships Are Infrastructure, Not Networking
One of the most operationally relevant insights is the reframing of relationships as core GovCon infrastructure, not social activity.
Effective relationships:
• Provide early market intelligence
• Clarify customer intent behind solicitation language
• Enable smarter teaming and pursuit decisions
• Reduce execution and capture risk
The podcast draws a clear distinction between superficial visibility and being genuinely useful. Leaders who consistently add value—by sharing insight, connecting partners, or helping others solve real problems—become trusted long before any RFP is released.
4. The Overselling Trap: A Too Common Growth Failure Mode
The discussion directly addresses why small and mid-sized firms often oversell—and why it backfires.
Overselling typically manifests as:
• Claiming broad capability instead of demonstrated depth
• Leading with intent rather than evidence
• Presenting “we can” instead of “we have done, repeatedly”
The insight here is pragmatic: government buyers are evaluating risk, not enthusiasm. Overstated claims signal execution risk and erode trust. Firms that win consistently do not try to be everything—they are clear, precise, and evidence-driven in how they present value.
5. Differentiation Requires Focus, Not Breadth
The episode reinforces that in GovCon, capability is baseline. Differentiation comes from specificity.
True differentiation includes:
• A defined customer problem set
• Repeatable outcomes and proof points
• Clear alignment to acquisition risk reduction
Rather than limiting opportunity, a well-defined niche increases win probability, improves partner alignment, and strengthens credibility with customers who value predictability and performance over promises.
6. Continuing to Serve Without the Uniform
The closing theme brings the discussion full circle: service continues after uniformed service. The roles have changed, but the values remain—it just takes a different form.
Purpose-driven leaders:
• Prioritize integrity over expediency
• Protect reputation as a long-term asset
• Build cultures that perform consistently
In GovCon, this translates directly into recompetes, referrals, partner trust, and sustained growth. Service becomes a multiplier for execution discipline, not just a personal value statement.
Takeaways
For senior leaders, BD executives, and GovCon practitioners, the episode delivers five clear lessons:
1. Transition success is driven by mindset, not mechanics.
2. Reputation and trust are the primary currencies of GovCon.
3. Relationships function as strategic infrastructure.
4. Overselling destroys credibility faster than saying “no.”
5. Focused differentiation outperforms generalized capability.
Bottom Line:
Winning in GovCon is less about how you claim capability—and more about how consistently you demonstrate value, competence, judgment, and integrity, over time. Here are high-value links and resources that expand on the themes from “Serving Without the Uniform: Transition and Growth in GovCon,” especially around veteran transition, GovCon business development, relationships, and credibility.
Resources:
Podcast & Media on GovCon, Transition, and Leadership
1. GovCon Unscripted Podcast (Chelsea Roberts)
Access episodes on GovCon transition, leadership, and growth—including the Larry Pokroy episode highlighted.
Resource: GovCon Unscripted — Series page (episodes, show notes, platforms) (RedCircle)
2. GovCon Giants Podcast — Veteran Success in GovCon
Podcast episode discussing strategies for veteran success in business and federal projects. (Steerbridge)
Search for “GovCon Giants Podcast Episode 224 Strategies for Veteran Success” on your podcast platform
3. GovCon Mindset YouTube — Veteran Support & Resources
Video discussing resources and mindset for veterans transitioning into procurement roles in GovCon. (YouTube)
YouTube search: “GovCon Mindset EP: Veteran Support and Resources.”
________________________________________
Transition Resources (Veteran-Focused)
4. Transition Assistance Program (TAP)
Official DoD program offering structured support, training, and tools for military-to-civilian transition. (Wikipedia)
5. NVBDC (National Veteran Small Business Coalition) Resources
Guides and programs for veteran business owners in government contracting, including growth, networking, and certification tips. (NVSBC)
6. Hiring Our Heroes — Military Transition Reading List
A curated professional reading list covering job search, skill translation, workplace adaptation, leadership, and career development. (Hiring Our Heroes)
7. How To Speak Civilian Fluently (Veteran Communication Guide)
Book/pdf focused on adapting military communication skills to civilian business language—useful for leadership and business development. (Vets2PM)
Search “How To Speak Civilian Fluently And Prove It with Your CM Credential”
8. Justin Constantine — Veteran Hiring and Transition Leadership
Author and consultant whose work focuses on veteran transition, thriving in civilian workplaces, and leadership translation. (Wikipedia)
Search “Justin Constantine From We Will to At Will”
________________________________________
GovCon Business Development, Strategy & Relationships
9. Business Development Lifecycle in GovCon
Guide explaining structured BD processes for government contracting—aligned to early engagement and relationship building. (GovDash)
10. GovCon Chamber — 10 Tips for Government Contracting Growth
Blog post with tactical networking, positioning, profiling, and teaming insights to grow in the federal marketplace. (GovCon Chamber)
11. Deltek’s GovCon Growth Strategies
Insight into technology, compliance readiness, and strategic planning for small and mid-sized government contractors. (Deltek)
12. Government Contracting Strategy & Market Trends (GrowFedBiz)
Analysis of the GovCon landscape including relationship building, strategic adaptation to policy shifts, and emerging opportunities. (Grow Fed Biz)
________________________________________
Formal GovCon Procurement Knowledge
13. Federal Acquisition Regulation (FAR)
The foundational set of procurement rules governing federal contracting — essential for credibility and compliance. (Wikipedia)
________________________________________
Additional Leadership & Transition Insight
14. What Color Is Your Parachute?
Classic career transition book with strategies on modern job searches, networking, and skill translation (recommended for all transitioning professionals).
Search for the latest edition of What Color Is Your Parachute?
15. “Radical Candor” by Kim Scott
Leadership and communication insights relevant to veterans adapting to civilian business culture.
Search “Radical Candor Kim Scott”
Federal Quality Control Requirements by Renee Glendenning
Federal Quality Control Requirements—and How They Can Impact Your Bottom Line
Every Federal construction project comes with Quality Control (QC) requirements. They are not optional, and they are not administrative formalities. Yet, time and again, contractors underestimate their scope, their rigor, and most importantly their impact on profitability.
When Federal QC requirements are misunderstood, poorly implemented, or treated as a paperwork exercise, they frequently become a direct threat to a contractor’s bottom line. Rework, delayed inspections, withheld payments, extended closeout periods, and strained relationships with Federal clients are all common outcomes of weak QC execution.
To succeed on Federal work, contractors must understand that Quality Control is not just about submittals. It is a comprehensive, contract-driven system that governs how work is planned, executed, inspected, documented, tested, commissioned, and closed out.
Federal Projects Always Include Quality Control Requirements
Every Federal Request for Proposal (RFP) includes explicit Quality Control requirements. These requirements may be outlined in the specifications, special contract requirements, or referenced standards such as USACE EM 385, NAVFAC guidance, or agency-specific QC manuals.
Too often, contractors focus heavily on scope, schedule, and pricing—while skimming over the QC section of the RFP. This is a costly mistake.
Federal QC requirements dictate:
- How inspections must be conducted
- What documentation must be generated and submitted
- How deficiencies are tracked and corrected
- How testing and commissioning are managed
- How closeout is executed and accepted
Failure to comply does not simply result in corrective action—it often results in lost time, lost money, delayed payment, and lost reputation.
Quality Control Failures Are Profit Killers
Federal clients are unforgiving when it comes to QC compliance. If inspections are missed, documentation is incomplete, or procedures are not followed exactly as required by the contract, the consequences are immediate and measurable.
Common profit impacts include:
- Rework at the contractor’s expense
- Failed inspections that halt progress
- Extended project durations
- Withheld retainage on progress payments
- Delayed final acceptance and closeout
- Increased administrative burden and staff burnout
In many cases, contractors do not lose money because the work was poorly performed but because quality was not properly managed or documented.
Quality Control Is More Than Submittals
One of the most persistent misconceptions in Federal construction is that Quality Control equals submittals.
Submittals are only one small piece of the QC program.
True Quality Control includes:
- Daily QC inspections and reports
- Three-phase control (preparatory, initial, follow-up)
- Definable feature of work (DFOW) planning
- Coordination of testing agencies
- Tracking and resolution of deficiencies
- Startup and commissioning support
- Closeout documentation and final acceptance
When QC is treated as a clerical function rather than an operational system, projects suffer especially during the last 10%.
The Limitations of the USACE CQCM Course
Many contractors rely solely on the USACE Construction Quality Management (CQCM) course and assume it fully prepares their team to execute QC on Federal projects.
This assumption is flawed.
While the CQCM course is a mandatory requirement for USACE projects, it serves a very specific purpose. It explains:
- The difference between Quality Control (QC) and Quality Assurance (QA)
- The government’s expectations at a high level
- The roles and responsibilities defined by the Corps of Engineers
What it does not teach is how to actually run a QC program day to day.
The CQCM course does not train your team on:
- Daily QC task execution
- Managing inspections and testing workflows
- Coordinating commissioning activities
- Driving closeout efficiently
- Standardizing QC practices across projects
In short, it provides a 1,000-foot overview—not the operational playbook your team needs in the field.
Why Your Entire Site Team Needs Federal QC Training
Another costly mistake contractors make is limiting QC knowledge to a single individual—the QC Manager.
Federal Quality Control is not a one-person job.
Project Managers, Superintendents, Project Engineers, Foremen, and administrative staff all influence QC outcomes. When only one person understands the QC requirements, bottlenecks form, information is missed, and mistakes multiply.
Training your entire site team on Federal QC requirements ensures:
- Consistent documentation practices
- Early identification of issues
- Clear understanding of inspection and testing requirements
- Better coordination with Federal QA representatives
- Faster startup, commissioning, and closeout
Most importantly, it protects your margin by preventing problems before they escalate.
Quality Control From Cradle to Grave
To protect your bottom line on Federal projects, your team must understand Quality Control from cradle to grave—from preconstruction planning through final pay application submission.
This includes:
- Reading and interpreting QC requirements in the RFP
- Developing and executing the QC plan
- Managing daily QC activities
- Supporting commissioning and testing
- Driving closeout so final payment is submitted on turnover day—not months later
Without this end-to-end understanding, even well-built projects can turn into financial losses.
A Standardized Approach Is the Only Sustainable Solution
One-off training, informal mentoring, and “learning on the job” are not sustainable strategies for Federal QC success.
A standardized, repeatable QC training program:
- Reduces risk across all Federal projects
- Ensures consistency regardless of personnel changes
- Accelerates onboarding for new hires
- Improves project outcomes and client satisfaction
Our lifetime-access online Quality Control training program was designed to meet this exact need.
With one purchase, your organization gains:
- Comprehensive Federal QC training
- Standardized forms, templates, and logs
- Practical guidance for daily QC execution
- A consistent QC approach across all projects
- Training access for current and future employees
Rather than reinventing the wheel on every Federal job, your team operates from a unified QC framework that protects profitability and performance.
Conclusion
Federal Quality Control requirements are not just contractual obligations they are financial risk factors. When misunderstood or poorly executed, they erode profit, delay payment, and damage reputations.
Contractors who succeed on Federal work understand that QC is operational, not administrative and that proper training is the difference between controlled outcomes and costly surprises.
If you want to protect your bottom line, your team must understand Federal Quality Control requirements from start to finish and be equipped with the tools, training, and systems to execute them correctly every time.
Mission Before Margin: Why One Bent Bolt Matters by Katie Bigelow
The bolt was only slightly bent. Barely noticeable, unless you knew exactly what you were looking for. On any other production line, it might have slipped through, become someone else’s problem, and never been traced back to where the decision was made.
In the review, one experienced team member shrugged and said what many in manufacturing have heard: “The soldiers will find a replacement in the field.” The room went quiet. People shifted on their feet. No one wanted to say the real question out loud, but everyone was thinking it: “Should they have to?”
That one bent bolt forced a choice. Do we stop the line and pull on the thread, or convince ourselves it is an isolated defect and keep moving? We had thousands of these assemblies at different stages—some at fab, some getting plated, some in paint. We did not know, beyond a shadow of a doubt, whether this bent bolt was the only one. The next questions came fast and ugly: How much will this cost? What will this do to schedule?
The decision at Mettle Ops was simple, but it was not easy: stop everything. Stop the line, find every suspect part, fix the problem, and then figure out how to save the schedule and absorb the financial hit. Warfighter first, without qualifiers.
That moment was not about a bolt. It was about what kind of company we are—and what kind of industry we want GovCon to be.
Operating Principle 1: Warfighters Serving Warfighters
Mettle Ops was built by people who have been on the receiving end of those “someone else will fix it” decisions. Many of us were soldiers in the field, literally searching for the proverbial missing bolt so a vehicle could roll, a mission could launch, or a wounded soldier could be moved. We remember the maintenance bay at 2 a.m., the cannibalized parts, and the quiet anger of knowing that somewhere upstream, a shortcut was treated as acceptable because “it’s good enough.”
“Warfighters Serving Warfighters” is not branding for us. It is an operating principle. It means:
· Every decision is made with a mental image of the person downrange who will depend on what we build.
· “Acceptable risk” is evaluated in terms of lives and mission, not just in terms of contract clauses and cost-plus margins.
· If something is within our power to fix now, we do not push it forward hoping the soldier will improvise around our choice later.
In the bent-bolt scenario, that principle made the decision clear. We had lived the reality of being the soldier who has to “find a replacement in the field.” If we can prevent that, we will—no matter how much rework it takes.
GovCon often talks about “supporting the warfighter,” but there is a difference between saying it in a proposal and operationalizing it in a factory, engineering lab, or program office. The test is whether the mission still comes first when it costs you money, forces you to call a customer with bad news, or jeopardizes your quarterly numbers.
Operating Principle 2: Resourcefulness Over Shortcuts
Stopping the line is the dramatic part of the story, but it is not the end. After “stop everything,” the next step has to be “and now we figure it out.”
Resourcefulness is how “mission before margin” becomes sustainable instead of reckless. At Mettle Ops, being resourceful means trusting that our team can solve the financial and schedule impact of doing the right thing.
When we halted production for that bent bolt, we immediately went to work on questions like:
· Where else can we pull cost out of this program without affecting safety or quality?
· How can we tighten internal cycle times to buy back schedule?
· What work can we parallelize or re-sequence to keep other progress moving while we correct the defect?
This is where scrappiness becomes a competitive advantage. Our team is used to solving complex engineering and integration problems under tight constraints, so we apply that same creativity to business constraints. Instead of asking, “Can we afford to fix this?” the better question is, “How do we afford to fix this?”
In practice, that might look like renegotiating noncritical elements, leaning harder on internal efficiencies, or taking a short-term margin hit on one contract while preserving long-term trust and opportunity with the customer. It is not comfortable, but it is doable—if
you decide up front that integrity is non-negotiable and resourcefulness is your response, not shortcuts.
Operating Principle 3: Transparency Builds Real Trust
The third principle is transparency—inside the company and with customers and suppliers. Trust is not built by pretending everything is fine; it is built by telling the truth quickly and then showing how you plan to fix it.
In the bent-bolt situation, transparency required several uncomfortable actions:
· Admitting internally that we had a problem large enough to stop production.
· Communicating the issue to our customer before they discovered it downstream.
· Bringing suppliers into the conversation to identify root causes and prevent a repeat.
Those conversations are never fun, but they are exactly where trust is earned. Customers in GovCon have seen plenty of vendors hide, deflect, or slow-roll issues until it is too late to respond without major disruption. When you show up early, lay out the facts, and present a plan, you separate yourself from that noise.
Transparency also protects culture. Teams notice how leaders respond under pressure. If leadership hides issues or quietly ships “good enough” product, the message is clear: short-term comfort beats long-term integrity. If leadership stops the line, owns the problem, and invites the team into the solution, the message is very different: this is a place where doing the right thing matters more than saving face.
The Real Competitive Advantage: We Were There
In a GovCon market crowded with slick websites, big promises, and pressure to grow at any cost, “we are real, we are trustworthy, we were there” is not a slogan—it is strategy.
Being “there” means carrying Army aviation experiences, deployment memories, and years of fielded systems into every design review, risk assessment, and production decision. It means remembering that behind every contract number is a formation of soldiers who will live with the consequences long after the period of performance ends.
Leading with integrity does not mean ignoring profit or schedule. It means refusing to let them sit in the decision-making chair. Profit and schedule are constraints to be managed;
the warfighter is the reason the company exists. When that order of priority is clear, decisions about bent bolts—and everything else—come into focus much faster.
Mission before margin is not free. It will cost you time, money, and a few uncomfortable phone calls. But in GovCon, where most companies lose more bids than they win and trust is the only real differentiator, there is no better competitive advantage than being the partner who can be counted on when no one is looking.
The bolt was bent, just a little. We stopped everything anyway. Because somewhere, a warfighter will depend on that assembly in a moment that cannot be rescheduled, and that is the only calculus that matters.
Reinventing Your Career After Government Service By Melinda Milheim
(Your federal career isn’t the finish line — it’s the launchpad)
After years in federal service — military or civilian — it can feel like your career path is carved in stone. Step outside, and suddenly it feels like starting from scratch. Many federal employees ask, “Will my skills translate to industry?”
The answer: absolutely.
Your federal career isn’t the end of your story — it’s the foundation of your next one. Think of this transition not as “starting over,” but as building on everything you already know to create your next chapter. Reinvention isn’t about abandoning your experience. It’s about reframing it, leveraging it, and showing the world how valuable it really is.
Why Reinvention Feels Hard
Leaving government — whether retirement, RIF, burnout, or just time for a change — can feel overwhelming. The GS system gives stability and structure that industry doesn’t always offer. And yes, it’s easy to assume private companies won’t understand (or value) the regulations and processes you’ve mastered.
But here’s the reality: the very skills you may see as “just part of the job” are the ones industry desperately needs.
The gap between government and industry is narrower than you think.
The Transferable Skills You Already Have
You don’t need to start from zero — you already have the toolkit. The key is learning how to describe it in business language.
Here are some examples of what already may bring to the table:
- Contracting & acquisition knowledge — You know how solicitations, awards, and teaming arrangements actually work. That’s the “inside edge” industry wants. Even outside federal work, every company manages contracts and procurement.
- Compliance & regulatory expertise — FAR, DFARS, cybersecurity, subcontracting. You’ve lived in the rulebook others are just trying to skim. That makes you the person who keeps companies audit-proof and out of trouble.
- Project management — Leading teams, coordinating stakeholders, delivering on time and on budget. Industry calls it “project management” — you’ve been doing it for years.
- Quality assurance — You’ve delivered work under standards so tight most companies would panic. That mindset is gold in any industry.
- Process improvement — Streamlining workflows, cutting inefficiencies, boosting value.
- Risk management — Federal service teaches you to see around corners. Identifying and mitigating risk is survival in business.
- Communication & leadership — Briefing senior leaders, guiding stakeholders, and making the complex simple.
These aren’t “government-only” skills. They’re mission-critical business skills. And when you frame them right, they make you stand out.
Lessons from My Own Reinvention
I know reinvention because I’ve lived it.
I started out delivering pizzas. Not exactly the launchpad you’d expect for someone who would later handle over $7 billion in federal contracts. But every step — government contracting, law school, federal service, corporate roles, consulting, and now professional training — built on the skills I already had.
The breakthrough wasn’t “starting fresh.” It was reframing what I knew so it mattered to the people I was serving.
When I left government, I worried my acquisition background wouldn’t translate. Instead, I found that contractors and consulting firms were desperate for someone who could bridge the gap — to translate requirements, evaluation criteria, and compliance into strategies that worked.
My government career wasn’t a limitation. It became my calling card.
Practical Steps for Federal Employees Considering Change
- Inventory your skills. Write them in plain language. Instead of “1102 Contract Specialist,” say: “Managed $300M in procurements, ensuring compliance with FAR Part 15 and delivering mission-critical capabilities.”
- Translate acronyms into results. Industry doesn’t always speak FAR or DFARS. They want outcomes: reduced risk, faster delivery, smarter negotiations.
- Highlight transferable strengths. Project management, compliance, contracting, subcontracting, quality assurance, and process improvement are valuable across industries.
- Leverage your network. Careers after federal service often start with connections — former colleagues, contractors (always within the rules of ethics, of course), or professional organizations.
- Start small. You don’t need to leap into the C-suite. Try consulting, short-term contracts, or training gigs to test the waters and prove your value.
- Embrace reinvention. It’s not about abandoning who you were. It’s about evolving into the next version of yourself.
The Big Picture
Government service gave you credibility, resilience, and hard-earned expertise. Industry gives you the chance to apply it in new ways — often with more flexibility and financial upside.
The hardest part of reinvention isn’t learning new skills. It’s believing the ones you already have are more valuable than you realize.
Final Takeaway
Your federal career wasn’t the finish line — it was the launchpad.
The skills you’ve built aren’t just transferable. They’re in demand. The only real question is: where will you take them next?
Why Everyone Is Talking About Oral Presentations (And How AI Can’t Save You Here) by Natasha Velez
Government contracting is having a moment. And by “moment,” we mean a complete shake-up of how proposals get evaluated and contracts get won.
If you’ve been in the contracting game for more than five minutes, you’ve probably noticed something: oral presentations are popping up everywhere. What used to be the exception is quickly becoming the rule, and there’s a good reason why agencies are making this shift.
The Great Proposal Pivot
Here’s what’s happening behind the scenes. Government agencies are drowning in 500-page proposal documents that all start to sound the same. Evaluators are spending weeks sifting through technical volumes, past performance narratives, and management approaches that could put a coffee-fueled insomniac to sleep.
Enter AI-powered evaluation tools. Agencies are now using artificial intelligence to scan proposals, match keywords to
requirements, and flag compliance issues faster than any human evaluator ever could. Sounds efficient, right? It is. But it’s also creating a new problem.
When AI can instantly identify which proposals hit all the technical checkboxes, the playing field gets flattened. Suddenly, everyone’s proposal looks technically compliant, everyone’s past performance seems relevant, and everyone’s management approach appears sound on paper.
That’s where oral presentations come in. They’re the human differentiator in an increasingly automated world.
Why Agencies Are Going All-In on Orals
Think about it from the government’s perspective. You’ve got three technically compliant proposals sitting on your desk. All three companies have solid past performance. All three hit the requirements. How do you pick the winner?
The oral presentation becomes the tie-breaker. It’s where agencies get to see who’s really behind those carefully crafted proposal documents. Can the proposed project manager actually articulate the technical approach? Does the team have genuine chemistry, or did they just meet for the first time in the parking lot?
This shift is happening across all contract types. We’re seeing oral presentations for everything from simple IT services contracts to complex multi-million-dollar prime opportunities. Even subcontracting opportunities are starting to include oral components.
The AI Advantage (And Where It Stops)
Let’s be clear: AI is revolutionizing proposal development. Smart contractors are using AI tools to analyze RFP requirements, generate compliance matrices, and even draft initial proposal sections. These tools can scan a 200-page RFP in minutes and extract every single requirement, deliverable, and evaluation criterion.
But here’s the thing about AI – it’s really good at processing information, but it’s terrible at being human.
When you’re sitting across from a government panel explaining why your team is the right choice, AI can’t help you read the room. It can’t adjust your message based on the evaluator’s body language or pivot when you realize they’re more concerned about schedule risk than technical approach.
The Human Elements AI Can’t Fake
Authentic Connection
Government evaluators aren’t just buying your solution; they’re buying into your team. They want to know that when things go sideways at 2 AM (and they will), they can pick up the phone and get real answers from real people who understand their mission.
AI might be able to generate talking points, but it can’t create that moment of connection when you share a relevant story about solving a similar challenge for another client. Those authentic moments – the ones that make evaluators think, “These people get it” – those can’t be automated.
Reading the Room
Every oral presentation is different, even when you’re delivering the same technical solution. One panel might be laser-focused on cybersecurity compliance. Another might be worried about your team’s availability. A third might want to drill down into your quality assurance processes.
Experienced presenters pick up on these cues and adjust accordingly. They notice when the contracting officer leans forward during the cost discussion or when the technical lead’s eyes light up during the architecture walkthrough. AI can’t do that.
Handling the Unexpected
Government evaluators love throwing curveballs. “What would you do if your key personnel gets pulled onto another contract?” “How would you handle a 30% budget cut?” “What if the user requirements change completely in month three?”
These scenarios require real-time thinking, not pre-programmed responses. They require the kind of problem-solving and adaptability that comes from actual experience, not training data.
Winning Strategies for the New Reality
Master the Keywords Game First
Before you even get to the oral presentation stage, your written proposal needs to survive the AI screening. This means being strategic about keyword density and requirement matching. But don’t just stuff keywords randomly – agencies are getting smarter about detecting this.
Practice Like Your Contract Depends on It
Because it does. The companies winning oral presentations aren’t just winging it. They’re running full dress rehearsals with mock evaluation panels. They’re timing their presentations to the minute and practicing their Q&A responses until they’re conversational, not scripted.
Bring Your A-Team (Not Your Sales Team)
This is crucial. The people presenting should be the people doing the work. Evaluators can spot a sales pitch from a mile away. They want to meet the actual project manager, the actual technical lead, the actual folks who’ll be answering their calls.
Tell Stories, Don’t Recite Features
Instead of rattling off your company’s capabilities, tell the story of how those capabilities solved real problems. “We reduced processing time by 40%” is a fact. “When Agency X was facing a backlog crisis that threatened their mission-critical operations, we implemented a solution that cut their processing time by 40% and got them back on track in three weeks” is a story.
The Partnership Factor
Here’s something that often gets overlooked: oral presentations aren’t just about proving you can do the work. They’re about proving you can be a good partner. Government clients want contractors who can think like teammates, not vendors.
This means asking smart questions during your presentation. Show them you’ve thought beyond just the requirements to the real challenges they’re facing. Demonstrate that you understand their mission, not just their RFP.
Preparing for What’s Coming Next
The trend toward oral presentations isn’t slowing down. If anything, it’s accelerating. Agencies are realizing they get better outcomes when they can evaluate the actual people, not just the paper proposals.
At NVS Strategic Solutions, we’re seeing this shift across all our client engagements. The companies that are adapting quickly – investing in presentation training, rethinking their proposal teams, and treating orals as seriously as written submissions – are winning more work.
The companies that are still treating oral presentations as an afterthought? They’re getting left behind, even when they have the best technical solution on paper.
The Bottom Line
AI is changing government contracting in fundamental ways. It’s making proposal evaluation more efficient, more consistent, and more focused on true differentiators. But those differentiators aren’t technical specs or past performance metrics – they’re human qualities like adaptability, partnership, and authentic expertise.
The contractors who understand this are the ones who’ll thrive in this new environment. They’re not trying to out-AI the machine; they’re doubling down on being unmistakably, authentically human.
And that’s something no algorithm can replicate. The conversation around oral presentations isn’t just industry chatter – it’s a signal that government contracting is evolving. The question isn’t whether your company will need to master oral presentations. The question is whether you’ll master them before your competition does.
Human connection still wins contracts. AI just makes that connection more important than ever.