overview / 01-1KE / 01-overview
How It Works
Last updated at 2026-06-15 18:09 AEST.
1KE takes the messy pile of documents that accompanies a sales opportunity — the customer's request, meeting notes, emails, spreadsheets — and turns it into a polished, customer-ready proposal. It does this the way an experienced solutions team would: read everything, work out what the customer actually needs, decide what to recommend, design how it would be built, and then write it all up. The difference is that 1KE does it in minutes, consistently, every time.
This page tells the whole story end to end. Each stage also has its own plain-English page if you want to go deeper.
The big idea
Think of 1KE as a tireless solutions consultant that never loses the thread. Every fact it puts in a proposal can be traced back to something the customer actually told you. It doesn't invent vendors, prices, or commitments. And nothing it produces is final until a person reviews and approves it — the platform does the heavy lifting, you stay in control of the decisions.
The work flows through four stages. Each one builds on the last, and each one is something you can read, edit, and sign off before moving on.
The four stages
The platform reads each document you upload — an RFP, a call transcript, an email thread, a pricing spreadsheet — and pulls out what matters: what the customer needs, their constraints, their environment, who's involved. It builds a single, organised picture of the deal that everything else is based on.
Read more: Understanding the deal
From that picture, 1KE recommends an approach: which of your services, products, and partners fit this customer. It only suggests things your organisation can actually deliver and sell. You review the recommendation and approve it before anything goes further.
Read more: Shaping the strategy
Once a strategy is approved, the platform designs how the solution would actually be built — the architecture, the moving parts, a current-state analysis, and clear architecture diagrams. This is the engineering thinking, captured before any proposal is written.
Read more: Designing the solution
Finally, 1KE assembles everything into a complete, professionally formatted proposal document — executive summary, commercials, implementation plan, and more — and then critiques and improves its own draft before handing you the finished file.
Read more: Writing the proposal
What makes the output trustworthy
The hardest question about any AI system is "can I trust what it produced?" 1KE is built around a few principles that answer it:
Every claim in a proposal traces back to something in the source material. The platform is explicitly steered away from inventing facts, and a built-in reviewer flags anything that can't be traced to an input.
The strategy and the proposal are checkpoints, not auto-sends. A person reviews and approves before the work moves to the next stage or reaches a customer.
Before handing over a proposal, the platform scores its own draft against a quality rubric and rewrites the weakest parts — the way a senior reviewer would mark up a junior's first draft.
Your documents and the proposals 1KE produces stay inside your organisation's private, access-controlled space. One customer's data is never visible to another.
Progress appears live. When a colleague kicks off a generation, you see it update on your own screen in real time — no refreshing, no wondering whether it's running.
Every version is kept. You can always see which documents and which decisions produced a given proposal, and roll back to an earlier version if you need to.
What you actually do
For all the machinery underneath, the day-to-day experience is simple:
- Upload the deal's documents. The platform reads and organises them for you.
- Review the recommended strategy and approve it (or adjust it first).
- Let the platform design the solution, and review the architecture it proposes.
- Generate the proposal, then download the finished document.
Each step runs in the background, so you're never stuck staring at a spinner — you can carry on with other work and come back when it's ready.
This page is the executive summary. If you'd like the same plain-English treatment for any single stage, follow the "Read more" links above — each stage has its own page, written for the same non-technical audience.