Public sector and GovTech · Live AI coaching
AI coaching for selling to government, municipalities, and public institutions
Amotions AI coaches reps who sell to cities, counties, universities, transit and parking authorities, and utilities. During live Microsoft Teams, Zoom, Meet, and phone calls it privately suggests the next question: budget cycle, funding source, buying path, who else must agree. It never joins as a bot, gives no procurement advice, and never coaches around an RFP quiet period.
Public-sector deals move on fiscal years, council calendars, and procurement rules, and one discovery call can decide whether a deal lands this year or in two. Amotions helps every rep, including the one who started last month, ask the right questions, handle “we have to go to RFP” calmly, and leave each call with a real next step.
Built for teams where every customer conversation matters. Published October 10, 2026 · Pianpian Xu Guthrie
Discovery with a department head
Customer“Honestly, our parking enforcement process is a mess, but I don’t know if this is the year to fix it.”
Suggested next move
Ask what “a mess” looks like for residents and staff today, then ask when the next budget is built and who would need to agree to fix it.
Buying path
Customer“I’d have to check with procurement on how we’d buy something like this.”
Suggested next move
Ask if they know the usual path for a purchase this size, whether procurement could join a short call, and what the buyer would need from you to start that conversation.
Private by design
Read the Trust CenterNever joins as a bot
No extra attendee, no recording notice from a meeting bot. The coach runs beside the call, not in it.
Private to the rep
Prompts appear on the seller’s own screen. The prospect, client, or family never sees them.
Your conversations stay yours
Customer conversations are never used to train third-party foundation models.
Works where you already talk
Zoom, Microsoft Teams, Google Meet, phone on speaker, and dialers, through the desktop app or a browser tab.
What this page covers
- Private live prompts on Microsoft Teams, Zoom, Meet, and phone calls. Amotions never joins as a bot, and the agency never sees it.
- Discovery that maps the budget cycle, funding source, procurement path, and every stakeholder, not only the champion.
- Calm, rule-aware responses to “we have to go to RFP,” “it’s not in this year’s budget,” and “we’d need a cooperative contract.”
- Faster ramp for new reps: AI roleplay with department-head, IT, and procurement personas, then scores against your own rubric.
Where revenue leaks
Where public-sector sales calls break down
Most lost public-sector deals are not lost on the demo. They stall because a rep skipped the budget question, talked only to the champion, or treated a procurement rule like an objection.
Single-threaded on the champion
A program manager loves the product, but nobody asked who in IT, finance, procurement, or legal has to agree, or when the council or board meets. The deal stalls months later.
Missing the budget cycle
The rep learns about the fiscal year after the budget is set. A deal that needed one question in the first call now waits a full year.
Treating “we have to go to RFP” as a no
Some reps give up. Others push for workarounds the agency cannot accept. Both lose the chance to understand the process and prepare properly.
Commercial habits that do not fit
End-of-quarter discounts, urgency closes, and gifts that are routine in commercial sales can be unwelcome or prohibited with a public buyer.
Slow ramp on a long cycle
A new rep can spend months before seeing a deal close, so they get little feedback. Managers cannot sit in on every call, and bad habits form quietly.
How Amotions helps
Give every public-sector rep support in the moments that matter
Amotions covers the whole conversation loop: practice before the call, private guidance during it, and scored feedback after it, all built on your own playbook.
During the conversation
Real-time guidance on calls and meetings
A private overlay listens and surfaces one next question, response, or next step at a time, drawn from your playbook. The customer never sees it, and no bot joins the call.
How real-time guidance works →Before the conversation
AI roleplay for practice
Rehearse the calls your team loses most often against AI customers built from your own objections and scenarios, then get scored on your criteria.
AI roleplay →After the conversation
Post-call feedback and coaching insights
Every conversation is scored against your process, with the one moment worth practicing next. Managers see where the team drifts without listening to every call.
Post-call scorecards →
During the conversation
What Amotions does during a public-sector sales call
Amotions listens alongside the rep and shows short private prompts tied to the call type and your own playbook. The agency never sees them, and Amotions never speaks.
- 1
Load your playbook and rules
Upload your discovery questions, qualification framework, stakeholder map, approved answers on security and contracts, and the procurement and ethics rules your company wants every rep to follow.
- 2
Track the buying path
As the buyer talks, Amotions notices what is still unknown, such as the budget cycle, funding source, procurement route, or a missing stakeholder, and suggests the next question.
- 3
Cue rule-aware responses
When a buyer says “we have to go to RFP” or “it’s not in the budget,” the rep gets a prompt to ask about process and timing, not to push for a workaround.
- 4
Notice hesitation and new voices
Hesitation, a change in tone, or a new stakeholder joining the call triggers a cue to slow down, check understanding, and ask what that person needs.
- 5
Score the call and assign practice
After the call, the rep gets a transcript, a score against your rubric, and one roleplay focus for the next call.
Example in-call guidance
Illustrative coaching across a public-sector sales cycle
Examples of how Amotions might guide a rep. Real prompts come from your own playbook, approved answers, and the rules you load, not from Amotions.
Illustrative coaching examples for this industry. Not recorded customer calls, compliance advice, or performance claims. Amotions does not speak to buyers; the professional stays in control. Nothing here is procurement, legal, or ethics advice; reps follow each agency’s procurement rules.
Discovery with a department head
Customer: “Honestly, our parking enforcement process is a mess, but I don’t know if this is the year to fix it.”
Private prompt
Ask what “a mess” looks like for residents and staff today, then ask when the next budget is built and who would need to agree to fix it.
The problem and the budget calendar together tell the rep whether this is a this-year deal or a next-cycle plan.
Buying path
Customer: “I’d have to check with procurement on how we’d buy something like this.”
Private prompt
Ask if they know the usual path for a purchase this size, whether procurement could join a short call, and what the buyer would need from you to start that conversation.
Procurement is a stakeholder, not an obstacle. Learning the path early prevents a surprise late in the cycle.
IT joins the call
Customer: “I’m from IT. Before we go further, where is the data stored and who can see it?”
Private prompt
Acknowledge Dana, answer only with your company’s approved security wording, offer the formal security review, and ask what else IT needs to see.
Improvised security answers create risk. A short, approved answer and a clear review process build trust with IT.
“Not in this year’s budget”
Customer: “I like it, but it’s not in this year’s budget.”
Private prompt
Thank them for saying so. Ask when next year’s budget requests are due, whether any other funding source could apply, and what they would need to put this in the request.
Budget timing is a fact about the agency, not a rejection. A rep who learns the calendar can help the buyer plan.
“We have to go to RFP”
Customer: “Anything at this size, we have to go out to RFP.”
Private prompt
Accept the process. Ask about the expected timeline and who the procurement contact will be, and confirm you will follow the solicitation’s contact rules once it is released.
Respecting the process keeps the relationship clean. Pushing for a workaround can disqualify a vendor.
Pilot proposal
Customer: “Could we try it at one garage first and see?”
Private prompt
Ask what a successful pilot would show them, who would decide, by when, and whether a pilot is something they can do under their own rules before agreeing on scope.
A pilot without written success criteria and a decision date often never ends. The agency decides what it is allowed to run.
Cooperative contracts
Customer: “Are you on any cooperative contracts we could piggyback on?”
Private prompt
Answer only with the contracts your company actually holds, then say whether the agency can use one is their procurement office’s decision, and offer to send the details to them.
Overstating contract access is a fast way to lose trust. Facts plus a referral to procurement keep the rep in role.
Next step and board timing
Customer: “If we go ahead, it probably needs to go to the council.”
Private prompt
Ask when the council meets, what the staff report or agenda item needs to include, and what the buyer needs from you by which date. Confirm the next call before ending.
Council and board calendars set the real close date. Working back from them turns “probably” into a plan.
Objections
Common public-sector buyer objections and coaching moves
Public buyers say no for structural reasons more often than personal ones: budgets, rules, and risk. Coaching helps reps understand the structure and respond with questions, never with workarounds.
“We have to go to RFP for this.”
Suggested next move: Accept it. Ask about timing, the procurement contact, and what the buyer can share before release, and say you will follow the solicitation’s contact rules once it is open.
It shows you understand public procurement and keeps your company eligible to respond.
“It’s not in this year’s budget.”
Suggested next move: Ask when budget requests are due, which kind of funding might fit, and what would make the request easy for them to justify. Offer to help with factual information.
It turns a “no” into a dated plan for the next cycle without pressuring the buyer.
“We’d need to piggyback on a cooperative contract.”
Suggested next move: Share the cooperative contracts your company holds, if any, and say the agency’s procurement office decides whether one can be used. Offer to send details to that office.
Facts plus deference to the agency’s process avoids overpromising a path the buyer cannot take.
“IT will never approve another cloud tool.”
Suggested next move: Ask what IT usually needs to review, offer your company’s formal security review, and ask whether IT could join a short call early.
Bringing IT in early replaces a late veto with a list of requirements.
“Call me after the election.”
Suggested next move: Agree, then ask what might change after it, who else on staff follows this project, and whether a short check-in on a specific date works.
It respects the timing while keeping the opportunity tied to real people and dates.
“Which other cities like ours are using this?”
Suggested next move: Share only references your company has permission to name. If there are none that fit, say so and offer a pilot scoped with clear success criteria.
Public buyers often call their peers. An honest answer survives that call; an exaggerated one does not.
Before the conversation
AI roleplay for public-sector sales training
New reps can rehearse the calls that slow down public-sector deals with AI buyer personas before they happen for real. Feedback scores against your own rubric.
A university parking director likes the idea but says the budget was set months ago and procurement “makes everything slow.”
Practice goal: Learn the budget calendar and procurement path without pushing, and agree on a dated next step.
Feedback focus: Discovery depth, listening, and whether the call ended with a specific next step.
A city IT manager joins a call and asks hard questions about data storage and access.
Practice goal: Answer only with approved security wording, offer the formal review, and learn IT’s requirements.
Feedback focus: Accuracy against approved answers, calm tone, and whether IT’s needs were captured.
A transit authority buyer says the purchase must go to RFP and asks whether you can “help shape it.”
Practice goal: Stay inside the agency’s rules, ask about process and timing, and follow your company’s policy on what you can and cannot do.
Feedback focus: Rule awareness, no workaround suggestions, and a clean next step.
A new program manager inherits your contract at renewal and is not sure it is worth keeping.
Practice goal: Rebuild the value in the new manager’s terms and learn the renewal and budget timeline.
Feedback focus: Questions before claims, stakeholder mapping, and timeline clarity.
After the conversation
Post-call scoring for public-sector teams
After each call, Amotions provides a transcript, a score against your rubric, and specific feedback: whether discovery covered budget cycle, funding, buying path, and stakeholders, how procurement moments were handled, and whether the call ended with a dated next step.
Scoring measures how the conversation was run. It does not predict awards or say whether a deal will close. Managers see patterns across reps and assign roleplay on the conversation types each person finds hardest, which helps new reps get feedback long before their first deal closes.
Outcomes
What your team can measure
Teams can measure impact through the numbers they already track. Set a baseline before the pilot and compare the same measures after; Amotions does not promise a specific lift.
- Time for a new rep to run a discovery call on their own
- Discovery calls that capture budget cycle, funding source, and buying path
- Opportunities with a named next step and date after every call
- Pilot proposals with written success criteria agreed by the buyer
- Multi-stakeholder calls where IT, procurement, and finance questions were answered or routed
- Manager review coverage across the team
- Rubric scores on “we have to go to RFP” and “not in the budget” moments
Who it is for
Who is public-sector sales coaching for?
This page is for vendors that sell to public institutions: the reps on the calls and the leaders responsible for how those calls go. It is communication coaching for your sales team, not a procurement, bid, or compliance tool.
GovTech and B2G account executives
AEs selling software, hardware, or services to state and local government, higher education, transit and parking authorities, and utilities, on long cycles with many stakeholders.
New reps ramping into public-sector territory
Reps who come from commercial sales and need to learn fiscal years, procurement thresholds, cooperative contracts, and quiet periods before they cost a deal.
SDRs and business development reps
Reps booking first meetings with department heads and program managers, who need to qualify timing and buying path without sounding like a commercial cold call.
Sales leaders growing a public-sector team
Leaders scaling from a handful of reps to a larger team who cannot sit in on every call and want consistent discovery, cleaner forecasts, and shorter ramp.
Not the right page if
- Teams looking for a CRM, bid-management, proposal, or RFP-writing tool. Amotions coaches live conversations and runs beside those tools.
- Anyone looking for procurement, legal, lobbying, or ethics advice. Those questions go to your counsel and the agency’s procurement office.
- Agencies or employees looking for software to run their own procurement. Amotions coaches vendor sales teams.
- Federal contracting teams that need FedRAMP-authorized tools, since this site does not list a FedRAMP authorization for Amotions. Ask for current status in a security review.
Conversations
What conversations do public-sector sales teams have?
Public-sector deals are a long run of different conversations with different people. Each one has its own job, so coaching follows the conversation type rather than one commercial script.
Discovery with a department head or program manager
Learning the problem in the agency’s words, who it affects (residents, students, riders, staff), what has been tried, and what would have to be true for anything to change.
Multi-stakeholder calls
IT asks about security and integration, procurement asks about the buying path, finance asks about funding, and someone mentions the council or board calendar. Each question needs an answer or an owner.
“It’s not in this year’s budget”
Finding out when the budget is built, whether operating, capital, or grant funding could apply, and what the buyer needs to bring the request into the next cycle.
“We have to go to RFP”
Understanding the agency’s procurement path and timeline, what the buyer can share before a solicitation is released, and how contact rules change once it is open.
Cooperative contracts and piggybacking
Answering “are you on a cooperative contract?” with facts about your own contracts, and leaving the decision about whether the agency can use one to the agency.
Pilot and proof-of-concept proposals
Scoping a pilot the agency is allowed to run, with written success criteria, a decision date, and a clear path to a purchase if it works.
Renewals and expansions
Renewal conversations with a new program manager, a changed budget, or a procurement office that wants to re-bid, where the value has to be shown again in the agency’s terms.
Your playbook
Train your public-sector playbook into Amotions
Amotions uses what your company loads. It does not invent procurement rules, contract vehicles, or security answers. Load the materials your team already trusts.
Discovery and qualification framework
The questions your best reps ask about the problem, budget cycle, funding source, procurement path, stakeholders, and council or board timing.
Approved security and contract answers
Your company’s approved wording for security, data handling, and the contracts you actually hold, so reps never improvise those answers.
Procurement and ethics rules to remind
Your company’s rules on quiet periods, contact during open solicitations, gifts and meals, and lobbying registration. The coach can remind reps of them; your counsel owns them.
Objection approaches by segment
How your team handles “we have to go to RFP,” “not in the budget,” and “we need a cooperative contract” for cities, universities, transit and parking authorities, and utilities.
Scoring rubric
The behaviors you want on every call: problem in the buyer’s words, full buying path, every stakeholder named, rules respected, and a dated next step.
Works with the sales methodology you already use
Amotions is configured around your team’s framework and stages, not a built-in one. Qualification fields, discovery questions, and scoring criteria come from the method you already teach.
- MEDDPICC
- SPIN Selling
- Challenger
- Sandler
- BANT
- Your own playbook
Signals
What communication and behavioral signals matter?
Public buyers show interest through process, not enthusiasm. Amotions helps reps notice those moments and ask the next practical question.
Signals public-sector reps should not miss
Asks what a budget request or cost estimate would need to include
Prompts the rep to ask when requests are due and who reviews them, and to offer factual information for the request.
Offers to introduce procurement, IT, or finance
Cues the rep to book that call now and ask what each person will want to know.
Mentions a council, board, or committee meeting date
Reminds the rep to work back from that date: staff report, approvals, and what the buyer needs from you.
Asks how a pilot would work or what it would cost to start small
Prompts the rep to ask for success criteria, a decision owner, and a decision date before agreeing to scope.
Asks for documents to share internally, such as security answers or a product overview
Cues the rep to ask who will read them and what decision they support, then confirm a follow-up date.
Emotional signals on public-sector calls
Public-sector buyers carry risk in public. A program manager who champions the wrong vendor can face questions from a council, an auditor, or the press. That shows up as caution: careful wording, long pauses, “I’d have to check,” or a sudden shift to procedure. Amotions picks up on hesitation and tone changes and cues the rep to slow down and ask what the buyer is worried about.
Stakeholders on the same call often want different things. IT wants fewer risks, finance wants predictable costs, and the program team wants the problem solved. Prompts help reps notice when one voice goes quiet and invite that person back in.
Behavioral signals across public-sector calls
Across a long cycle, patterns matter: a buyer who avoids the budget question, a stakeholder who never joins, or a timeline that slips at every call. Amotions surfaces those points in post-call summaries so the rep and manager can see where the deal really stands.
On the rep side, scorecards show talk-time balance, whether discovery covered budget cycle, funding, buying path, and stakeholders, and whether every call ended with a dated next step. Managers coach the habits that slow deals down instead of guessing from the forecast.
What they see
What the public-sector rep actually sees
The agency never sees or hears Amotions. The rep sees short prompts in a private overlay on their own screen while they run the call.
Short cues, not a script
A reminder to ask about the budget calendar, a missing stakeholder, or the procurement contact. A few words to glance at, not a paragraph to read aloud.
Never a bot in the meeting
Amotions does not join Microsoft Teams, Zoom, or Meet as a participant. Buyers and other attendees do not see it.
Rep stays in control
Reps can ignore any prompt and lower how often suggestions appear, from 1 to 12 per minute. The overlay can sit on a second monitor and stays hidden during screen share.
No procurement or legal answers from the AI
Amotions does not decide what an agency’s rules allow. Prompts point back to your approved wording, your company’s policies, and the agency’s procurement office.
Workflows
Which public-sector sales workflows are supported?
Most public-sector selling happens on Microsoft Teams, with some Zoom, Meet, and phone calls. Amotions runs beside the tools your team already uses and does not replace your CRM or bid-management system.
Microsoft Teams calls
There is no native Teams app. Teams works through the Amotions Desktop App and Web Real-time AI: on Windows, share the entire screen with audio; on a Mac, join Teams in Chrome and share that tab with audio. Amotions never joins as a bot.
Zoom and Google Meet
A native Zoom Marketplace app on desktop Zoom, plus the Desktop App or Web Real-time AI for Zoom in a browser and for Google Meet.
Desk phone and cell phone calls
Run the Desktop App on a Mac or Windows computer and put the call on speaker or through computer audio. Real-time AI on a mobile phone itself is not available.
AI roleplay for new-hire ramp
Practice discovery, IT and procurement calls, and RFP and budget conversations with AI buyer personas before live calls.
Post-call scoring and uploads
Score coached calls against your rubric, or upload recordings for scoring. Recording and consent follow your company’s policy and the laws that apply to each call.
Evidence
Customer evidence for public-sector sales
Amotions only cites named customer stories that are published on this site. There is no published named public-sector sales customer story yet.
No named customer story is published for public-sector sales yet. The conversation examples on this page are illustrative enablement content, not case studies. See the customer-stories hub for published proof in other verticals, or book a demo to discuss a pilot.
Published customer stories →Pilot
Start with a focused pilot
Choose one team, one call type, and a small set of measurable outcomes. Configure Amotions around your existing playbook, establish a baseline, and evaluate how live guidance, practice, and post-call coaching affect performance.
- 1
Define the team and conversation type
Pick one group and one call that matters, such as first inquiries, consults, or renewals, and agree on the numbers you already track.
- 2
Configure guidance around your playbook
Upload your scripts, approved answers, objection responses, and scoring rubric. Calibration typically takes about a week.
- 3
Review adoption, quality, and outcomes
Compare conversation scores and your business metrics against the baseline, then decide whether to expand.
FAQ
Frequently asked questions
Amotions coaches how your reps run conversations. It gives no procurement, legal, or ethics advice. Reps follow each agency’s procurement rules, including RFP quiet periods (no contact outside the designated procurement contact during an open solicitation), gift and ethics rules, and lobbying registration where it applies. The coach can remind reps of rules you load; it never coaches around them, and it makes no claims about winning contracts.
What is the best AI sales coaching for GovTech and public-sector sales teams?
Look for coaching that works during live calls on the platforms public buyers use, especially Microsoft Teams, and that runs on your own playbook. Amotions gives reps private live prompts, AI roleplay with department-head, IT, and procurement personas, and post-call scores against your rubric. It never joins as a bot and gives no procurement advice.
Does Amotions work on Microsoft Teams calls with government buyers?
Yes, as a private overlay. There is no native Teams app. On Windows, reps share the entire screen with audio to the Desktop App or Web Real-time AI; on a Mac, they join Teams in Chrome and share that tab with audio. Amotions never joins the meeting, and the agency does not see it.
How can we shorten ramp time for new reps selling to government?
Give new reps practice and feedback before their first deal closes. With Amotions they rehearse discovery, IT, procurement, and budget conversations in AI roleplay, get private prompts on live calls, and receive scores against your rubric after each call, so managers coach specific habits instead of waiting months for results.
Can AI coaching help reps during an RFP quiet period?
It can remind reps of the contact rules your company loads, such as speaking only with the designated procurement contact once a solicitation is open. It never suggests contacting evaluators or end users outside those rules. Amotions gives no procurement or legal advice; your counsel and the agency’s rules decide what is allowed.
Will Amotions help us win more government contracts?
Amotions does not promise contract awards, bid outcomes, or renewals. It helps reps run better conversations: fuller discovery, every stakeholder named, rules respected, and a dated next step after each call. You measure the results against your own baseline.
Is Amotions FedRAMP or StateRAMP authorized, or SOC 2 certified?
This site does not list a FedRAMP, StateRAMP, or CJIS authorization or a SOC 2 report for Amotions. Coaching workloads run in isolated Google Cloud environments with encrypted transmission and storage. If your review requires a specific authorization, ask for current status during a security review.
Is Amotions a CRM, bid-management, or RFP-writing tool?
No. Amotions coaches live conversations and scores them afterward. It does not track bids, write proposals, or answer RFPs. It runs beside your CRM and bid-management tools.
Does the agency know Amotions is on the call?
Amotions does not join the call, speak, or appear to attendees. The prompts are visible only to your rep. Whether to disclose recording or AI assistance is set by your company’s policy, the agency’s policy, and the consent laws that apply to the call.
See what better live guidance could do for your team.
Bring your discovery questions and the objection your reps hear most, whether that is “we have to go to RFP” or “not in this year’s budget.” We will show private live prompts on a Teams call, AI roleplay with a department-head persona, and a score against your rubric. Playbook-trained custom agents are included on every paid plan, from Starter up.
Never joins your calls as a bot · Start free on Basic