Before there was a FAR, before there was SAM, before there were set-asides, there were contracts. The Continental Congress awarded contracts to suppliers for weapons, uniforms, and provisions during the Revolutionary War. Some of the first government contractors were the merchants and craftsmen who helped build a nation.

The scale has changed. The systems have changed. But the foundation remains the same: the government needs capable businesses to deliver what the mission requires.

Happy Independence Day from all of us at USFCR.

r/GovernmentContracting Weekly Roundup, June 24 to July 1, 2026

The 3D printer thread this week has a small but genuinely useful reframe hiding in it.

u/face_eater_5000 posted asking where the whitelist of approved 3D printers for federal manufacturing lives. He's a single-operator SDVOSB with a micromanufacturing cell in his house, trying to become a vendor supplying replacement parts, and he wanted to know which machines are on the approved list before he spends the money.

The answer from the thread is that the list doesn't exist because that's not how federal manufacturing works. The government does not qualify equipment. It qualifies parts. When a solicitation posts, it references a drawing, a material spec, and a process spec, and your part gets evaluated against those. Nobody checks what machine you used to make it. What matters is whether the finished part meets the drawing and passes whatever nondestructive testing the spec calls out.

That reframe changes the whole approach for a small manufacturer. Instead of shopping for a printer that's on some imaginary approved list, the question becomes which specs your current or planned equipment can actually meet, and which solicitations don't ban additive manufacturing outright. Some do. AM parts often struggle with porosity requirements, and there are categories where the government still won't accept them regardless of how good the print is. Those are worth knowing before you invest in the machine.

The broader point for anyone new to federal manufacturing: if you find yourself hunting for an approved vendor list or approved equipment list before bidding, stop and check whether the qualification actually works that way. A lot of federal buying is spec-based, not vendor-based. The list you're looking for might not exist because the government doesn't need it to exist.

So a question worth throwing back: for the manufacturers here who've qualified parts under a federal spec, what was the moment you realized the process was different than what you expected? And for anyone doing AM specifically, which agencies or NAICS codes have been most workable versus most closed to additive?

Also this week in r/GovernmentContracting**:**

• u/Miller25 asked about Booz Allen retaining incumbents on a recompete they may have just won. The consensus in the replies: incumbents usually get retained because the overhead of replacing an entire team is too high, but customer relationships matter more than any "key personnel" designation. If the client wants you back, you're back.
• u/No_Hold_9560 is doing acquisition due diligence on a services firm with 70% federal revenue and asked how to actually stress-test that revenue durability. The most useful answer pointed at pairing USASpending with CPARS to see not just contract history but actual performance ratings. Worth reading if you're evaluating a similar deal.
• u/samster4225 got their IARPA white paper rejected with feedback that said their 12-month timeline was too risky, even though the 12 months was IARPA's own stated timeline. The replies clarified what was actually happening: the government wasn't rejecting the schedule, it was rejecting the risk they saw in the team's ability to hit it. Useful distinction if you've ever felt whiplashed by proposal feedback.
• u/DirectionDangerous42 runs an electrical contracting shop in El Paso and asked how to get bigger contracts. The most concrete answer pointed at Fort Bliss next door and the base operations and maintenance contracts that flow work down to local trades. A good example of how geography plus a nearby installation can be a real strategy, not just networking advice.

Back next week.

This has been another quiet week for standout threads, so this post is built around the questions new vendors keep asking, with the sources sought mix-up leading.

The one worth slowing down on is the sources sought confusion, because it quietly costs people opportunities they don't even realize they're skipping.

The pattern goes like this. A new vendor sees a sources sought notice for work they can do, assumes it's a contract they have to bid on right now, and either scrambles or ignores it because they aren't ready. Both reactions miss what it actually is.

A sources sought is market research under FAR Part 10, not a solicitation. Responding doesn't commit you to anything, doesn't obligate you to bid later, and costs nothing but the time to write it. What it does do is put your capability in front of the agency before the requirement is locked.

