Solution Design Builder

The Problem

Building a customized solution design deck for a prospect is one of the most time-consuming parts of enterprise sales. After a discovery call, a solution architect or SE sits down with their notes, opens a PowerPoint template, and spends hours tailoring slides to the specific account — their pain points, their tech stack, their use cases, their objections.

The work is repetitive but not simple. Every deck is different because every account is different. You can't fully templatize it because the value is in the customization. But the process of translating call notes into polished slides is manual, slow, and pulls senior technical people away from actually selling.

The Solution

We built the Solution Design Builder — a tool that takes a PowerPoint template, combines it with prompt instructions and a user's RAG context (call notes, account research, discovery findings), and generates a customized deck automatically.

The user sets up their own RAG by dropping in their call notes and account intel. A README walks them through the setup so they don't need to understand the underlying architecture. They run the builder, and it produces a presentation that follows the company's standard template but is populated with content specific to that deal — tailored talking points, relevant use cases, and solution recommendations pulled from the discovery context.

How We Thought About It

The obvious approach would be to build a web app with a form — "enter your account name, select your use cases, click generate." That works for simple decks but falls apart when the customization needs to be genuinely intelligent. A dropdown menu can't capture the nuance of a 45-minute discovery call.

Instead, we leaned into RAG. The user's own notes and research become the knowledge base. The AI doesn't generate generic content — it generates content grounded in what was actually discussed with that specific prospect. The PowerPoint template ensures brand consistency and structure, while the AI handles the content that makes each deck unique.

We also made a deliberate choice to keep it as a script with a README rather than wrapping it in a full application. The users are technical — solution architects and sales engineers who are comfortable with a terminal. A simple setup guide and a script they can run is faster to build, easier to maintain, and honestly more flexible than a UI that would constrain how they feed in context.

The Result

• Deck preparation time reduced from hours to minutes
• Every deck follows brand-consistent templates automatically
• Content is grounded in actual call notes, not generic boilerplate
• Users set up their own RAG context — no dependency on a central team
• Simple script-based tool that technical sales teams adopted without training