Your First 90 Days as Head of Public Sector: A 30-60-90 Day Operating Plan

Your first 90 days as head of public sector should not be judged by how many government logos you add to a spreadsheet. They should be judged by whether the company can now make better choices: which market to enter, which accounts deserve scarce time, who influences each purchase, what buying path is plausible, and what the team should do next.

That distinction matters because public-sector coverage can become busywork very quickly. Federal opportunities live in one set of systems and rules. States, cities, counties, school districts, and public authorities have their own procurement sites, registration requirements, calendars, and contract vehicles. A new leader can spend a quarter buying access, registering everywhere, and filling a CRM without resolving the fundamental question: where can this company credibly win?

The better mandate is to build an evidence-backed operating system. The broader public-sector sales playbook explains the complete motion. This guide focuses on the first 90 days: the sequence of decisions that turns a broad ambition into a repeatable weekly practice.

The governing principle: earn the right to scale

A new public-sector leader usually inherits pressure to show movement immediately. That pressure can produce three attractive mistakes: an enormous target-account list, a pile of data subscriptions, and activity goals disconnected from how government buys. All three make dashboards fuller. None proves that the motion is sound.

The first 90 days should instead move through three gates:

1. Days 1–30: choose. Define the market thesis, evidence standard, and initial account universe.
2. Days 31–60: test. Apply the thesis to real accounts, buying teams, and procurement paths.
3. Days 61–90: operationalize. Turn what survived the test into a repeatable cadence and an investment decision.

Each phase narrows the field. That is a feature. A credible day-90 plan should contain more reasons to stop pursuing weak accounts, not merely more reasons to add new ones.

Before day one: agree on the charter

The 90-day clock should begin with a written charter from the executive sponsor. Keep it to one page. State the business hypothesis, the markets in scope, the resources already committed, the decisions leadership expects at day 90, and the claims that still need evidence. If leadership expects immediate bookings from a new market but has not agreed on contract readiness, implementation constraints, or reference strategy, surface that mismatch now.

For federal work, the Small Business Administration advises companies to assess whether government buys what they sell and at a competitive price before pursuing contracts. The same discipline applies to larger vendors and SLED entrants. Market presence is not a strategy; evidence of buyer need and a viable path to purchase is.

• In scope: buyer types, geographies, use cases, contract sizes, and the product configuration the team can actually deliver.
• Out of scope: segments, security requirements, custom work, or contract paths the company is not prepared to support.
• Day-90 decisions: concentrate, pause, or expand; required hires; partner strategy; compliance investment; and next-quarter targets.
• Evidence boundary: distinguish confirmed public facts, buyer statements, internal assumptions, and recommendations.

Days 1–30: build the market thesis and evidence standard

The first month is about deciding what deserves investigation. Interview product, security, implementation, finance, legal, sales, customer success, and the executive sponsor. The goal is not stakeholder consensus on every account. It is a shared definition of a good public-sector opportunity and an honest inventory of constraints.

1. Define fit and disqualification criteria

Write criteria specific enough that two people could independently reach a similar decision. Useful dimensions include mission problem, use-case evidence, agency size, current system or incumbent, contract value range, implementation burden, integration needs, security posture, available contract route, relevant past performance, partner access, geography, and timing. Add explicit disqualifiers. A requirement your product cannot meet is more useful than a vague score suggesting an account is merely less attractive.

Use the SLED account-prioritization template to make these choices inspectable. A score should organize judgment, not disguise missing evidence. Preserve the source and date behind every decisive input.

2. Build the account universe from primary evidence

Start with public records before layering on commentary. For federal buyers, SAM.gov Contract Opportunities contains presolicitation, solicitation, award, and sole-source notices, and the public can search without an account. USAspending Advanced Search can be filtered by agency, recipient, award type, NAICS, time period, and other fields to examine who buys, what has been awarded, and which vendors appear. These sources do not decide fit, but they ground the thesis in observable purchasing behavior.

For SLED, resist the temptation to treat one portal as the market. NASPO maintains a directory of official state procurement websites and a separate supplier-registration directory, while warning that official state records control. California, for example, directs vendors to Cal eProcure for state bid and contracting resources. Use the relevant state and agency sources, then record where each fact came from and when it was checked.

3. Establish one account brief and one weekly cadence

Choose one shared account-brief format: buyer problem, fit evidence, current initiatives, procurement history, likely route to purchase, relevant stakeholders, incumbent or alternative, open questions, risk, source links, and recommended next action. Do not let every rep invent a private research system.

Start the weekly review now, even if the evidence is incomplete. The first meetings will expose ambiguous criteria, missing sources, and conflicting assumptions. That is the point. The day-30 gate is passed when leadership can explain why the initial accounts are in scope and what evidence would remove them.

Days 31–60: test the thesis on real buying paths

The second month is where research becomes a sales motion. Select a deliberately small portfolio that represents the most important hypotheses—not simply the most recognizable logos. Give each account a named owner and require a dated pursue, validate, watch, or pass decision with a reason.

1. Map the program, procurement, and ecosystem lanes