That's the part that matters. By the time an RFP is public, the agency has usually done its homework and often has a shortlist in mind. The sources sought is the window before that, while the contracting officer is still deciding how to buy, whether to set the work aside for small business, and which NAICS fits. If enough capable small businesses respond, the agency can set the work aside under the rule of two, which changes who you're competing against. A good response isn't just a hand raise. It's a chance to shape the field you'll end up bidding in.

So the question worth opening up: for anyone who has responded to a sources sought, did your input ever visibly change the final solicitation or the set-aside, or at least get you a call from the KO? Curious where it actually moved the needle versus where it vanished into the void.

Also this week in r/GovernmentContracting**:**

• The perennial "where do I even start" question. Short version: register in SAM.gov first, it's free and it issues your UEI, then narrow to 1-3 NAICS codes that match what you already do well. A registration with no focus doesn't pull opportunities toward you. Useful if you're in your first 90 days and treating that window as setup and research instead of bidding.
• A few people asked how to tell whether they actually count as a small business and qualify for set-asides. Size is set by SBA per NAICS code, measured by revenue or employee count depending on the industry, and certifications like 8(a), HUBZone, WOSB, and SDVOSB sit on top of that with their own rules. Check the SBA size standards tool before claiming anything anywhere. Matters most if you're near a threshold, where your NAICS choice can swing your status.
• The recurring "is it just SAM.gov" question about finding work. Most opportunities above $25,000 post on SAM.gov Contract Opportunities, but the early signals show up first in sources sought, RFIs, and agency forecasts, and USAspending.gov shows you which agencies and primes actually buy your service. Worth a read if you keep refreshing SAM and concluding there's nothing there.
• The closed-loop classic: every solicitation wants past performance you can't get without a contract. Commercial work counts, and subcontracting or teaming builds a federal record without being the prime on day one. Your first win is often a subcontract, not a prime award. Useful if you're stuck at the starting line.

Quieter week on the sub, but the middleman podcast thread is worth pulling out.

u/gjsjr04 watched a podcast titled "How Anyone Can Make $10K+/Month From the Government" and brought the strategy to the sub to ask if it was real. The pitch: set up a generic LLC, bid on random federal contracts from anywhere in the country (hazardous waste, catering, whatever), 100% subcontract the work, collect the spread. The host described herself as a broker.

The community answered it without much disagreement. The reason it doesn't work is FAR 52.219-14, the limitations on subcontracting clause. On small business set-asides, the prime has to self-perform at least 50% of the billable labor with its own employees. Project management does not count.

A contracting officer in the thread said they get around 100 solicitations a day from this kind of vendor, all promising they'll handle "project management" while subbing the actual work. They disqualify the quotes on sight. Other commenters added that competitors will protest, established vendors recognize the pattern immediately, and the consequences scale from blackballing all the way up to civil or criminal prosecution depending on how reckless the execution is.

What makes the thread worth reading isn't the takedown. It's the structural reason: federal set-aside programs exist to put real work in front of real small businesses, and the 50% self-performance rule is the mechanism that protects that. A pass-through model isn't a loophole. It's the specific thing the rule was written to stop.

So the question worth opening up: for people who've been on the receiving end of a protest or KO conversation about this, what's the moment the wheels actually came off? Was it the technical evaluation, a subcontracting plan that didn't add up, or someone in the supply chain flagging it?

Also this week in r/GovernmentContracting:

• u/FlyFish503 won his first two DLA awards on the same day and asked the room how to actually execute them. u/mattyyahoo wrote out the entire workflow start to finish, from order receipt through MIL-STD-129 packaging through WAWF invoicing. The single most useful comment in the sub this week if you're new to DIBBS.
• u/FSUAttorney runs a six-person SDVOSB IT shop with three years of subcontracting past performance and an FCL, and asked how to transition from sub to prime. The replies converged on the same answer: target identification first, then capture, then vehicle access. Worth reading if you're at a similar stage.
• u/toxidani1024 asked whether one employee can legally be paid different wages under an SCA contract depending on which task they're performing. The answer: yes, if the tasks are categorized, the time is segregated by classification, and each rate meets the wage determination minimum. A useful thread if you run lab or multi-classification work.

