What the 15-minute draft contains
The system produces an editable proposal draft containing project requirements, citations and assumptions for review. A writer still checks the reasoning and parameters, and the document needs approval before submission.
At a consulting and research firm, source preparation and first-draft writing previously took roughly two days. The workflow produced drafts in 15 minutes with 99% citation accuracy and seven completeness checks. These figures describe that project; new use cases require their own testing.
Agree on review criteria first
We examine templates, previous proposals and reviewer comments with the business team. This establishes requirements for sections, pricing, specifications and citations. Documents with the same name may have different approval standards across companies.
We then separate reusable product knowledge from facts that apply only to a previous project. Current client constraints, parameters and assumptions need identifiable sources so old conditions are not carried into the new proposal.
Organize past material
Ingestion preserves relationships between sections, tables and attachments. Parameters stay associated with the equipment and version they describe; clauses retain their scope. Records also include sources and update dates.
Product knowledge, prior arguments and current inputs are managed separately. The workflow confirms the new project’s goals and constraints before retrieving material. Missing information becomes a list of questions for the team, especially where a numerical value needs confirmation.
Generate and check in stages
Technical choices, costs and implementation plans depend on one another. A misunderstood requirement can affect later sections. Processing in stages helps reveal the error before work continues.
The workflow confirms needs, extracts constraints, retrieves evidence, prepares an outline, drafts sections and checks completeness. People confirm important decisions. Each section can use a different retrieval scope and validation rules, with the sources visible to the reviewer.
Check parameters and completeness
Define each field’s unit, source, version and treatment of missing values. Use deterministic calculation logic where needed and retain the parameter source in the draft for review.
Completeness checks follow the agreed checklist and identify missing sections, required fields and supporting material. The existing project uses seven checks; other organizations need a checklist based on their own delivery standards.
Human review
Authorized reviewers confirm final commitments, commercial terms, sensitive assumptions and professional responsibilities. The review interface should open the relevant citations and assumptions directly. Missing sources, conflicting references or absent required parameters pause the workflow and prompt a request for information.
Testing before launch
Select representative historical projects, covering complete and incomplete sources, conflicting clauses and complex constraints. Compare outputs with accepted documents and check coverage, parameter consistency, citations and risk flags.
Record where reviewers make changes. Repeated errors in one section suggest checking retrieval and templates. Decisions that vary by project need appropriate human inputs. These records also help compare review effort before and after implementation.
Adding document types
Begin with a frequently used format that has adequate sources and clear review criteria. Confirm adoption and reduced review time before adding related types. Each new type needs defined inputs, structure, checks and an owner. Knowledge indexes, integrations and some review rules can be reused, but must be tested against the new requirements.
Discuss a similar project
Bring your current process and a work sample to discuss scope, costs and implementation requirements.
Discuss your project


