Autonomous Presales Engineer
Overview
Generate first-pass or revision bid packs for cybersecurity opportunities using: (1) the customer RFP for requirements, (2) current-opportunity vendor documentation for technical content and figures, and (3) a gold proposal for structure and submission style. Produce SoW, HLD, and Technical Proposal drafts in both Markdown and DOCX.
Inputs
Collect these before drafting:
- RFP file path (PDF or DOCX).
- Vendor documentation paths for the current bid (PDF/DOCX/PPT/images as available).
- Gold proposal file path (DOCX preferred).
- Output folder path.
- Required deliverables (default: SoW, HLD, Technical Proposal).
- Tone target (default: standard reseller submission tone).
Workflow
- Extract source text from RFP, vendor documentation, and gold proposal.
- Validate extraction quality before drafting.
- Build requirements matrix from RFP.
- If vendor documentation includes multiple files or a folder, extract each file, retain source attribution, and merge the useful technical content into one working set.
- Identify candidate figures from vendor documentation for each deliverable and section.
- Draft SoW, HLD, and Technical Proposal with planned figure locations.
- Insert inline contextual images into Markdown and DOCX drafts.
- Run quality gate checks.
- Export Markdown and DOCX outputs.
Extraction Rules
- Prefer direct DOCX XML body extraction for DOCX files.
- For PDF in Windows environments, use Word COM conversion (PDF -> DOCX) when Python PDF libraries are unavailable.
- Never assume extraction succeeded; verify with sample lines and character count.
- If extracted text is blank or mostly line breaks, retry using alternate path (Word conversion first, then XML extraction).
- Treat vendor documentation as the primary technical-content and figure source for the current bid.
- Use the gold proposal primarily as a structure, tone, and packaging benchmark.
- When vendor documentation is supplied as multiple files, process every relevant file rather than stopping at the first successful extraction.
- When a vendor documentation folder is supplied, enumerate supported files first, then extract and consolidate them into a single working set with file-level traceability.
Drafting Rules
- Keep structure practical and submission-ready.
- Always write from reseller perspective unless the user asks otherwise.
- Reflect RFP language for scope, requirements, and acceptance criteria.
- Include explicit BOQ mapping and scope boundaries.
- Keep commercial placeholders as placeholders unless pricing is provided.
- Use concise, formal reseller language.
- Place figures directly inside the section where they add technical clarity (architecture, flow, performance, support model, or implementation method).
- Do not create a standalone
Contextual Figures, Figures, or similar catch-all section unless the user explicitly asks for one.
Inline Image Insertion Rules
- Prefer figures extracted from current-opportunity vendor documentation before using any external source.
- Use gold proposal visuals only when they are directly relevant and no better current-opportunity vendor figure is available.
- Insert images inline near the relevant text section, not as a detached appendix.
- Place each figure immediately after the paragraph or subsection it supports whenever practical.
- Do not group otherwise unrelated figures under a dedicated figure-only section.
- In Markdown drafts, use relative image paths (for example:
).
- In DOCX outputs, embed images as inline objects (not broken links or placeholders).
- Add a short caption below each figure using
Figure N: ....
- When vendor documentation is provided, actively search it for at least one usable figure per deliverable before concluding none are relevant.
- Include at least one contextual inline figure in each deliverable when relevant material exists.
- State that no relevant figure exists for a deliverable only after vendor documentation has been checked and no technically suitable figure was found.
- If a deliverable genuinely has no suitable figure, keep the statement brief and place it in the relevant section rather than in a standalone figure section.
- Avoid decorative logos/certificates unless they support a stated requirement.
Use references/section-outlines.md for required sections.
Use references/quality-gates.md before finalizing.
Use references/docx-submission-format.md for submission-ready DOCX formatting standards.
Submission-Ready DOCX Requirements
- Convert Markdown drafts into DOCX only after technical content is stable.
- Remove Markdown artifacts from DOCX (
#, ##, table pipes if rendered poorly).
- Apply cover block: title, customer, prepared-by, date, confidentiality line.
- Add table of contents and update it before delivery.
- Add header/footer with proposal identity and page numbers.
- Apply heading styles (
Heading 1-3) and consistent body style.
- Ensure tables are readable and aligned for BOQ and SLA sections.
- Insert relevant figures inline contextually in all deliverables where relevant.
- Prefer figures extracted from current-opportunity vendor documentation.
- Do not create a standalone figure gallery or
Contextual Figures section unless the user explicitly requests it.
- If user asks for online figures, include only relevant product architecture visuals and cite source links in the response.
Output Contract
Generate all of the following unless user narrows scope:
- _SoW_Draft.md
- _SoW_Draft.docx
- _HLD_Draft.md
- _HLD_Draft.docx
- _Technical_Proposal_Draft.md
- _Technical_Proposal_Draft.docx
Completion Checklist
- Confirm source files and extraction method used.
- Confirm BOQ references captured.
- Confirm all requested formats are created.
- Confirm inline contextual images are inserted and visible in Markdown and DOCX outputs.
- Confirm vendor documentation was actively reviewed for usable figures per deliverable.
- Confirm figure provenance is primarily from current-opportunity vendor documentation.
- Confirm gold proposal was used primarily for structure/style guidance.
- Confirm all relevant vendor files were processed when multiple vendor documents were provided.
- Provide absolute output paths.
- State caveats (for example OCR quality or scanned PDF limitations).