Back next week.

The recompete anxiety thread this week is worth reading even if you're not facing one.

A new PhD hire posted about finding out, after moving across the country for the job, that the contract goes up for recompete in a year. Nobody mentioned it during hiring. The fiancé already has a job in town. The customer says she'll be retained but how much does that actually mean.

What the replies surfaced is the mechanics most people new to contracting don't know yet. When a recompete happens, the easiest path for the incoming prime is almost always to keep the people already doing the work. A badge swap costs the new prime less than recruiting from scratch. Agencies often communicate key personnel preferences to whoever wins, and a customer who says they want you back has more weight than it sounds like. Specialized roles, especially anything where the client depends on a specific person's expertise, are very rarely the ones cut.

The math changes if you're one of seven people doing the same work. It changes again if the contract is staff augmentation versus mission work. But for a PhD in a specialized role with a customer asking for retention, the realistic worst case is usually a badge swap, not a layoff.

The thread is also a reminder of something hiring managers don't always say out loud: when a contract has less than 12 months left on the current period of performance, that should be part of the conversation before someone relocates. It rarely is.

So a question for the recompete veterans: when you've been kept through a transition, what actually happened in the 60 days before the award? Did the new prime contact you directly, did the existing employer broker it, or did you wake up to a new badge and a new email address?

Also this week in r/GovernmentContracting**:**

• A federal employee burning leave before official retirement asked whether contractor HR systems would flag her starting a contractor role early. The replies were useful: HR systems themselves don't have visibility into active fed employment, but the resume and the OCI agreement catch it during interview and onboarding anyway. It's not automatically disqualifying as long as the ethics office signs off and there's no procurement authority conflict.
• u/Global_Gas_1506 asked the room what a proposal manager should be making at a $15-20M small business. The 32 comments converged on a clear point: the right number depends entirely on whether you're bringing in new business or just managing the pipeline that already exists.
• u/Spiritual-Effect-681 asked how small shops are tracking CDRLs. Most answers said Excel. The interesting part was the comment that the failure mode is almost never the tool. It's that nobody explicitly owns the CDRL function and dates move with mods that don't get tracked.
• A defense subcontractor asked about Ironclad vs. TechnoMile for contract lifecycle management. The thread turned into a small but useful catalog of which CLM tools are actually FedRAMP-moderate compliant and which ones sales reps pretend are. Worth a scan if you're shopping in that space.

Back next week.

If your SAM registration is in a shared office space, you should know what happened to u/DerixSpaceHero this week.

He has 1,200 square feet of dedicated office space behind a locking door, in a four-story building, with an annual lease. He sent the lease, sent a picture of the door, and SAM still kicked his entity registration back. The rejection cited the standard list of unacceptable addresses (PO boxes, virtual offices, coworking) but flagged him because another contractor is registered at the same building address.

The pattern in the replies was clear: this isn't a new rule, but enforcement has gotten stricter. DLA's CAGE code validation is reading "shared office space" more aggressively than it used to. The thing that actually unblocks these cases is escalation. First-tier Federal Service Desk agents don't have the authority to fix it. You have to specifically request a CAGE code validation specialist and reference the other registered entity by name and suite so the validator can see they're separate operations.

The reason this matters for anyone reading: a lot of small businesses share commercial buildings, especially in coworking-adjacent setups that have been fine for years. If you registered before this enforcement shift, you're probably grandfathered. If you're updating, renewing, or registering fresh, the building address itself is now a flag.

Two questions worth opening up: has anyone gotten through this in the last 60 days, and what specifically did the validator ask for? And separately, has anyone had to actually relocate to fix it, or has documentation always been enough?

Also this week in r/GovernmentContracting

