overview / 01-1KE / 05-writing-the-proposal
Stage 4 · Writing the Proposal
Last updated at 2026-06-15 18:09 AEST.
This is where everything comes together. The platform takes the understanding of the deal, the approved strategy, and the solution design, and assembles them into a finished, professionally formatted proposal — a Word document, attached to the deal, ready for your team to review and send. It's the most involved stage by far, and the one that most resembles a whole team of people working at once.
The simplest way to think about it
Picture a proposal team under deadline: one person writes the executive summary, another the commercials, another the implementation plan — all working in parallel from the same brief. Then a senior reviewer reads the whole draft, marks up the weakest sections, and sends them back for another pass. 1KE runs that entire team-and-reviewer cycle automatically, every time.
At a glance
What goes in
By this point, the hard thinking is already done. The proposal stage gathers it all:
- The deal's understanding and the approved requirements.
- The approved strategy — the services, products, and partners to propose.
- The saved solution design and its diagrams (reused as-is, never rebuilt here).
- Optional steering notes, a chosen document style, and your organisation's logo for the cover.
If the solution design is missing or has gone out of date, the platform stops and tells you — clearly — rather than quietly writing a proposal around stale engineering. It's a guardrail, not a guess.
How the document is built
A proposal isn't one block of text — it's a dozen distinct sections, each needing its own expertise. 1KE assigns a dedicated specialist writer to most of them — eleven in all — and runs the independent ones at the same time so the whole document comes together quickly rather than one section after another. (The twelfth, the solution overview, isn't written here; it's carried over ready-made from the design stage.) The sections include:
- Executive summary
- Current state
- Solution overview
- Commercials
- Implementation plan
- Managed services
- Migration & cutover
- Non-functional requirements (performance, reliability, and the like)
- Risks & assumptions
- Security & compliance
- Testing & acceptance
- Appendices
Alongside the written sections, the platform works out a sensible delivery plan — the phases, their order, and rough durations — and splices in your organisation's standard boilerplate (terms and conditions, company background) from your own library. Finally it renders everything into a styled Word document, complete with a cover page carrying the customer name, deal name, date, and your logo.
It reviews and improves its own draft
This is what sets the stage apart. A first draft is rarely a final draft — so before handing anything over, the platform puts its own work through a tough internal review. A separate AI reviewer reads the assembled proposal and scores it against six quality dimensions, then the platform rewrites the weakest sections and scores again, keeping whichever round came out best.
Every name, number, date, and commitment must trace back to the source material. Anything invented is flagged hard.
Every meaningful thing the customer asked for is addressed somewhere in the proposal — nothing important is left out.
The sections agree with each other — the products, the priced scope, and the timeline line up across the whole document.
One consistent, professional voice toward the customer, with no unsupported marketing fluff.
No gaps, no "to be decided" placeholders, no off-topic filler — every section that belongs is present and substantial.
Specific and substantive given what the inputs support — not vague, generic boilerplate.
The reviewer scores conservatively: top marks are reserved for content that's clearly traceable to the inputs with no contradictions. The effect is that obvious weaknesses get caught and fixed before you ever see the draft — the same thing a careful human reviewer would do, just faster and on every proposal without exception.
A quality flag, not a blocker
Before it even starts writing, the platform checks whether the inputs are rich enough to support a strong proposal. If they're thin, it still produces the document but marks it as a draft, so your team knows to fill gaps before sending. It never silently passes off a weak proposal as a finished one.
What comes out
A complete Word document, saved into your organisation's private storage and attached to the deal. From there your team downloads it, reviews it, and sends it — the proposal is a strong, customer-ready starting point, with a person making the final call. The platform also keeps a full record of which inputs and decisions produced each version, and automatically runs a quality assessment afterwards so you have an honest read on what it generated.
Built-in safeguards
The expensive design work was done in the previous stage and is reused here, so the proposal always matches the approved solution.
The reviewer is hardened against attempts to smuggle instructions inside customer documents — it treats their content as information to assess, never as commands to follow.
If a run stalls or an instance restarts mid-generation, the platform detects it and recovers automatically, so a stuck job surfaces for retry instead of sitting frozen.
You watch a "Generating…" placeholder turn into the finished file in real time; the document stays in private storage; and every version is kept with its full history.
Previous: Designing the solution · Back to 1KE