How do I build a federal / public-sector motion from scratch in 2027?

The outcome you should expect

Set expectations honestly before the first dollar is spent, because the gap between what leadership imagines and what actually happens in year one is where most failed federal motions die. The realistic outcome of a well-executed first twelve months is zero meaningful revenue and a functioning machine — a federal sales leader hired, a sponsoring agency relationship secured, a FedRAMP package in agency review, reseller paper signed, a GSA Schedule offer submitted, and two to four real captures opened with written capture plans. That is a successful year one. Any plan that books federal revenue at month twelve has been mis-set from the start, and the board should be told this in writing before the search for the first hire begins.

Time-to-meaningful-revenue for a from-scratch motion runs 24 to 48 months. The critical path decomposes roughly as: 6-12 months to hire the federal leader and develop a sponsoring agency relationship; 12-24 months for FedRAMP Moderate authorization (partially overlapping); 6-12 months to land your own GSA Schedule (overlapping, and short-circuitable via reseller paper); 18-36 months for a first serious capture to convert to a funded award; and 3-9 months of agency Authority to Operate on top of the signed contract before the product is switched on. These phases overlap, but they do not compress below roughly two years for a company starting cold.

The capital requirement over the first three years lands in the $3.5M-$7.5M range for a civilian-agency motion: FedRAMP Moderate authorization at $500K-$2M, a GovCloud environment and its ongoing premium, continuous monitoring at $200K-$500K per year once authorized, a GSA Schedule offer with consultant support at $15K-$50K, market intelligence tooling at $15K-$50K per year, two to four federal headcount at $250K-$450K OTE for the leader plus sellers and capture support, and bid-and-proposal budget that a single serious capture can consume six figures of. Defense motions cost more because of clearances, higher impact levels, and CMMC.

The payoff that justifies the wait is the shape of the revenue on the far side. Federal contracts are budget-backed, multi-year, structured around base periods plus option years, and structurally sticky — displacing an incumbent inside a program of record is hard for your competitors in exactly the way it was hard for you. Once an agency has issued your ATO, absorbed your product into a mission workflow, and carried you through an option-year exercise, churn approaches zero and expansion happens inside a relationship the agency already accepted risk on. Public-sector revenue is also counter-cyclical relative to commercial software spend, which is why boards that can fund the wait usually should.

The decision gate is binary and worth stating plainly. Do not start unless you have 24-36 months of runway you can commit to a market that pays nothing in year one, a credible path to a sponsoring agency, and a commercial business healthy enough that a federal miss does not threaten the company. If any of the three is missing, the correct move is to run a SLED motion first — it builds real government past performance and operational muscle at roughly a tenth the capital cost, and it materially de-risks a later federal push.

What drives that outcome

Four variables drive whether the motion converts on schedule or bleeds cash for three years and gets quietly defunded. Understanding which one is actually gating you at any moment is the core management discipline of the first two years.

The sponsoring agency is the hardest dependency and the one you control least. Under the agency-ATO path, you need a real federal customer willing to put their name on your authorization package and shepherd it through their security organization. That is a chicken-and-egg problem: your first federal "sale" is convincing an agency to sponsor a product they cannot yet legally run. Sponsors come from relationships — a program office with an urgent mission need, a prime who wants your technology on their team, or a SBIR Phase I that put you in front of a program manager. This is why the first hire's relationship network is not a nice-to-have; it is the mechanism that unblocks everything downstream.

The compliance program determines whether you are allowed to sell at all. In commercial software, compliance is a sales-enablement artifact produced alongside the product. In government, the order inverts: the authorization is the thing you are building first, and the commercial product is an input to it. FedRAMP Moderate covers roughly 325 NIST 800-53 controls, requires a System Security Plan running into the hundreds of pages, a formal 3PAO assessment, remediation against a Plan of Action and Milestones, and an agency authorization decision. It has a program manager, a budget line, a Gantt chart, and an external dependency you do not control.

Contract vehicle access determines who can buy and how fast. A federal agency cannot put your product on a card. Purchasing flows through pre-competed vehicles — the GSA Multiple Award Schedule, governmentwide acquisition contracts like NASA SEWP, agency-specific IDIQs, Other Transaction Authorities on the defense side, and SBIR Phase III, which can be sole-sourced without further competition. Reseller paper through an aggregator gives you transactability in weeks; your own Schedule takes 6-12 months but gives you long-term direct-relationship control.

Capture discipline determines whether pursuit spend converts. A federal opportunity runs 18-36 months from identification to award, and the work in that window is a named discipline with gate reviews and bid/no-bid decisions. Skipping the discipline means burning bid-and-proposal dollars on unwinnable pursuits.

Benchmarks and realistic ranges