• u/Limp_Tune_3222 asked why embassy KOs never respond to status requests. A KO answered honestly: 5 seconds per email times 15 vendors per bid times 20 active contracts is most of a workday spent on responses, and most of those quotes had no real effort behind them. Useful perspective on what's actually happening on the other side of the inbox.
• u/Embarrassed-Fly6921 and u/Known-Disaster-4493 both posted classic "how do I break in" threads in the same week. The replies are a good reference for anyone navigating the same questions.
• u/BeachesAreOverrated asked whether DoD acquisition offices are running out the clock on the TINA threshold change (jumping from $2.5M to $10M on June 30). The KOs in the thread said no, nobody has the bandwidth to delay anything strategically right now.
• u/DistinctTradition200 asked whether SDVOSB certification moves the needle on a non-set-aside SBIR Phase I. The answer was mostly no, technical reviewers are scientists scoring on merit, but mention it briefly in your company capability section.

Back next week.

The thread that stuck with me this week came from a contracting officer.

u/Character_Project715, an 1102, asked how vendors actually track federal contracting given that most of it doesn't touch sam.gov. The question wasn't rhetorical. They genuinely wanted to know. That's worth sitting with for a second. The people writing the contracts are telling us the public-facing system is not the picture.

The replies were a mix of agency forecasts, GovWin, GSA eBuy, FPDS pulls, subcontracting plans on USASpending, sources sought watching, and old-fashioned KO relationships. Nothing exotic. But the pattern across the answers was consistent: serious vendors stopped treating sam.gov as the universe years ago. They use it as one feed among many, and most of the real positioning happens before anything posts.

What's useful about hearing this from a 1102 is that it confirms what experienced vendors already know without it sounding like sales pitch. If you build your pipeline around sam.gov keyword alerts, you're seeing the contracts after the shaping is done. The wins were decided in the months nobody was watching.

So here's the question: for the people who've moved past sam.gov as their primary source, what was the shift that did it? Did you lose a bid you should have won? Did a KO tell you something? Or did you just notice the same names kept winning the work you only saw on the day it posted?

Also this week in r/GovernmentContracting:

• u/Lemonade867 is making $115K in a fluff TS role and wants out into software engineering. Practical advice in the replies about self-directed development inside government contracting.
• u/Andrew-Gene is debating leaving finance for a 5-year gov contracting role at $30K more. The replies are a useful reality check on what that tradeoff actually looks like.
• u/Familiar_Beach_1392 asked about SAIC benefits ahead of a possible switch from sub to prime. Helpful if you're evaluating a similar move.

Back next week.

r/GovernmentContracting Weekly Roundup - April 30 - May 7, 2026

A few themes kept showing up this week: cleared career tradeoffs, post-award lessons, low-bid frustration, funding delays, and the practical side of getting ready before an award hits. Different topics, same underlying issue: government contracting rewards people who understand the process behind the process.

A clearance got the strongest reaction.

u/Main-Lake-1590 kicked off the biggest thread of the week by asking whether cleared work is really worth it when the day-to-day role feels dull, restrictive, and disconnected from their education level. That question hit because cleared work gets talked about like a golden ticket, but the reality is more mixed. The pay can be good. The job security can be strong. The work environment can also feel limiting, especially in a SCIF where normal communication and flexibility are not always available.

The replies showed both sides. Some people missed the hard boundary between work and home that SCIF life can create. Others agreed that the work can feel slow or underwhelming. That is probably the real answer: a clearance is valuable, but it is not automatically fulfilling.

What matters is whether the role is building toward something. If the job gives you stability while you build technical skills, understand the mission, and position yourself for a better cleared role, it can be a strong stepping stone. If it only gives you a paycheck while your skills stall, that is worth noticing early.

Debriefs also got a lot of attention.

u/GovConTips raised a point many contractors skip after a loss: asking for a post-award debriefing. The thread was useful because it did not stop at “you should request one.” Another commenter added the practical side: debriefings can be thin, cautious, and limited because agencies are trying to avoid disclosing sensitive information or creating protest risk.

Both points can be true at the same time. Contractors should ask for debriefs, but they should not expect a private coaching session. The value usually comes from asking better questions, comparing the answers to the evaluation criteria, and turning the feedback into a better proposal process.

That means asking where the proposal was weak, whether price or technical approach drove the gap, and what separated the awardee. Even a limited answer can help if you track the pattern across multiple bids.

