Federal Digital Services Contracting: USDS, 18F, and Modern Tech Procurement

A quiet revolution in federal technology procurement has been underway since 2014. The US Digital Service (USDS) and 18F (housed at GSA) were created to bring modern software development practices — agile, user-centered design, open source, iterative delivery — into federal agencies. Their influence has reshaped how the government writes RFPs, evaluates proposals, and manages technology contracts.

For digital-native technology companies — startups, design firms, modern software developers — understanding this ecosystem opens access to federal contracts that traditional IT contractors are poorly equipped to pursue.

---

The Federal Digital Services Landscape

US Digital Service (USDS)

The US Digital Service is a small agency within the Executive Office of the President. Founded in 2014 after the Healthcare.gov launch failure, USDS deploys small teams of technology experts ("tours of duty") to partner with federal agencies on their most critical digital challenges.

USDS does not primarily award contracts — it provides in-house expertise to partner agencies. However, USDS teams:

• Help agencies design RFPs for modern technology procurements
• Evaluate vendor proposals for technical quality (not just FAR compliance)
• Embed with agency teams to improve how they manage technology development contracts

When USDS is involved in an agency's procurement, the RFPs tend to be markedly different — emphasizing technical demonstrations, working code, and user research over paper certifications.

18F (General Services Administration)

18F is a digital consultancy within GSA that works with federal agencies on a cost-recovery basis. Unlike USDS, 18F's primary function includes procurement assistance:

• Acquisition consulting: Helping agencies structure contracts for modern technology delivery
• Path Analysis: Short discovery engagements to diagnose technology problems and recommend solutions
• Assisted Acquisition: 18F can act as the contracting office for agency clients, managing the full procurement from market research through contract award

18F developed influential procurement guides and templates (the "TechFAR Handbook" and "De-risking Government Technology Guide") that many agencies use as models for modern IT procurement.

Agency Digital Service Teams

Many major federal agencies now have their own digital service units modeled on USDS:

• VA Digital Service — Veterans Affairs technology modernization
• CMS Innovation Center — Medicare and Medicaid technology programs
• DDS (Defense Digital Service) — DoD technology modernization
• PFDS (Presidential Fellows for Digital Service) — cross-agency rotation program

When an agency has a mature digital service team, their procurements tend to embrace modern practices: challenge-based evaluations, technical demonstrations, agile delivery requirements.

---

How Modern Federal Digital Procurement Works

Challenge-Based Evaluation

Traditional federal IT proposals require companies to write lengthy technical approaches describing what they would do. Modern digital service-influenced procurements often require companies to demonstrate capability instead:

• Code challenges: Applicants receive a dataset or problem and submit working code within 72 hours
• Prototype development: Offerors build a working prototype of a system component as the "proposal"
• Technical presentations: Live demonstration of a past project or live coding exercise

These approaches favor companies with demonstrated engineering talent over companies with strong proposal writing capabilities. Small digital companies that can execute well often outperform large incumbent contractors.

Human-Centered Design Requirements

Digital service-influenced RFPs frequently require:

• User research: Evidence that the contractor will engage actual end users during development
• Usability testing: Periodic testing with representative users to validate design decisions
• Accessibility compliance: WCAG 2.1 AA compliance and Section 508 requirements
• Plain language: Requirements for government-readable documentation and user interfaces

Open Source Requirements

Some digital service contracts require:

• Code developed under the contract to be published to public GitHub repositories under open source licenses
• Use of open source components rather than proprietary frameworks where feasible

Iterative Delivery Over Waterfall

Modern federal digital contracts structure delivery differently:

• Sprint reviews with government product owners (Scrum/Kanban practices)
• Working software delivered incrementally rather than long design-then-build cycles
• Product owner on the government side with real decision-making authority
• Lightweight documentation instead of voluminous design documents

---

18F's Acquisition Templates: What They Mean for Vendors

18F publishes acquisition templates used by agencies that work with 18F and by agencies independently. Understanding these templates helps you understand what modern federal buyers expect.

