Methodology

I approach presales as a repeatable operating model. The goal is to improve clarity for the customer, reduce risk in the buying process, and position a solution in a way that is both technically credible and commercially persuasive.

1. Discovery

I begin by understanding:

• the business driver behind the initiative
• the pain points in the current state
• the operational or regulatory constraints
• the stakeholders involved in the decision
• the criteria that will define success

This prevents premature solutioning and helps separate symptoms from root problems.

2. Problem Framing

After discovery, I translate the findings into a structured problem statement. At this stage I want the customer and internal account team to be aligned on:

• what problem is actually being solved
• which outcomes matter most
• where the real blockers are
• what must be proven during evaluation

Good framing improves solution fit and sharpens executive conversations.

3. Solution Mapping

I then map the requirement to a practical solution path. Depending on the opportunity, this may involve:

• architecture options
• platform fit assessment
• integration and governance considerations
• implementation assumptions
• risk and dependency identification

This stage is where technical breadth becomes commercially useful.

4. Technical Storytelling

A solution only lands when it is communicated correctly. I tailor the message for different audiences:

• Executives need business outcomes, risk posture, and strategic rationale
• Business sponsors need process relevance, usability, and expected impact
• Technical teams need architecture clarity, feasibility, and implementation confidence

I treat narrative design as part of solution design, not as an afterthought.

5. Value Articulation

Before a recommendation is complete, I work to make the value legible. That can include:

• cost or efficiency logic
• risk reduction
• speed to insight or delivery
• decision quality improvements
• scalability and future readiness

The principle is simple: buyers should be able to explain back to themselves why the recommendation matters.

6. Deal Support and Objection Handling

Late-stage support usually requires precision. This can include:

• clarifying requirements and assumptions
• addressing technical objections
• refining scope boundaries
• strengthening implementation credibility
• helping internal sales teams defend the narrative

This is often where strong presales work materially improves deal confidence.

Frameworks and Habits I Value

While each engagement is different, my working style aligns well with structured presales habits such as:

• value-based selling
• disciplined qualification
• stakeholder mapping
• evidence-backed architecture recommendation
• executive-friendly communication

What Good Looks Like

A successful presales engagement should leave the customer with four things:

1. a clearer understanding of the real problem
2. a credible path forward
3. confidence in the technical recommendation
4. a business rationale strong enough to support a decision