Approach
Develop the people, processes and systems that support technical sales.
Every technical sales organisation develops differently. The appropriate combination of training, coaching, sales processes and software depends on your product, customers, team and existing technology environment.
My approach begins with observing how your organisation currently works, identifying where improvements would deliver the greatest value and implementing solutions within that environment.
I combine enterprise sales leadership, technical sales experience and hands-on software engineering throughout this process.
01 / Observe
Understand customer conversations, live opportunities and existing systems.
02 / Diagnose
Identify capability gaps, recurring challenges and operational bottlenecks.
03 / Design
Determine the appropriate combination of people, processes and technology.
04 / Implement
Coach salespeople, configure platforms and engineer custom solutions.
05 / Measure
Evaluate effectiveness and refine the implementation.
Continuous improvement informed by real sales activity.
01 / Observe
Understand how your organisation currently works.
I start by observing the activities your team is already doing, including customer conversations, hiring interviews, technical evaluations, opportunity reviews and internal discussions.
These activities reveal how your team understands customer requirements, applies technical knowledge, makes commercial decisions and progresses opportunities.
I also examine the existing sales technology and workflows to understand how information is captured, shared and used throughout the organisation.
Areas of observation
- Founder-led and AE-led customer conversations.
- Technical discovery and product demonstrations.
- Customer evaluations and implementation discussions.
- Hiring, onboarding and salesperson development.
- CRM, conversation intelligence and internal knowledge systems.
- Handoffs between sales and engineering.
This establishes a practical understanding of your product, customers, team capabilities and existing operating environment.
buyer · 00:14
“Our engineers can build this internally. Why would we add another vendor?”
founder · 00:41
“Who would be responsible for maintaining that system once it's in production?”
- Buyer signal
- Build-vs-buy evaluation
- Founder insight
- Operational ownership
- Discovery objective
- Understand ongoing engineering responsibilities
- Trainable skill
- Implementation discovery
02 / Diagnose
Identify where additional capability would make the greatest difference.
I examine the observations to understand which challenges are related to salesperson knowledge, commercial judgment, technical understanding, existing processes or limitations in the supporting software.
The objective is to identify the underlying causes of recurring problems and establish which improvements would have meaningful commercial or operational value.
| Observation | Potential underlying cause | Improvement opportunity |
|---|---|---|
| AEs regularly request founder support during discovery | Technical or commercial knowledge remains concentrated with the founder | Targeted coaching and knowledge transfer |
| Technical evaluations have inconsistent success criteria | Customer requirements are not consistently established | Evaluation methodology and workflow improvements |
| Engineers repeatedly answer similar customer questions | Validated technical knowledge is difficult to access | Training, knowledge systems and integrations |
| Customer requirements are lost between meetings | Information is captured inconsistently across existing tools | Structured data capture and workflow automation |
Together, we prioritise the problems worth addressing and establish what a successful improvement would look like.
03 / Design
Determine the appropriate solution.
Once we understand the problem, I determine which combination of salesperson development, process improvements and technology would address it most effectively.
Some problems require direct coaching. Others can be addressed through clearer sales processes, better configuration of existing platforms or software that fills a specific gap.
I assess the available options in the context of your existing technology environment, implementation requirements, operational responsibilities and commercial objectives.
- Hiring and candidate assessment
- Product-specific training
- Individual coaching
- Practical exercises
- Salesperson development frameworks
- Technical discovery methodology
- Customer evaluation criteria
- Opportunity review workflows
- Sales-to-engineering handoffs
- Knowledge capture and sharing
- Existing platform configuration
- API integrations
- AI-enabled workflows
- Internal applications
- Custom data models and automation
The solution is designed around the commercial requirement, using existing software wherever it meets the need.
04 / Implement
Deliver the agreed improvements.
I work directly with your team to implement the solution, whether that involves developing salespeople, improving technical sales execution or building software.
Training and coaching are based on real customer conversations and live opportunities. Workflow and software improvements are developed around how your team already operates.
Where engineering is required, I can configure existing platforms, build integrations and develop custom software within your repositories and infrastructure.
Develop salesperson capability.
I turn validated customer knowledge and effective sales behaviours into practical training, exercises and assessment criteria, then work directly with salespeople to help them apply what they learn.
Understanding customer implementation requirements
Technical discovery / Enterprise deployment
“We would need your product to work within our existing cloud environment and integrate with our identity platform.”
01 / Observe
Review an annotated customer conversation in which the founder establishes the customer's existing architecture and deployment constraints.
02 / Understand
Learn how implementation requirements, security policies and engineering responsibilities influence purchasing decisions.
03 / Practise
Conduct a simulated discovery conversation with a customer evaluating the product for an enterprise deployment.
skill_assessment
- Establishes the customer's existing technical environment.
- Identifies integration, deployment and security requirements.
- Understands who owns implementation and ongoing operations.
- Establishes the criteria for a successful technical evaluation.
Improve technical sales execution.
I help salespeople understand the customer's existing architecture, implementation requirements, operational responsibilities and evaluation criteria, and apply that understanding during live opportunities.
existing architecture
- Deployment
- Vendor-hosted
- Integration
- API + SDK
- Customer eng.
- Low
- Operations
- Vendor-managed service
- Deployment
- Customer VPC
- Integration
- API + infra
- Customer eng.
- High
- Operations
- Customer
- Deployment
- Customer
- Integration
- Custom
- Customer eng.
- Very high
- Operations
- Customer
Engineer the supporting systems.
I can bring your technical sales methodology into your existing software environment through platform configuration, API integrations, AI-enabled workflows and custom applications.
Existing technology environment
Conversations
Gong · Fireflies
CRM
HubSpot · Salesforce
Internal knowledge
Notion · Slack · Product documentation
Company-specific implementation
Commercial knowledge
- Technical discovery criteria
- Customer evaluation methodology
- Validated product knowledge
- Salesperson development objectives
Engineering
- Platform configuration
- API integrations
- AI-enabled workflows
- Custom software
Delivered capabilities
Opportunity intelligence
Customer requirements, risks and next steps.
Salesperson development
Targeted coaching, training and assessment.
Technical knowledge
Validated answers and customer examples.
Evaluation workflows
Technical requirements, POC criteria and progress.
Delivered within existing sales workflows
CRM · Messaging · Meetings · Internal applications
Deliver capabilities within existing workflows.
The objective is to make useful information and recommended actions available where your salespeople already work, rather than unnecessarily introducing additional tools.
Enterprise opportunity
Technical discovery · Enterprise deployment
Requirements incomplete
Technical discovery coverage
Existing cloud environment
Established
Deployment requirements
Established
Identity integration
Partial
Data residency requirements
Established
Implementation ownership
Not established
Evaluation success criteria
Not established
recommended_next_action
Establish identity integration requirements.
The customer requires SSO integration, but their identity provider, provisioning requirements and technical responsibilities have not been fully established.
supporting_conversation
buyer · 12:43
“We'll need SSO before we can roll this out. Our identity team would need to be involved.”
recommended_discovery
- Which identity provider and authentication protocols do you currently use?
- Are automated user provisioning and deprovisioning required?
- Who needs to participate in validating the integration?
Deal action
Confirm identity requirements and involve the appropriate technical stakeholders before defining the evaluation plan.
Coaching action
Develop the AE's ability to establish detailed integration requirements and identify the stakeholders responsible for implementation.
Possible delivery destinations
Connect technical discovery to customer evaluations.
Technical sales increasingly depends on coordinating customer requirements, product capabilities, engineering validation and implementation planning.
I can build workflows that connect these activities, using information from customer conversations and existing systems to help salespeople and technical specialists manage evaluations more effectively.
Customer evaluation workspace
Enterprise deployment · Technical evaluation planning
Generated from discovery conversations, CRM opportunity data and validated product knowledge.
Customer requirements
| Requirement | Validation method | Status |
|---|---|---|
| Data residency | Architecture review | Confirmed |
| SSO integration | Test environment | Pending |
| Processing throughput | Performance benchmark | Pending |
| Deployment model | Technical workshop | Confirmed |
| Operational ownership | Customer agreement | Unresolved |
Evaluation criteria
Identity integration
Successful authentication using the customer's identity provider
Deployment
Architecture and hosting model approved by the customer's technical team
Performance
Demonstrated throughput against an agreed representative workload
Operations
Implementation and ongoing ownership responsibilities agreed
Inputs
- Discovery transcripts
- CRM opportunity data
- Validated product documentation
- Existing technical requirements
Outputs
- Customer evaluation plan
- Engineering validation tasks
- Outstanding technical requirements
- Customer-specific implementation summary
next_action
Validate SSO integration.
Confirm the customer's identity provider and authentication requirements. Prepare a test environment and agree on validation criteria with the customer's identity team.
- Assigned to
- Account team · Technical specialist
- Dependency
- Customer identity requirements
Possible delivery destinations
The objective is to make technical evaluations easier to coordinate, ensure that customer requirements are captured consistently and establish clear responsibilities across sales, engineering and the customer.
Where custom software is required, we agree on code ownership, deployment, documentation, security requirements and ongoing maintenance.
05 / Measure and improve
Establish whether the implementation is effective.
Before implementing an improvement, we establish the commercial or operational outcome we want to achieve and identify appropriate ways to measure progress.
I review how salespeople apply new capabilities, how workflows and software are being used, and whether the changes are improving the organisation's ability to execute.
These observations inform subsequent coaching, process improvements and software development.
| measure | baseline | developing | target |
|---|---|---|---|
| Founder involvement↓ target | High | Selective | Exceptions |
| Discovery ownership | Observes | Co-leads | Leads |
| Technical evaluation | Founder-led | Shared | AE-led coordination |
| Customer judgment | Developing | Improving | Demonstrated |
| Measure | Measurement approach | Desired direction |
|---|---|---|
| Independent deal ownership | Proportion of AE-owned opportunities without routine founder intervention | ↑Increase |
| Technical discovery quality | Evidence-based assessment against validated discovery criteria | ↑Increase |
| Founder involvement | Founder hours spent supporting AE-owned opportunities | ↓Decrease |
| Time to new-hire productivity | Time until independent discovery and deal progression | ↓Decrease |
| Repeated engineering support requests | Recurring requests for the same technical assistance | ↓Decrease |
| Technical evaluation conversion | Proportion of evaluations progressing to the agreed next commercial stage | ↑Increase |
| Internal workflow adoption | Usage of agreed systems and workflows by the intended team | ↑Increase |
This creates an ongoing improvement process grounded in actual sales activity and the needs of your organisation.
06 / Contact
Identify an opportunity for improvement.
I'd be interested to understand how your sales team currently operates, where you're investing in its development and whether there are opportunities I could help you address.
