Technical proposals in your client's format, in minutes.
Upload the resume and the JD, pick the client's SOP, and get a DOCX that follows their layout exactly. The resume is the only source of fact, so nothing is invented to fill a gap.
Any client SOP
A new client format is a new SOP upload, not a code change. The SOP defines the fields; the paired DOCX defines the look.
JD-driven selection
The job description decides which experience goes in and in what order. Unsupported requirements are listed, never claimed.
Page count respected
Set a page target and the engine trims the least important lines until it fits, without touching the template's spacing.
How it works
Resume + JD + SOP → submission-ready document
Your client's SOP decides how the document looks. The job description decides what goes in it. The resume is the only thing allowed to be a source of fact.
- 1
Drop the resume, the JD, and pick the SOP
PDF or DOCX on both sides. The SOP is either one your agency uploaded or one published to you from the platform catalog — you only ever see catalog SOPs that are published and granted to your workspace.
- 2
Text and layout come out of the files
DOCX goes through Mammoth, PDF through the parser. The SOP's own DOCX formatting — fonts, spacing, headings, table structure — is captured separately so the finished file matches the client's house style.
- 3
The SOP becomes a contract
The SOP compiles into an expected output schema: exact field names, types and nesting. No proposal layout is hardcoded in the engine, so a new client SOP needs no code change.
- 4
The model fills the schema, not a template
Each field is written from the resume. The JD drives selection, the SOP drives presentation, and invented employers, metrics or credentials are prohibited by the system prompt.
- 5
Gaps and SOP echoes get caught
A validator fills missing schema fields, rejects output that just parrots the SOP text back, and surfaces preflight blocks before a file is ever built.
- 6
A DOCX lands in your exports
The document is rendered from the SOP layout and stored against your workspace — Supabase when configured, local exports otherwise.
What you get
- Attachment proposal
- Client-formatted DOCX