Cleared contracting came up from the business-owner side, too.

u/CoastieKid asked about starting an SDVOSB focused on cleared work while living in an area without many cleared positions or SCIFs nearby. The replies pointed to a key distinction that many new cleared founders miss: having personal cleared experience is not the same as having a business ready to perform classified work.

The big issue is not always geography. If employees are working at client sites, travel is manageable, and the niche is strong, location may not be the dealbreaker. The harder issue is often the Facility Clearance path, prime relationships, and whether there is a realistic subcontracting route into the work.

For a new firm, subcontracting is usually the cleaner first step. It lets the business build relevant past performance, understand cleared staffing expectations, and potentially work with a prime that can support the clearance path when the requirement justifies it. Trying to jump straight into prime cleared work without that foundation can get expensive and frustrating fast.

Small construction bids showed how confusing “low price” can look from the outside.

u/tmill2100 asked about a small construction RFP where the required fixture spec seemed expensive, but the winning bid came in dramatically lower. That kind of result naturally raises questions. Did the awardee actually meet the spec? Did they have inventory? Did they propose an alternative? Did the solicitation allow flexibility? Or did something get missed?

The useful takeaway from the replies was that specs are not supposed to be decorative. If a solicitation requires certain minimum characteristics, those requirements matter. At the same time, small buys and simplified acquisition procedures can leave room for different evaluation approaches, depending on how the solicitation was written.

That is why the solicitation language matters more than assumptions. If the RFP required product data with the bid, that is one situation. If materials are reviewed after award through submittals, that is another. If Buy America or Buy American requirements were included, that would create another layer entirely.

The practical move is not to guess from the award amount alone. Ask the contracting officer for the explanation available to you, review the award notice, and document the specific solicitation requirements that made the low price seem unrealistic.

Award delays were another recurring frustration.

u/PotentialDeadbeat asked about delayed defense awards after seeing multiple proposals across several defense agencies stall out. The replies were a good reminder that funding delays are often more fragmented than contractors want them to be. One program may be waiting on internal approval. Another may be affected by budget churn. Another may be delayed because a key person moved, retired, or got buried in backlog.

That is what makes these delays so hard to plan around. From the contractor side, it feels like “DoD funding is frozen.” From the inside, it may be ten different reasons across ten different offices.

Contractors cannot control that timing, but they can control how exposed they are to it. A pipeline built around a few delayed awards can create real cash flow pressure. A stronger pipeline has different stages, different agencies, and enough active prospecting that one stalled award does not freeze the whole business.

Vendor readiness also came up in a beginner-friendly way.

u/Difficult-Seat510 shared that they were about to speak with a potential vendor for the first time. It was a small thread, but it pointed to something important: vendor relationships should not start after the award if the work requires fast mobilization.

That is especially true for service work, logistics, construction support, emergency response, staffing, and anything with a short performance ramp. If you only start calling vendors after award, you may already be behind.

A good vendor call does not need to be complicated. Confirm scope, pricing assumptions, lead times, capacity, insurance, certifications, and communication expectations. Then keep notes. The goal is not just to find someone who says yes. The goal is to know who can actually perform when the clock starts.

What small contractors should take from this week:

• u/Main-Lake-1590’s thread showed that cleared work can offer stability, but a clearance alone does not make a role satisfying.
• u/GovConTips’ debrief post was a reminder that losses can still produce useful competitive intelligence.
• u/CoastieKid’s question highlighted why cleared founders need to understand FCL realities and subcontracting paths.
• u/tmill2100’s construction RFP thread showed why low bids should be evaluated against the actual solicitation language, not just gut instinct.
• u/PotentialDeadbeat’s funding-delay post reinforced the need for a pipeline that can survive slow awards.
• u/Difficult-Seat510’s vendor thread was a good reminder that readiness starts before the award notice.

The businesses that improve fastest are usually not the ones with perfect conditions. They are the ones who keep learning from each awkward, slow, confusing step.

We hope this helped bring some clarity to the conversations from this week. We’ll be back next week with another roundup, so keep leaving your questions, experiences, and replies!