Account Strategy
Preparation before day one.
I arrive with a point of view on where to create value, who must support the decision, and what evidence could earn the sale. A territory becomes a growth opportunity when business relevance, access and technical fit come together.
My account-planning materials connect commercial potential, relationships, stakeholders and product whitespace. I developed these materials during interview processes with Microsoft, Cisco, Google and Palo Alto Networks; these companies were prospective employers, separate from my employment history.
The framework below shows how I would adapt that preparation for Armadin, then validate the plan with leadership and technical partners on joining.
One discipline.
Different industry realities.
Across my customer portfolio, the business model shapes the questions I ask. These are the strategic lenses I bring to discovery, qualification and account development.
Financial services & insurance
Business context to explore. Risk governance, third-party oversight and investment accountability.
How I approach the conversation. Map the program owner, executive sponsor and approval requirements. Connect evidence to prioritized exposure and a defensible investment decision.
Healthcare & laboratory services
Business context to explore. Service continuity, sensitive information and interconnected providers.
How I approach the conversation. Start with essential workflows and dependencies. Partner with the architect to validate environment needs and success criteria around continuity and trust.
Technology, cybersecurity & payments
Business context to explore. Platforms, APIs, integrations and partner ecosystems.
How I approach the conversation. Evaluate technical fit alongside the commercial model. Explore where embedded capabilities can support service differentiation or a new B2B revenue opportunity.
Retail & consumer services
Business context to explore. Digital commerce, distributed operations and supplier relationships.
How I approach the conversation. Connect discovery to customer-facing journeys and business-critical services. Align cybersecurity priorities with continuity, customer trust and growth.
Entertainment & hospitality
Business context to explore. Multiple brands, business units and buying teams.
How I approach the conversation. Map shared needs and local owners across cybersecurity, GRC and privacy. Build a focused entry point and an expansion plan grounded in delivered value.
Utilities & public-sector organizations
Business context to explore. Essential services, accountability and external dependencies.
How I approach the conversation. Prioritize critical operations and risk ownership. Clarify governance, procurement and the evidence required to support action.
Business services
Business context to explore. Customer commitments, information flows and operational dependencies.
How I approach the conversation. Trace the workflow the customer relies on. Translate technical requirements into a practical evaluation and measurable service outcomes.
Each account’s priorities, environment and success measures are validated directly with its stakeholders.
See this business-outcome approach in my customer storiesTurn preparation into
a commercial advantage.
Six connected workstreams. One purpose: make every first conversation relevant to the customer’s business and useful to the team building the opportunity.
Revenue continuity · Customer trust · Critical operations · Growth initiatives
Where to create value
01Read the market Connect industry pressures and company priorities to a relevant security conversation. Output · Territory thesisExplore the workstream
Before day one. Review public filings, leadership priorities, business models and signals such as acquisitions, digital initiatives or operational change. Identify the services and dependencies that matter commercially.
My working artifact. A sector map connecting business priorities, potential security concerns and discovery questions. Each hypothesis has a source and an assumption to test.
Validate on joining. Armadin’s ideal customer profile, territory boundaries, supported use cases and the priorities leadership wants the territory to advance.
02Choose accounts deliberately Prioritize business relevance and commercial scope, then choose an entry strategy. Output · Account priority mapExplore the workstream
Before day one. Build a focused shortlist using the customer problem, business criticality, likely timing, relationship strength and potential breadth across environments or business units.
My working artifact. A workbook with the priority, reason to engage, known relationships, stakeholder gaps, likely product whitespace and next research action for each account.
Validate on joining. Account ownership, existing opportunities, customer history and capacity to support an evaluation. Commercial potential becomes a forecast only through qualification.
Who makes it happen
03Map the buying team Start with executive outcomes and connect directors, practitioners and decision owners. Output · Stakeholder mapExplore the workstream
Before day one. Map likely CISO and executive stakeholders, security directors, technical owners, relevant business leaders and procurement. Separate a potential champion from a confirmed sponsor or economic buyer.
My working artifact. A role map showing each person’s priorities, influence, relationships and questions. Executive messaging connects to business exposure; practitioner discovery focuses on the environment and the evidence needed.
Validate on joining. Who owns the problem, who approves investment, who evaluates the solution and whose support is missing from the decision.
04Activate my network Use my extensive black book of contacts and networks to create relevant introductions and business insight. Output · Engagement planExplore the workstream
Before day one. Map my extensive black book of contacts and industry networks to priority accounts and buying teams. Identify trusted relationships with business leaders, cyber executives, directors, practitioners and partners. Choose a relevant direct conversation, agreed introduction or partner route, with a business reason to engage.
My working artifact. A relationship and engagement map: contact role, relationship context, relevance to the account, route to an introduction, value to offer and next action. I use the network to learn and contribute as well as to earn access.
Validate on joining. Coordinate with SDRs, marketing and approved channel or alliance teams on ownership, messaging and follow-through. My relationships with internal cybersecurity practitioners at a Fortune 100 enterprise inform practitioner questions; each new customer’s needs still require direct discovery.
What earns the decision
05Prepare technical proof Translate a security hypothesis into questions an architect and the customer can validate. Output · Draft evaluation briefExplore the workstream
Before day one. Study available product material and prepare questions on deployment, integration, permissions, data handling, authorized scope, safety requirements and evidence quality.
My working artifact. A discovery and evaluation brief connecting a business-critical environment to the security question, proposed scope and success criteria. For Armadin, I would explore how evidence of exploitable risk could support a meaningful business decision.
Validate on joining. Review fit and feasibility with the technical team, drawing on the close sales-and-architecture partnership I practice with Kristin Gunnell. Agree the customer’s evaluation and remediation ownership before making commitments.
06Build the route to revenue Connect demonstrated value to decision milestones, net new business and earned expansion. Output · Draft decision planExplore the workstream
Before day one. Outline the path from discovery to technical validation, investment case and procurement. Identify where a relevant first use case might lead to additional business units or environments.
My working artifact. A draft mutual action plan: milestone, owner, evidence required and next decision. The investment case links agreed customer priorities to validated findings and expected value.
Validate on joining. Confirm budget, buying process, commercial model and realistic timing. Track stakeholder coverage, agreed evaluation criteria and opportunities with a clear next step; measure expansion against delivered value.
A prioritized territory view, a credible access strategy and a draft path from customer problem to technical proof and revenue.
Account priorities.
Business relevance sets the priority. Relationship strength shapes how I earn access.
| Business relevance | Limited access | Established access |
|---|---|---|
| Higher | Create the entryBuild a relevant introduction or partner route. Test the business hypothesis. | Prioritize discoveryUse access to validate need, decision ownership and technical fit. |
| Unclear or lower | Research and nurtureLook for a meaningful trigger before committing selling resources. | Validate relevanceUse the relationship to learn. Confirm a real problem and fit. |
I also weigh timing and commercial scope. Access alone does not make an account a qualified opportunity.
The buying team.
I connect executive intent to the people who must validate, adopt and approve the solution.
- CISO & executive stakeholders
Business exposure, strategic priorities and investment rationale.
- Directors & program owners
Operational priorities, ownership and a champion’s plan for change.
- Practitioners & solution architects
Environment, evaluation scope, technical evidence and adoption.
- Finance, procurement & governance
Funding, approval requirements, commercial terms and timing.
The decision map is confirmed with the customer; an executive title alone does not establish buying authority.
What I bring into day one.
Where I would start
Sector priorities, a focused account shortlist, source-backed hypotheses and a clear reason to engage.
First alignment: Confirm ownership, customer fit and the team’s growth priorities.
How I would earn access
Buying-team maps connected to my black book of trusted relationships, relevant introductions, tailored opening messages and first-meeting agendas.
First alignment: Coordinate introductions, partner routes and account-team responsibilities.
How I would earn the next step
Technical discovery questions, draft evaluation criteria, decision milestones and expansion hypotheses.
First alignment: Confirm product fit and feasibility with the technical team, then validate priorities with customers.
See how the preparation translates into a customer conversation
Start with a business-critical service.
- Business hypothesis
- A retailer’s digital service may be important to revenue continuity and customer trust. Confirm its importance with the business owner.
- Opening question
- “Which customer-facing service would create the greatest business impact if disrupted, and what evidence do you need to understand its exposure?”
- Buying-team connection
- Align the CISO and digital business owner on the outcome. Involve the security director, relevant practitioners and architect in defining what to evaluate.
- Proof and decision
- Agree an authorized scope, a baseline and success criteria. Use validated findings to discuss remediation priorities and an investment case.
- Expansion question
- If the first use case demonstrates value, which related environments or business units have a similar priority?
This example illustrates the preparation method; it is not a customer result or an Armadin deployment claim.
The business-outcome discipline behind this plan is reflected in my customer stories and net new revenue results.