An org chart is not a stakeholder map. For each priority account, use three consistent lanes: program and mission, procurement and control, and ecosystem and influence. Buyer, decision-maker, security reviewer, partner, reseller, and peer are roles within those lanes. The government stakeholder-map template turns those lanes into actions and open questions.

2. Test access before a final solicitation

Public-sector selling is not synonymous with waiting for an RFP. For negotiated federal acquisitions, FAR 15.201 encourages exchanges with industry from the earliest identification of a requirement and lists market research, one-on-one meetings, presolicitation notices, draft RFPs, RFIs, conferences, and site visits among the available techniques. The rule also protects procurement integrity and requires the contracting officer to become the focal point after solicitation release.

Use that window to learn and contribute, not to seek privileged treatment. Bring a relevant point of view, answer public RFIs carefully, ask questions through the prescribed channel, and document what the buyer actually confirms. State and local rules differ, so check the applicable jurisdiction rather than importing federal practice by analogy.

3. Run the learning loop every week

For every material buyer movement—a budget item, leadership change, public meeting, grant, expiring contract, RFI, partner introduction, or posted solicitation—record four things: the source, why it matters under your fit criteria, the owner, and the next action. If the event changes nothing, say so. A signal feed without a decision process becomes another inbox.

At day 60, ask whether the team can identify a plausible problem, buying team, timing window, and procurement path for each surviving account. If not, decide whether the missing information is obtainable. Move the account to watch or pass when it is not. Unresolved curiosity is not pipeline.

Days 61–90: turn the evidence into an operating system

The final month is not a victory lap. It is the conversion of tested choices into a system other people can run. Standardize the minimum account brief, review agenda, CRM fields, decision vocabulary, and escalation path. Define which events trigger immediate review and which can wait for the weekly meeting.

1. Connect sources to the system of record

Audit the stack against the workflow. Portals, public records, market-intelligence products, partners, and internal conversations are sources. Your CRM is usually the system of record. The missing layer is often the process that applies company-specific fit, keeps evidence attached, and presents a recommended next action for a named owner to accept, change, or reject. Settle is designed as that additive workflow layer: see how source-backed signals move into action. It does not make every source or CRM unnecessary.

Only add a subscription when the team can name the decision it improves. Coverage is one possible gap. Qualification, evidence freshness, routing, and action ownership are different gaps. A tool that expands coverage while increasing manual triage may move the wrong metric.

2. Establish baselines before targets

Do not invent universal performance thresholds for a motion you have just begun. Establish a baseline, examine the trend, and set the next-quarter target from your actual capacity and cycle. Recommended operating measures include:

• Decision coverage: the share of priority accounts with a current pursue, validate, watch, or pass decision and documented rationale.
• Evidence freshness: the age and source quality of the facts that drive each decision.
• Action latency: elapsed time from a material, relevant signal to an owner decision and next action.
• Stakeholder coverage: whether each surviving account has confirmed or hypothesized contacts across program and mission, procurement and control, and ecosystem and influence, with unknowns clearly marked.
• Learning-loop completion: whether discovery and outreach outcomes change the account thesis, criteria, or next action rather than disappearing into notes.
• Sourced pipeline: opportunities connected to an observable buyer need and credible path, separated from speculative account entries.

3. Present choices, not just activity

The day-90 executive readout should make an argument. Show the original hypotheses, what the team observed, what changed, and the resulting investment choices. Recommend a primary market and use case, priority-account portfolio, capacity plan, partner strategy, compliance roadmap, and next-quarter experiments. Include the accounts and activities you recommend stopping.

Be precise about claim boundaries. A well-researched account is not a qualified opportunity. A relevant signal is not a forecast. A recommended next action is not helpful if not actioned on. An improving operating metric is not a guaranteed revenue outcome. Credibility comes from preserving those distinctions.

The complete 30-60-90 day scorecard

What not to do in the first 90 days

• Do not register everywhere. Register where an approved account and route require it. Maintain the resulting credentials and deadlines deliberately.
• Do not confuse a database export with a territory. A territory is a set of choices backed by fit, capacity, access, and timing.
• Do not wait for posted RFPs to learn the market. Use lawful, early exchanges and public evidence while buyers are still defining the path.
• Do not hide uncertainty inside a score. Label hypotheses and missing evidence. False precision makes weak accounts look defensible.
• Do not outsource the thesis to a reseller or consultant. Partners can provide access and a contract path; your team still owns buyer understanding, positioning, and learning.
• Do not make revenue the only day-90 test. Revenue matters, but a new motion may not mature inside one quarter. Judge whether the team created evidence, focus, access, and a repeatable process.

The weekly meeting that makes the plan real

A plan becomes operational when it changes Monday morning. Run a short weekly meeting around decisions, not updates: what changed in the buyer environment; which accounts moved up, down, in, or out; what evidence supports the change; which next actions have owners and dates; and what the team learned about its fit criteria. The detailed government sales operating cadence provides the daily and weekly structure.

By day 90, the most important outcome is not that the organization knows more about government. It is that the organization behaves differently: it chooses accounts with evidence, engages while there is still time to shape a path, preserves the buyer context behind every action, and learns fast enough to stop weak pursuits. That is the foundation a public-sector team can scale.