Blueprint elements
Understand every current group of elements and how each setting affects personalised emails.
How Blueprint elements work
Elements are the settings that shape the emails PitchKraft creates. The current editor groups them into collapsible sections on the left. Expand a section to see its fields and select View and edit to work on a value in the panel on the right.
Each section has a completion indicator such as 4/4 or 4/5, showing how many fields have been filled. Some optional fields can remain Not set; this does not automatically mean there is a problem.
Edit the selected element directly using the available field or rich-text editor.
Discuss an individual element with PitchKraft. It shows the current value and lets you ask what to add, change or remove.
Use Save all to preserve your changes, and Preview email to check their effect on an actual sample message. See the Edit Blueprints guide for the complete editing workflow.
Jump to a section
Detailed element guides and examples
This overview is a directory, not a replacement for the original long-form element guides. The following articles retain their detailed explanations, practical examples and mini case studies. Each individual element below also links to the most relevant existing guide where one is available.
What editing an element looks like now
In the current Blueprint editor, groups expand in the left-hand column. The View and edit button opens the selected field on the right, where users can select Manual or Chat AI. The example below is reconstructed from the current interface without showing any contact information.
EXAMPLE MESSAGE
This email is the writing reference for the Blueprint.
Current value: A reference email is already saved, including the greeting, offer, relevant context and closing.
What would you like to add, change or remove?
Visual guide based on the current screenshots. Example text and figures are illustrative, not from a customer's live Blueprint.
Other original element articles
These established articles remain available with their original detailed guidance and examples. Some cover supporting settings that do not have their own separate row in the current editor.
Main focus
The essentials that define the message and how it becomes relevant to each recipient.
| Element | What it controls |
|---|---|
| Example message | A model email that provides the Blueprint's writing reference: structure, content, tone and style. It can be edited manually or with Chat AI. |
| Theme | The overall subject or purpose of the outbound message, such as introducing an event or offering a service. |
| Hook | The connection you want PitchKraft to make between the recipient and the main theme. |
| Personalization search | Guidance on what evidence or information PitchKraft should search for to support the hook and make each message relevant. |
Personalization sources
Choose the types of information PitchKraft is allowed to consider when generating personalised content.
| Element | What it controls |
|---|---|
| Use online research | Allows PitchKraft to use publicly available online research relevant to the recipient, company and message. |
| Use professional summary | Allows use of the contact's professional summary where that information is available. |
| Use notes | Allows relevant notes associated with the contact to inform the email. |
| Use email history | Allows relevant previous email interactions, where available, to contribute context. |
| Use LinkedIn history | Controls whether available LinkedIn history may be used as another context source. |
Your company
Information about the organisation on whose behalf the emails are written.
| Element | What it controls |
|---|---|
| Company name | The name of the organisation represented in the email. |
| Registered company name | Its formal registered name, where different from the public-facing name. |
| Company website | The organisation's website URL. |
| Knowledge base | Internal reference material about the organisation, its offerings, sessions, events or other details that the email may need to use. |
Signature
How the email should close.
| Element | What it controls |
|---|---|
| Signature | The sign-off block, for example the sender's name, role, organisation and other contact details. The editor supports formatted text. |
Writing preferences
The preferred language and style conventions.
| Element | What it controls |
|---|---|
| Language | Sets the language or variant used in the email, such as English (UK). |
| Emojis | Controls the desired level of emoji use, such as minimal. |
Dos and don'ts
Instructions that govern what must be included, excluded or expressed in a particular way.
| Element | What it controls |
|---|---|
| Extra instructions | Additional rules and guidance. For example, you can direct PitchKraft to choose the most relevant event session for a recipient instead of repeatedly suggesting the same session. |
| Avoid words | A list of words or phrases you do not want PitchKraft to use, such as generic sales clichés or certain expressions. |
Greetings & farewells
Decide whether greetings, closings and unsubscribe text appear in the message.
| Element | What it controls |
|---|---|
| Include greeting | Controls whether the generated email includes an opening greeting. |
| Include farewell | Controls whether a closing greeting or sign-off is included. |
| Use unsub block | Controls inclusion of the configured unsubscribe wording. |
| Unsubscribe block | The exact wording or template used for the unsubscribe section, including any relevant contact or source references. |
Extra assets
Optional social proof and supporting material.
| Element | What it controls |
|---|---|
| Use testimony | Controls whether a relevant testimonial or quote should be included. |
| Testimony content | The approved testimonial or quote material available for PitchKraft to use. |
Images
Visual elements used in the generated email.
| Element | What it controls |
|---|---|
| Banner image (URL) | A URL for an image displayed in or near the email header. |
| Footer image (URL) | A URL for an image used in the footer or signature area. |
| Footer image width (px) | The intended width of the footer image in pixels. |
| Additional visual instructions | Further guidance on which images to use and how they should appear. |
Subject line
How the subject is generated and controlled.
| Element | What it controls |
|---|---|
| Subject – use AI? | Controls whether PitchKraft should generate the subject line. |
| Subject instructions | Extra guidance for AI-generated subjects, if used. |
| Subject – manual | An explicitly supplied subject line when you want to define the wording yourself. |
Custom
Additional fields unique to a particular Blueprint.
| Element | What it controls |
|---|---|
| Custom element(s) | User-defined settings or values. Your fields may differ from those shown in a sample Blueprint—for example, a custom user-name field. |
Worked examples: how elements change the final email
These examples demonstrate how different Blueprint fields work together, based on the women-in-technology event use case shown in the app screenshots. They illustrate the writing process, not measured campaign outcomes.
1. Hook + research
Goal: Invite a software quality professional to a technology event.
Fields: Theme, Hook and Personalization Search.
Instruction: Connect the invitation to the recipient's technical responsibilities and check whether their employer has public initiatives relevant to inclusion.
Example effect: The email can explain why a relevant event session matters to the recipient, rather than sending a generic exhibition invitation.
Read the detailed Hook examples →2. Knowledge base + sources
Goal: Recommend the most relevant session to each prospect.
Fields: Knowledge Base, Use Online Research and Extra Instructions.
Instruction: Consider available event sessions alongside the prospect's role and employer background; select only a session supported by the available details.
Example effect: A role-specific session suggestion supported by event and prospect information, with a link to the actual session.
See the company knowledge guide →3. Example + safeguards
Goal: Maintain a recognisable email structure while personalising each recipient's message.
Fields: Example Message, Avoid Words, Signature and Unsubscribe Block.
Instruction: Use the reference message's tone and CTA, avoid generic openings, preserve a consistent signature and add the configured opt-out wording.
Example effect: Each email can be individually relevant without losing the campaign's identity or expected closing information.
Read the original example-email guide →Making the elements work together
A strong Blueprint connects the theme, hook and personalisation search. The theme says what you are promoting, the hook says why it matters to this recipient, and the search objective guides what evidence PitchKraft looks for. Company knowledge, notes, professional information and other enabled sources provide context.
Example: For an industry event, the theme might be inviting relevant professionals to attend; the hook could connect the event to the prospect's responsibilities; and the personalisation search could look for public evidence about their team's priorities. Extra instructions can guide which event sessions to recommend.
If output feels generic, first check that the hook and research objective are specific enough. If something is factually unsupported, revise the content and inspect the source evidence before using the resulting email.