Quality Assurance Surveillance Plan (QASP) templates: 18F QASPs focus on code quality, deployment frequency, accessibility, and user satisfaction — not traditional contract milestones. If your RFP includes an 18F-style QASP, expect to be evaluated on:

• Automated test coverage
• Deployment pipeline quality
• Accessibility audit results
• End-user satisfaction metrics

Incremental funding models: 18F-influenced contracts often use smaller initial awards with option periods tied to demonstrated value, rather than large upfront commitments. This reduces government risk but also means you need to continuously demonstrate value to unlock additional funding.

---

The Defense Digital Service (DDS) and DARPA

Within DoD, the Defense Digital Service (DDS) and DARPA represent distinct modern technology procurement approaches:

DDS: Small teams of civilian technologists embedded across DoD to solve high-impact problems. DDS participates in procurements for cutting-edge defense technology — often using Other Transaction Authority (OTAs) rather than FAR-based contracts.

DARPA: DARPA funds breakthrough research through contracts and Other Transactions. DARPA is not a typical defense contractor market — they seek genuinely novel technical approaches. For companies with breakthrough technology in AI, quantum computing, biometrics, autonomous systems, or communications, DARPA is an important early customer.

Other Transaction Authority (OTA): Many DDS and DARPA projects use OTAs (10 U.S.C. § 4021 for research; 10 U.S.C. § 4022 for prototype) which are not subject to the FAR. OTAs allow faster, more flexible agreements that can transition to contracts or production awards.

---

How to Position for Digital Services Federal Contracting

Demonstrate Working Software, Not Just Credentials

Modern federal digital buyers are skeptical of large consulting firms' promises and credentials. They want to see working code. Build a portfolio of:

• Open-source contributions or public GitHub repositories
• Past government projects with demonstrable outcomes (improved user satisfaction, faster processing, lower error rates)
• Technical blog posts demonstrating engineering depth

Get on 8(a) STARS III or OASIS+ Professional Services

Digital services companies need a GWAC vehicle to compete for most federal task orders. 8(a) STARS III (if you have 8(a) certification) or OASIS+ Management Consulting / IT are the primary vehicles for digital services task orders.

GSA Schedule 70 / Schedule IT: Many digital service task orders under $250K use direct ordering from the GSA IT Schedule. If you're a small digital company, a GSA Schedule is often the fastest path to initial task orders.

Target Emerging Agency Digital Service Programs

Agencies building new digital service teams are often the most open to new vendors — they don't have entrenched incumbents yet and are actively seeking modern technical partners. Monitor:

• New agency USDS partnership announcements
• New agency digital service unit formations
• Agency digital transformation strategy documents (often published as PDFs)

Respond to 18F-Assisted Solicitations

When 18F is involved in an acquisition as the contracting office, you'll see this in the solicitation. 18F-assisted acquisitions use modern evaluation methods and are often more accessible to smaller digital companies than agency-run traditional IT procurements.

---

Key Takeaways

• USDS (Executive Office) and 18F (GSA) have reshaped how modern federal technology is procured — introducing agile, user-centered design, challenge-based evaluation, and open source requirements.
• Digital service-influenced RFPs favor demonstrated technical capability over paper proposals — code challenges, prototypes, and technical presentations are increasingly common evaluation methods.
• Defense Digital Service (DDS) and DARPA use Other Transaction Authority (OTA) for breakthrough technology — not subject to FAR, faster and more flexible.
• 8(a) STARS III and OASIS+ Professional Services are the primary GWAC vehicles for digital services task orders — GWAC positioning is essential for larger task orders.
• Portfolio over credentials: Modern federal digital buyers want to see working software, public repositories, and measurable outcomes — not just years of experience and certifications.
• 18F-assisted solicitations and agency digital service team procurements are often the most accessible federal technology opportunities for digital-native small businesses.

Find federal digital services and technology contracting opportunities on RFxNerd →