Oral Presentations and Technical Demos for Software Companies: How Evaluators Score the Live Part

2026-10-22#saas #federal-market

By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.

More federal software buys now include a live component: an oral presentation, a product demonstration, or a scenario the agency asks you to work through in front of its evaluators. For a software company this can be an advantage. A working product shown well is more persuasive than fifty pages describing it. It’s also where proposals that read well on paper come apart, because the evaluators are scoring what they see against criteria you may not have read closely.

This guide explains how oral presentations fit into a federal source selection, what the rules allow, and how to prepare a team and a demo for one.

What the FAR says about oral presentations

Under FAR Part 15, an agency may use oral presentations to replace part of the written proposal or to add to it. The solicitation sets the terms. It typically describes:

the kind of information to be presented orally, and how it relates to the evaluation factors
who must present, often named key personnel rather than a sales team
any limits on slides, handouts or other written material
the date, time, location and length of the session
whether evaluators may ask questions, and on what topics

Some things can’t be done orally. Certifications, representations and the signed offer, including any exceptions you take to the government’s terms, must be in writing. And if something you say during the presentation is meant to become a contract term, it has to be put in writing too.

The agency also decides how to keep a record of the session: video, audio, written notes, or a copy of the slides you used. That record goes into the contract file, and it’s what evaluators and any later reviewer rely on, so treat the room as if everything you say will be written down.

The FAR is being rewritten through the Revolutionary FAR Overhaul, and many agencies now apply the new text by class deviation, so section numbers and wording may differ. Check the solicitation and the current FAR text for the rules that apply to a given buy.

Questions, clarifications and discussions

The rules on questions matter more than most first-time bidders expect. If evaluators use the session to let you revise your proposal, rather than just clarify what you’ve said, that’s a discussion, and the agency must then follow the rules for discussions with every offeror in the competitive range. Agencies that want to avoid that often limit what evaluators may ask, or allow only clarifying questions.

In practice: answer the question asked, don’t volunteer changes to price or terms, and don’t treat a follow-up question as an invitation to renegotiate. If you’re unsure whether an exchange is a clarification, ask the contracting officer afterwards in writing.

Product demonstrations and scenario challenges

Many software evaluations now ask you to demonstrate the product rather than describe it, sometimes against a scenario the agency hands you on the day. Formats vary:

Scripted demo. You show specific functions listed in the solicitation, in order, within a time limit.
Scenario challenge. The agency gives you a problem or a dataset, sometimes with little notice, and evaluators watch your team solve it in the product.
Hands-on evaluation. Agency users work in a test environment you provide, against a checklist.

Read the instructions as closely as you would read Section L. If the solicitation says the demo must use the production version, a staging build with unreleased features can count against you. If it names specific functions, show each one, in the order listed, and say aloud which requirement you are meeting so the evaluator can note it. Evaluators score against the stated factors in Section M, not against how impressive the product is in general.

Plan for the environment as well as the product. Government networks may block the domains, ports or browser features your demo needs, and some sessions are run in a government room on government equipment. Ask in advance, bring an offline fallback, and rehearse on a locked-down machine.

Preparing the team

Who presents matters. Solicitations that require key personnel to present usually mean it: if your proposal names a program manager and a technical lead, they should be the ones answering questions, not a sales engineer the agency will never see again.

Rehearse against the factors. Build the presentation outline from the evaluation criteria, one section per factor, and have someone outside the team score a dry run against them.
Time it. Sessions are often strictly timed, and running out of time before the last factor means it goes unscored.
Prepare for security and compliance questions. Evaluators may ask how you handle data, where it’s hosted, and what your FedRAMP, Section 508 or CMMC status is. Be precise. A self-attested status is not the same as an authorization or a third-party assessment, and evaluators know the difference.
Keep claims consistent with the written proposal. Anything you say that contradicts your written volumes creates a question about which one the agency should rely on.

After the session

Write down what was asked and how you answered while it’s fresh. If you lose, those notes make the debriefing far more useful, because you can ask how the oral portion was rated and match the answer to specific moments. If you win, they help the delivery team understand what the agency was promised in the room.

To see where your company stands on the factors evaluators tend to weigh, score your company’s federal readiness.

The CMMC brief

What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.