Numbers matter here because the whole failure mode is underfunding a known-cost project. These are the ranges a finance team should model against.

Compliance. FedRAMP Moderate all-in runs $500K-$2M+ and 12-24 months from serious start to authorization, covering 3PAO fees (commonly $250K-$600K across initial assessment and remediation), the GovCloud environment, a dedicated compliance and security team, documentation labor, and remediation cycles. FedRAMP High runs materially higher and longer — think $2M-$4M+ and 18-30 months — and applies to law enforcement, emergency services, financial systems, and large PII repositories. Continuous monitoring after authorization is a permanent $200K-$500K+ per year in tooling, annual 3PAO fees, monthly vulnerability scans, monthly POA&M updates, and dedicated staff. StateRAMP, the SLED analog, is meaningfully cheaper and faster; many states still accept SOC 2 alone.

Vehicles. A GSA Schedule offer takes 6-12 months from serious start to award, with most companies spending $15K-$50K on a GSA consultant to prepare it. The awarded contract typically runs a base period plus options extending up to twenty years. Reseller paper through an aggregator is signable in weeks and gives you access to their existing Schedule and GWAC portfolio immediately. The cost is margin: aggregators and resellers typically take 3-8 points, more for full value-added services.

Cycle length by sub-market. Civilian agencies run 12-18 months from first serious conversation to funded award for a net-new vendor. DoD runs 18-36 months and frequently routes through prime systems integrators rather than direct. SLED runs 6-12 months and, once you hold a cooperative contract, individual transactions can close far faster. Layer the agency ATO on top of every federal deal: 3-9 months even when your FedRAMP package is clean, because the Authorizing Official and their security staff run their own review on their own timeline.

People. A credible federal sales leader runs $250K-$450K OTE, higher for someone with a proven federal book and a strong network. Expect to fund the role 18-24 months before it produces revenue. Market intelligence tooling — GovWin IQ is the standard, supplemented by SAM.gov, USAspending.gov, FPDS, and GovTribe — runs $15K-$50K+ per year and is not optional; it is how you see opportunities two years out, map incumbents, and track expiring contracts.

Market size and shape. Federal IT spend runs roughly $120B-$130B annually, with civilian agencies taking somewhat over half and DoD IT around $60B-$70B. The government carries small-business contracting goals — historically around 23% of eligible dollars — with sub-goals across 8(a), SDVOSB, WOSB/EDWOSB, and HUBZone designations. Most venture-backed companies qualify for none of these, which means a meaningful slice of the market is reachable only through a qualifying teaming partner.

Revenue timing. The federal fiscal year runs October 1 to September 30, and most appropriations are one-year money that is lost if not obligated by the deadline. The result is a large, predictable award surge in July, August, and the final weeks of September. Build the forecast around it. State fiscal years vary — many run July to June, Texas starts in September, New York in April — so a SLED forecast has several seasonal peaks rather than one.

Risks, edge cases, and failure modes

The commercial-AE hire. The single most expensive mistake is hiring someone with a federal-sounding resume who has actually run commercial enterprise deals. Federal selling is not a sales process run slowly; it is a multi-year, rules-bound relationship campaign that positions you for a procurement that does not exist yet. The account map has layers a commercial map does not: the program office that owns the requirement and the budget, the Contracting Officer who alone can legally obligate the government, the Contracting Officer's Representative once assigned, the end-user community whose advocacy creates pull, the security organization running your ATO, the agency CIO office setting technology direction, an incumbent with deeper relationships than yours, and the prime or reseller through whom the deal actually transacts. Getting this hire wrong costs two years and several million dollars.

Structural defunding. Federal dies quietly more often than loudly. A quarterly-pressured commercial CRO reassigns the federal headcount to "help the number," or a budget cycle trims the compliance line, and eighteen months of investment evaporates six months before it would have paid. The structural defense is to stand the unit up under a dedicated public-sector GM reporting to the CEO with board visibility, measured on leading indicators — sponsor relationship progress, FedRAMP milestone completion, vehicle access established, captures in pursuit, bid/no-bid discipline, teaming positions secured — not on quarterly bookings. Revenue is a year-three metric; holding the unit to it earlier just teaches people to lie or quit.

Comp plan mismatch. Putting a federal seller on a standard annual quota with accelerators when their deals take two years guarantees your best hire leaves at month fourteen with no commission. The plan needs a larger guaranteed component early, milestone-based incentives tied to sponsor secured, FedRAMP authorized, first vehicle award, and first ATO, and a quota that ramps against the realistic revenue curve.

