From Draft Report to the Client's Inbox

The challenge

An AI draft is a starting point. Advisers are responsible for what reaches their clients, so every report needs a review and usually a few edits. If editing meant copying text into Word, fixing the formatting by hand and attaching the file to an email, much of the time saved in drafting would be lost at the final step. Clients also expect a proper document, formatted like one.

What we built

A review and send workspace on every FinPlan meeting record:

• A proper editor: reports open in a rich text editor with headings, lists, task lists, tables, underline and text alignment. Advisers who prefer Markdown can edit in that instead.
• Autosave: changes save every 30 seconds while there are unsaved edits, so very little is lost if a tab closes mid-review.
• Several reports per meeting: one meeting can produce a file note for the practice and a summary for the client, each from a different template, all kept against the same record.
• Export in three formats: PDF with a title and creation date, Word, and plain text. Files are generated in memory and streamed to the browser, and are never written to disk on the server.
• Email from the record: advisers send the report to the client with their own subject line and message, with the PDF or Word file attached.

Technology

A TipTap rich text editor in Next.js, with reports stored as Markdown and converted for editing. PDF export uses iText and Word export uses Apache POI, both running in a Kotlin and Spring Boot service. Email goes out from the backend with the export attached. Drafts come from Advice Documents Drafted From the Adviser's Own Templates, and we run the delivery step in production as part of An AI Platform That Turns Client Meetings Into Finished Reports.