The setting
makes security systems for organizations that run many sites. Its record video on the camera and copy it to the cloud.
Discovery speed is pulling against the need to keep every buyer commitment grounded in the call record.
SLED sellers need faster follow-up after complex calls, while account records must preserve the evidence behind budget, authority, and timing claims.
Who you’d be doing this for
“The board asked what we actually need by Friday, and I’m still chasing answers from three people.”
Harald Lindqvist · Director of Security · a character in this brief
Leads a school district security program and must align operational needs with procurement and IT stakeholders.
What is at stake
Discovery details are being rebuilt from scattered notes after customer calls. You must decide how far a draft next step goes before the seller has checked it against the call record in Salesforce and Outreach.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- source-linked fields vs. free-form seller notes
- structured Salesforce data vs. seller review time
- partner urgency vs. qualification completeness
- repeatable workflow vs. public-sector nuance
Why Verkada
Verkada Cameras depends on credible discovery across public-sector buying cycles where camera scope, procurement, and partner involvement move together.
Written with these in mind
Not your kind of problem? 77 more at Verkada, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Verkada. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Federal Enterprise Account Executive (U.S. Navy) (opens in a new tab)
- Identify operational champions, economic buyers, resource sponsors, acquisition stakeholders, technical authorities, and budget timelines required to move opportunities from pilot or installation-level requirements to regional and enterprise-scale adoption.
- Mentor and educate Verkada sales, engineering, product, channel, and leadership teams on Navy organizational structure, culture, mission priorities, acquisition practices, and customer engagement.
- Regional Sales Manager, Mid-Market, Austin (opens in a new tab)
- Enterprise Account Executive (Washington - SLED) (opens in a new tab)
- This includes prospecting and outreach to new local/education business opportunities providing product demos, product trials, and strategic negotiations with customers and channel partners
- This includes identifying customers’ goals and requirements, including budgetary constraints and key decision makers
- Mid-Market Manager, France (opens in a new tab)
- VU Athlete (opens in a new tab)
- Learn how to prospect, cold call, and book meetings with business leaders
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on committing to a deal before it checks out.
Strategic sellers are revisiting call records because critical qualification details never reach Salesforce cleanly.
You must decide at which point between the call record and the Salesforce deal record a seller has to step in, and which MEDDPICC fields and buyer promises the AI is allowed to fill before that point.
Commercial sellers are rebuilding discovery context after calls, and the next conversation can chase the wrong fleet problem.
You have to decide where the AI stops reading a discovery call and where the seller takes over deciding which fleet problem the next step pursues in Salesforce.
Pilot opportunities are carrying conflicting account context across Salesforce and your project tool after discovery calls.
You have to decide whether the system or the seller on the call settles which version of the buyer's workflow and agreed next step becomes the Salesforce record.
The same setting, from another role
Each is set around Verkada’s Verkada Cameras, written for a different role. They’re separate briefs, not the same scenario.
Renewal context is split between Salesforce and the camera platform, so risks can surface after the customer has already formed an opinion.
You have to decide where the ranking stops and the CSM's read of a low-usage account begins, before anyone contacts a security manager.
Recurring false-alarm complaints are arriving through different partner and ordering surfaces without a shared evidence trail.
You must decide what the system groups, what product managers verify, and what stays out of roadmap evidence.
Firmware findings are being reopened because the evidence needed to judge them arrives in separate places.
You must decide where the routing of a finding hands over to the security engineer, once the evidence from AWS Athena and Querybook is gathered and an owner is proposed.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make the background systems nobody sees behave dependably even under heavy, high-volume real-world load.
Eleven of the 18 committed workflows still need manual follow-up to provision accounts or hand over equipment, and hiring dates are fixed.
You have to weigh a faster launch against the risk of wrong access or a dropped handoff.
Deal managers are opening dozens of document views to infer which reviewers are engaged.
You have to weigh a faster deal signal against permission-safe visibility.
Incorrect confirmations are sending patients into clinic callbacks and invalid appointment slots.
You have to weigh rapid restoration against the proof needed before changing a live scheduling workflow.
