For Sales Engineers ·
What you'll accomplish
After the third discovery call in a week, retyping the same formatting instructions gets old fast. A Gem remembers the instructions for you. Paste in raw notes or a transcript, and it hands back the same structured requirements summary every time, without you rebuilding the prompt from scratch.
What you'll need
What you should see: A blank Gem setup screen with fields for a name, instructions, and optional knowledge files.
Give it a specific name so you can find it fast later, such as "Discovery Intake Formatter." A vague name like "Sales Helper" gets lost in a sidebar full of other Gems within a month.
This is the field that does the real work. It plays the same role a system prompt would: it tells the Gem how to behave on every single chat you start with it, so you never retype these rules again.
Exact text to copy into the instructions field:
You turn raw sales discovery call notes or transcripts into a structured requirements summary for a sales engineer. Every time I paste in notes, produce a summary organized into these exact sections, in this order:
1. Functional Need: what the customer says they need the product to do.
2. Integration: systems, data sources, or platforms the solution needs to connect to.
3. Security and Compliance: any security, privacy, or regulatory requirements mentioned.
4. Scalability: volume, user count, or growth expectations mentioned.
5. Open Questions: anything the notes don't answer that a sales engineer would need to follow up on.
Only include what the notes actually say. If a section has nothing relevant, write "Not discussed" rather than guessing or inventing detail. Keep each section to a few bullet points, not paragraphs.
If you have a template file or a past example of a well-formatted summary, you can add it under the Knowledge section by clicking Add files. This step is optional. The instructions above are usually enough on their own.
Click Save. Your Gem now appears under "My Gems" in the Gems sidebar, ready to reuse any time, and it syncs to the Gemini mobile app as well.
What you should see: Your named Gem listed alongside any pre-built Gems Google includes by default. Troubleshooting: If a Save button doesn't appear or the preview window seems to save automatically, don't assume it stuck. Navigate back to the Gems list afterward and confirm your Gem is actually there before you close the tab.
Open your Gem and paste in notes or a transcript from an actual discovery call.
Confidentiality caution: Discovery notes usually name the customer and sometimes describe their internal systems in detail. Before pasting anything in, strip the customer's name (use "the prospect" or their industry instead) and remove any IP addresses, hostnames, or internal system names. The summary the Gem produces is just as useful with those details genericized, and it keeps a live customer environment out of a chat log.
What you should see: A summary broken into the five sections from the instructions, with "Not discussed" in any section the notes didn't cover.
Verification step: Before you send the summary to the account executive or reference it during demo planning, scan it against your raw notes line by line and confirm every requirement listed was actually said by the customer, not inferred or filled in by the Gem. A requirements summary that quietly invents a stated need is worse than a shorter, honest one.