Once your framework is set and your tone is chosen, length and variables are the fine-grained controls that sharpen output. Length determines how much Wyra expands each slot. Variables determine exactly what goes into specific parts of every message. Used together, they give you precision without sacrificing personalization.
Understanding length
Length shifts the tendency of output. It doesn't enforce a word count.
The length scale runs from 1 (shortest) to 5 (longest). It tells Wyra how much to expand each slot — how much context, explanation, and detail to include when filling in each part of the framework. It is not a strict character limit. Wyra prioritizes coherent, complete output over hitting an exact target.
1
Shortest
One tight sentence per slot. Maximum compression.
2
Compact
Short sentences, efficient. Gets to the point fast.
3
Balanced
Most campaigns. Enough room to build the case without excess.
4
Extended
More context per slot. Good for complex offerings or enterprise audiences.
5
Longest
Full expansion. Each slot gets maximum detail and context.
Why length 1 sometimes produces longer messages than expected
If a slot instruction is complex — referencing a specific ecosystem signal, bridging a nuanced pain point, or requiring multiple pieces of context to be coherent — Wyra will use the words it needs to complete it properly. Compressing it below a certain threshold would produce something incomplete or awkward. Wyra chooses coherence over brevity in those cases. If this happens consistently, tighten the slot instruction itself. More specific instructions produce tighter output at every length setting.
How length and slots interact
These two settings work together. Match them intentionally.
The total length of a message is determined by the combination of slot count and length setting — not either one alone. Here's how the combinations behave and when to use each.
Few slots (2–3)
+ Short length (1–2)
Tight and punchy
Each slot produces one concise sentence. Total message stays short and direct.
LinkedIn, C-suite email, re-engagement
Many slots (5–6)
+ Long length (4–5)
Detailed and thorough
Every slot gets full expansion. Produces a complete, well-argued message with all dimensions of the offering covered.
Complex enterprise email, long-cycle deals
Many slots (5–6)
+ Short length (1–2)
Broad but compressed
Wyra covers all the slots but compresses each one tightly. You get the full structure without bulk — but some nuance gets lost.
When you need breadth but inbox context demands brevity
Few slots (2–3)
+ Long length (4–5)
Deep on a few points
Each slot gets significant expansion. Good when you want to dwell on one key insight or proof point rather than covering everything.
Challenger campaigns, single-insight openers
Length in practice
Same 3-slot framework. Same lead. Four different lengths.
Framework: {opener connecting to lead’s AWS partner context} · {pain point around co-sell pipeline velocity} · {CTA tied to MAP funding window}. Lead: VP of Partnerships at an AWS Advanced partner SI.
Length 1 — Shortest
“Advanced tier partners competing for PDM attention need pipeline moving fast. We help AWS SIs accelerate co-sell sourcing. MAP funding closes Q1 — worth 20 minutes?”
Length 3 — Balanced
“At the Advanced tier, co-sell velocity is everything — partners competing for PDM attention need pipeline building fast, not sitting in qualification queues. We help AWS SIs move from signal to co-sell motion in days rather than weeks, using ecosystem intelligence to prioritize the right opportunities at the right time. With MAP funding allocations Q1-weighted, now is the lowest-cost window to validate the approach. Worth 20 minutes to see how this works for a team your size?”
Length 5 — Longest
“At the AWS Advanced tier, the gap between partners who compound their co-sell motion and those who plateau usually comes down to one thing: pipeline velocity. When opportunities sit in qualification for weeks, PDMs move on. By the time a partner has an account mapped, the window has closed. We work with AWS SIs to solve that gap — using ecosystem intelligence to identify co-sell-ready accounts, generate tailored outreach automatically, and get opportunities into ACE before the conversation moves elsewhere. Teams using this approach have cut the time from signal to active co-sell by more than 60% and increased partner-sourced pipeline by an average of 40% within the first quarter. MAP funding allocations are Q1-weighted this year, which makes now the lowest-cost window to test this motion against your current approach. Would a 20-minute walkthrough of how this works for a team at your tier be worth your time before the window closes?”
Length 3 is the right default for most email campaigns
Start at length 3 and adjust from there. If the preview reads too long for your audience, move to 2. If the message feels thin and doesn't build enough of a case, move to 4. Use the 3 preview leads to calibrate — look at the shortest and longest outputs, not just the first one.
Variables — three types
AI Descriptors, custom slots, and exact verbatim. Each serves a different purpose.
Variables give you precise control over what appears in specific parts of every message. You can use all three types in a single framework — Wyra handles them independently and combines them into a coherent message for each lead.
AI Descriptors — Wyra's pre-generated variables
When you open the messaging step, Wyra generates a set of descriptors automatically based on your offering data, lead profile, and campaign idea. These are ready-to-use variable options — select one and it appears in your framework as a filled-in element. If the generated descriptors fit your intent, use them. They're built from the full campaign context Wyra has assembled up to this point.
AWS Partner example
Wyra generates: “top proof point”
Populates as: “40+ ISVs migrated to AWS-native architecture with 60% average reduction in infrastructure overhead”
SaaS example
Wyra generates: “primary pain point”
Populates as: “personalized outreach at PLG scale doesn't keep up with the volume teams need to hit targets”
Custom Slots — your own AI variable instructions
When Wyra's pre-generated descriptors don't match what you need, write your own. A custom slot is a curly-brace instruction {like this} placed anywhere in the framework. Wyra reads the instruction, draws from all available data — offering, lead profile, campaign context — and fills it in uniquely for every lead in the campaign. The more specific the instruction, the more precisely Wyra can execute it.
AWS Partner — specific slot
{lead’s current AWS partner tier and most recent co-sell or Marketplace activity}
Wyra finds and inserts the right data per lead — different for every prospect in the campaign
SaaS — specific slot
{lead’s company growth stage and the outreach challenge most common at that stage}
Wyra infers growth stage from company data and maps it to the most relevant pain point
Exact Verbatim — fixed text that appears in every message
Text you write directly into the framework — not inside curly braces — that you want to appear in every message as intended. Wyra doesn't rewrite verbatim text, but it does refine it for spam safety, grammar, and message flow so it doesn't disrupt the surrounding message. Use it for branded phrases, specific product claims, compliance statements, or any language that must appear exactly as written.
AWS Partner example
Wyra is an AWS Select Tier Partner specializing in GTM acceleration for ISVs and SIs.
Appears in every message — refined for flow but not rewritten
SaaS example
Wyra is SOC 2 Type II certified and GDPR compliant.
Fixed claim — appears word-for-word in every message in the campaign
Putting it together
A framework using all three variable types.
This framework combines AI descriptors, custom slots, and exact verbatim in a single 4-slot email for an AWS partner campaign.
Framework — 4 slots, mixed variable types
Offering: GTM Intelligence Platform. Lead: VP of Partnerships at AWS Advanced SI. Length: 3. Tone: Wyra.
Why mixing variable types works
Each type serves a different need in the same message. Custom slots give Wyra the flexibility to personalize deeply for each lead. AI descriptors handle the elements where Wyra's pre-built context is already strong — proof points, pain points, CTAs. Exact verbatim locks the parts that must stay fixed — brand claims, compliance statements, product names. Used together, they give you a message that's simultaneously personalized, contextually strong, and precisely controlled where it matters.
Common variable mistakes
Three things that consistently produce weak output.
Vague slot instructions
{pain point} gives Wyra too little to work with — it defaults to the most general version of a pain point. {pain point for a PLG team transitioning to sales-assisted at Series B} gives Wyra exactly the lens it needs.
Using verbatim for everything
Verbatim text doesn't personalize. A framework that's mostly verbatim produces messages that feel like templates. Reserve verbatim for claims that genuinely can't vary — let slots handle the personalization.
Ignoring AI descriptors
Wyra's pre-generated descriptors are built from the full campaign context assembled to that point — offering data, lead enrichment, campaign idea. They're often the fastest path to strong output. Review them before writing custom slots from scratch.
Mismatching slots and length
5 slots at length 1 forces aggressive compression — Wyra squeezes each slot to a fragment. 2 slots at length 5 forces artificial padding — Wyra adds detail that isn't needed. Match slot count and length to your audience and channel.
Where to go next