Getting started

Wrenwire is an AI-driven workflow for B2B outbound sales. You describe what you are selling once, and the platform turns that into targeted segments, decision-maker profiles, and ready-to-send email and LinkedIn sequences, with a quality review before anything goes out.

The shape of the product follows from one decision: the AI prepares, you approve. Every stage produces a draft you can read, change or reject, and the next stage does not start until you have. That is why the screens look like a queue of decisions rather than a dashboard.

The path to your first campaign

1. Create a product canvas: a short description of what you are selling. Every campaign is built on one. See Product canvas.
2. Create a campaign: a name, a goal (“book 10 demo calls with CFOs at manufacturers”), and a target market. The market matters: Germany, Austria and Switzerland carry extra requirements for cold outreach and get a checklist before launch. See Compliance.
3. The AI generates target segments and value propositions from your canvas. Review and adjust before moving on. See Target audience.
4. The AI generates decision-maker personas and message sequences for email and LinkedIn, per segment. See Message sequences.
5. The quality review scores every version before it can be activated, so nothing goes out unchecked.
6. Find and qualify prospects with the prospect finder. Wrenwire then creates the campaign on your own Snov.io account and adds the qualified prospects to it. You can also export the list, for cold calling for instance. See Prospect finder.

Each AI step consumes credits from your plan. Credits and billing explains how that works and how to see the cost of an action before you run it.

How long the first campaign takes

The generation steps run in the background and take minutes rather than hours, but the overall pace is set by your reviews, not by the model. In practice the first campaign is an afternoon: most of that time goes on reading the segments and the first message series and deciding what you actually want to say.

Later campaigns are faster, because the product canvas is already written and can be reused.

What a stage waiting for you looks like

A generated artefact arrives with its quality score and the notes behind it. You can accept it, edit it in place, or send it back for another attempt with your comment attached. Edits are versioned, so an earlier draft is never lost and you can compare what changed.

Nothing about this is a formality. The quality review drops weak versions before you see them, so what reaches you is the survivor of a filter rather than the first thing the model produced.

What blocks a launch

Activation is refused, rather than warned about, when:

• the quality review has not been run or has not passed,
• the campaign targets Germany, Austria or Switzerland and its pre-flight checklist is incomplete: legal basis for contact, sender’s legal details, SPF, DKIM and DMARC on the sending domain, and the unsubscribe-link signing key.

The reason for refusing rather than warning is that these are the checks nobody performs twice. A warning gets dismissed on a busy afternoon; a refused launch gets fixed.

Guided mode

A new workspace opens in guided mode, which narrows the interface to what the current stage needs, so the first campaign is not a tour of every screen at once. The setup checklist tracks the path from an empty account to the first send.

You can switch to advanced mode at any time, and switch back. Nothing is hidden permanently.

What Wrenwire does not do

It does not send on its own. Sending happens through the tool you connect, and a series reaches it only after you approve it.

It does not judge whether your legal basis for contacting someone is sound. It records the basis you declare, applies the checks it can automate, and leaves the judgement to you. See Compliance and the market pages linked from it.