Yes. 1KE is designed to turn customer inputs into structured requirements, solution direction, technical solution content, and proposal-ready outputs.
The goal is not just to summarise a deal. It is to help sales and presales teams move from messy discovery signals to a solution and proposal that reflects the customer’s needs, your organisation’s capabilities and your preferred way of selling and delivering.
1KE can produce deal summaries, structured requirements, gap analysis, solution outlines, technical solution content, proposal sections, customer-ready narratives, and delivery handover notes.
Outputs can be refined by your team and improved as more customer context is added.
Yes. 1KE can help create early drafts, working solution direction and proposal content even when the deal is still developing.
It also helps identify what is missing, what needs validation and where more customer input is required.
No. 1KE is designed to fit into the way sales and presales teams already work.
It can use existing deal signals such as meetings, notes, emails, CRM records, uploaded documents, RFPs, discovery material and proposal inputs, rather than forcing teams into a completely new process.
Ambient means 1KE can work from the information your team is already creating as part of the sales process.
Instead of relying only on manual data entry, 1KE helps capture and structure the deal context that already exists across conversations, documents, meetings and systems.
Yes. Teams can start by creating deals directly in 1KE and uploading the relevant deal assets.
CRM integration can add more automation and context, but it is not required to begin using the platform.
1KE is purpose-built for technical sales and presales workflows.
It does not just respond to prompts. It structures deal signals, extracts requirements, builds deal context and generates solution and proposal outputs using your organisation’s capabilities, preferences, services, delivery models and commercial patterns.
Yes. 1KE can be configured around your preferred vendors, technical capabilities, service offerings, delivery models, proposal standards and commercial preferences.
That means generated solutions can be grounded in what your organisation can actually sell, implement, support and deliver.
Yes. 1KE is designed to work with organisational knowledge such as proposal templates, service catalogues, delivery patterns, pricing structures and preferred solution approaches.
This helps make outputs more consistent, more usable and more aligned to how your business operates.
No. 1KE is designed to amplify sales and presales teams, not replace them.
It helps capture context, structure requirements, accelerate solution development and produce stronger first drafts, while keeping expert judgement in the loop.
Yes. Users can review, edit, refine and correct requirements, assumptions, summaries, solution content and proposal outputs.
1KE is designed to improve the quality and completeness of the deal record over time.
1KE can help surface gaps, assumptions and contradictions so teams know what needs to be clarified before a solution or proposal is finalised.
This helps reduce avoidable rework, poor handovers and proposal risk.
1KE is designed around organisation-level data separation, dedicated customer storage, controlled access, audit logging, and private AI workflows.
Customer requirements, technical documents, solution logic, proposal content and institutional IP remain scoped to the customer organisation.
No. Your customer context supports your own workflow. It is not reused across other customer accounts or used by 1KE to train public AI models.
Yes. 1KE can support regional deployment models for customers with specific data residency requirements, subject to agreed architecture, integration and AI processing needs.
Ideas, frameworks, and updates for technical sales teams - delivered to your inbox.