Mistaking FedRAMP for the finish line. FedRAMP authorization is the reusable baseline; it is necessary but not sufficient. Every individual agency still issues its own ATO, a signature from a named Authorizing Official accepting risk on behalf of their organization. A CRO who books revenue on contract signature rather than ATO grant will miss the date by a quarter or two on every single deal. Make ATO an explicit pipeline stage and staff customer success to shepherd agencies through it.

Pricing exposure. Being on Schedule means your pricing is disclosed, negotiated, and audited. The Commercial Sales Practices disclosure requires you to explain how you price commercial customers; the Price Reductions Clause can obligate you to extend certain commercial price cuts to the government. Defective pricing, mischarging, or misrepresentation in those disclosures can become False Claims Act matters with treble damages and whistleblower exposure. Government pricing gets set by finance with contracts counsel, versioned, and defended — never improvised by a seller closing a quarter. The first few contracts set precedents a Contracting Officer will cite for years.

Appropriations risk. Congress is frequently late passing full-year appropriations, and agencies then operate under a Continuing Resolution — prior-year funding levels with restrictions on new starts. Under a CR, net-new vendor awards stall because agencies hesitate to begin something they may not be able to continue. Shutdowns and the threat of them compound it. Track the appropriations calendar as closely as your own pipeline, and carry CR risk explicitly in the forecast rather than absorbing it as a surprise every year.

Color of money. Federal funds come in categories — operations and maintenance, procurement, research and development — each with rules about what it can buy and how long it remains available. Your champion may love the product and be structurally unable to buy it with the money they hold. Qualifying which color funds the deal, and whether it is expiring, is core federal qualification and has no commercial analog.

Prime dependency. Riding a systems integrator onto a large program is often the only realistic path to the biggest deals, but you are one layer from the customer, your margin is set in a subcontract negotiation, and you are exposed to the prime's win probability and program health. Get onto multiple primes' teams for opportunities you care about rather than betting on a single horse.

Roadmap drag. Once authorized, meaningful architecture changes can trigger a significant-change review that gates your release cadence. The authorized environment operates under change-control discipline the commercial environment does not, and engineering leadership has to accept that permanently. Companies that discover this after authorization rather than before end up with a government product line that falls a year behind the commercial one.

Clearance and FOCI. DoD and intelligence work require cleared personnel and often a Facility Clearance. Individual clearances need a sponsor and can take months to well over a year to adjudicate. A Facility Clearance requires sponsorship, cleared management, an appointed Facility Security Officer, and a Foreign Ownership, Control or Influence review — and foreign limited partners in a venture cap table can complicate or block it, sometimes requiring formal mitigation instruments. This is a strong argument for sequencing civilian or SLED first.

A practical rollout plan

Months 1-3: commit and staff. The board formally commits multi-year capital against a written business case with an honest cost model. Finance builds the three-year public-sector P&L and a bid-and-proposal budget line. The specialist search for the federal leader opens — sourced from federal sales orgs at peer software companies, channel teams at the major government aggregators, business development at the primes, and agency or military backgrounds transitioning to industry, typically through recruiters with cleared and GovCon practices. Legal, engineering, and security leadership are briefed on what is coming and asked to name a federal workstream owner each. Decide your beachhead sub-market deliberately: civilian, DoD, or SLED. They are not interchangeable, and building for one does not port to the next.

Months 3-6: foundations in parallel. The leader onboards and immediately runs two workstreams at once — developing sponsoring-agency relationships, which is the gating dependency, and scoping the FedRAMP project with a 3PAO and a named compliance owner. Engineering starts the GovCloud environment build against the control baseline rather than retrofitting later. Reseller conversations open with the major aggregators for immediate vehicle access. Your own GSA Schedule offer preparation begins. GovWin IQ is stood up and the leader builds the target-agency map and opportunity list. Budget dedicated technical writing capacity for the System Security Plan — engineering-led teams chronically underestimate it and it is the first place the timeline slips.

Months 6-9: authorization underway, captures opened. Readiness assessment and SSP work is in full swing. A reseller agreement is signed. The GSA Schedule offer is submitted. The leader has identified real opportunities 18-36 months out and opened formal captures on the best one or two, each with a written capture plan and scheduled gate reviews. Industry-day attendance and RFI and Sources Sought responses begin — this is where you legitimately shape requirements before an RFP exists. Pursue a SBIR Phase I in parallel if the product fits; it is often the cleanest first dollar and the cleanest first slice of past performance, and Phase III can be sole-sourced later.

Months 9-12: sponsor locked, machine taking shape. The sponsoring agency relationship is secured and the authorization package is in agency review. Captures progress through bid/no-bid gates with teaming agreements under negotiation — getting onto the right team before competitors lock up the obvious partners is frequently the real competition. A second hire lands, either a seller or a capture and proposal capability. A first small win may arrive — a SBIR Phase I, a pilot off the reseller's vehicle, a modest OTA — valued for past performance rather than revenue, which solves the chicken-and-egg problem that nearly every RFP's past-performance requirement creates for net-new vendors.

