Outbound Architect · Signal-based outbound

Make every message start with a reason.

Start with verifiable evidence, form a useful hypothesis, and prepare a reviewable message for the channel—without turning a signal into a certainty.

For BDRs who want the first line of a call or email to be about the prospect, not the product. Usage limits apply by plan.

Evidence → angle → your wordsDraft for review

Fictional example: a company announces a regional launch. The source context stays attached to the draft.

Review the evidence and tone before use. Nothing is saved or sent.

Illustrative workflow · Conceptual explanation, not a current product screen.

How a draft is built

Evidence first. Message second.

Four checks keep a signal-based message relevant, honest, and short enough to earn a reply.

  1. Evidence: begin with the source.

    Review the account event, date, and provenance before it becomes the first line of a message or call.

  2. Hypothesis: connect the change to a consequence.

    Explain what the event may create operationally while leaving room for the prospect to correct the assumption.

  3. Channel: adapt the angle to the action.

    Prepare a concise call opener, email, or LinkedIn direction from the same evidence without copying one template everywhere.

  4. Review: the rep owns the final message.

    Verify relevance, remove overconfident claims, and approve the output before any live outreach.

Relevant evidence → useful angle → editable outreach

The context changes the conversation.

Switch channels. Try the words. Keep the reasoning attached.

Illustrative example · Fictional company and source · Prewritten drafts, not live AI output

Draft for reviewNot sent

Make the first sentence count.

Edits stay on this page. Nothing is saved or sent. Do not enter private information.

Check the launch, confirm the right person, and leave room for their answer.

Draft for reviewNot sent

Keep the reason in the message.

Edits stay on this page. Nothing is saved or sent. Do not enter private information.

A public event supports the opening. It does not prove a problem. Edit the hypothesis and request.

Draft for reviewNot sent

A small note with real context.

Edits stay on this page. Nothing is saved or sent. Do not enter private information.

Review the recipient, the evidence, and the tone before using this note.

Human review

Relevant does not mean invasive.

Use business events the company has made public. Every draft stays editable, and nothing is sent automatically.

Syntri prepares

  • Call scripts, emails, and LinkedIn drafts grounded in account evidence
  • The source behind each claim in the draft
  • Channel-specific length and structure

You decide

  • Whether the evidence is accurate and still current
  • Which claims to keep, soften, or remove
  • Whether and when the message is used

From signal to next action

Keep outbound inside the daily plan.

The strongest message still needs the right account, contact, timing, and follow-up.

Explore the Daily Attack Plan

FAQ

Drafts, not automatic sends.

What is signal-based outbound?

Signal-based outbound uses a specific, timely account change to form a problem hypothesis and relevant question. The signal changes the reason for outreach rather than decorating a generic pitch.

Does Syntri automatically send generated messages?

No. Generated outreach is a draft. The rep reviews the source, account context, claim, channel, and final message before taking action.

Which channels can the same signal support?

A verified signal can inform a cold-call opener, email, or LinkedIn touch, but the length and request should be adapted to the channel.

Outbound Architect

Say something relevant.

Start from the evidence, then make the message sound like you.