Year two: convert. Authorization completes, the first captures reach RFP, and the proposal machine gets exercised for real — capture manager, proposal manager, technical writers, pricing and contracts lead, graphics, and subject-matter experts, running Pink, Red, and Gold Team reviews against Section L instructions and Section M evaluation criteria. Non-compliance with the instructions disqualifies you regardless of product quality. Budget for protests: a losing bidder can delay award by months.

Year three: compound. First ATOs granted, first option years exercised, past performance accumulating, and the vehicle portfolio broadening. This is where the RevOps discipline you already run commercially finally attaches — federal pipeline stages that include ATO, forecast models weighted by capture gate rather than commercial probability, and territory and quota design built around the September 30 surge.

Related questions

Should we start with SLED instead of federal?

For most companies, yes. State, local and education buyers often accept SOC 2 or StateRAMP rather than full FedRAMP, cycles run 6-12 months, and cooperative vehicles let one competitive award serve thousands of entities. It builds real past performance and government muscle at a fraction of federal capital cost.

Do we need our own GSA Schedule immediately?

No. Reseller paper through a government aggregator gives agencies a way to buy your product within weeks, versus 6-12 months for your own Schedule. The mature pattern is to lead with reseller access for transactability while pursuing your own Schedule in parallel for long-term relationship control.

How do we get past performance when we have never held a contract?

Bootstrap it. A SBIR Phase I, a small pilot transacted off a reseller's existing vehicle, an OTA prototype agreement, or a subcontract position on a prime's team all generate documentable past performance. SLED contracts count as government past performance too, and are far easier to land first.

Is FedRAMP enough to start selling?

No. FedRAMP authorization is the reusable baseline; each agency still issues its own Authority to Operate, a 3-9 month review by their Authorizing Official even with a clean package. Treat ATO as an explicit pipeline stage and never book revenue on contract signature alone.

FAQ

How long before federal revenue is material to the company?

Two to four years from a standing start. The critical path runs through hiring a federal leader, securing a sponsoring agency, completing FedRAMP, landing vehicle access, converting an 18-36 month capture, and clearing an agency ATO. These phases overlap but do not compress below roughly twenty-four months.

What does the first hire actually look like?

A federal sales leader with genuine agency relationships, capture experience, and standing inside the GovCon ecosystem — someone who has carried a federal number, knows program offices in your target agencies, understands FedRAMP and the vehicle market, and is known to the major aggregators and primes. Expect $250K-$450K OTE and 18-24 months before production.

Why does everyone sell through resellers rather than direct?

Aggregators already hold the contract vehicles, so an agency can buy through their Schedule the week you sign, rather than waiting 6-12 months for your own. They handle FAR-compliant transaction mechanics and catalog maintenance. The cost is 3-8 points of margin and some loss of direct relationship control, and the math usually favors it early.

Should federal report into the commercial CRO?

Generally no. Federal should sit under a dedicated public-sector GM with a direct line to the CEO and board visibility, because the motion needs multi-year capital protection that only that level can defend. The most common way federal dies is a quarterly-pressured commercial leader reassigning its people to help the current number.

What actually blocks a FedRAMP timeline?

Four things, in order: the System Security Plan documentation effort, which teams chronically under-resource; remediation of 3PAO findings that require real engineering rework rather than config changes; the sponsoring agency's own review queue, which runs on their schedule; and later, significant-change reviews that gate roadmap items in the authorized environment.

How does the federal fiscal year change the forecast?

Most appropriations are one-year money lost if unobligated by September 30, producing a large, predictable award surge in July, August, and late September. Plan capacity for a six-to-eight-week sprint. Also carry Continuing Resolution risk explicitly — under a CR, agencies stall net-new vendor awards.

Sources

• https://www.fedramp.gov/
• https://www.gsa.gov/buy-through-us/products-services/multiple-award-schedule
• https://www.acquisition.gov/browse/index/far
• https://sam.gov/
• https://www.usaspending.gov/
• https://www.sbir.gov/
• https://www.sba.gov/federal-contracting/contracting-guide/types-contracts
• https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
• https://dodcio.defense.gov/cmmc/
• https://www.stateramp.org/

Related on PULSE

• How do I structure a channel and reseller motion from scratch?
• How do I design comp plans for long-cycle enterprise sellers?
• How do I build a capture and proposal function inside a sales org?
• How do I forecast a pipeline where deals take two years to close?
• How do I stand up a new vertical business unit inside an existing company?