Outbound Engine is a cold outbound optimizer. It asks whether the user has an Instantly account, audits campaigns, sending accounts and warmup scores through the Instantly API, collects the ideal customer profile and offer, and then scores draft email copy with a ten-expert panel until it reaches 90 out of 100.
The result is a strategy document with every scoring round, final copy in Instantly format, capacity math and stop and start lists. Nothing is pushed to Instantly without explicit approval.
What You Get
- An infrastructure report on campaigns, sending accounts, warmup scores and which accounts are ready to send
- A confirmed ideal customer profile with an anti-profile and a one-sentence offer
- Every scoring round with a score per panelist, the top weaknesses and the revised copy
- A strategy document with final email copy, an implementation plan, capacity math, weekly metric targets and STOP and START lists
- Optional scripts for lead sourcing, competitor change reports and cross-source signal detection
Common Use Cases
- Auditing an existing Instantly setup to find what to stop and what to start
- Writing a first cold email sequence for a new offer and testing it against a panel
- Estimating how many emails and replies a set of warmed accounts can produce each month
What Makes It Unique
The score target of 90 is a hard gate, and every round stays in the final document so the reasoning is visible. Accounts are flagged as not ready when warmup is under 80 or under 14 days, and capacity is worked out from ready accounts only. A human review gate sits before any write to Instantly.
Under The Hood
The skill holds instructions, four reference files and five Python scripts. At start it runs the repository’s version check and telemetry helper through the shell and says usage is logged locally with remote telemetry opt-in. The audit script calls the Instantly API with a key the user supplies. The lead pipeline calls people search, email validation and campaign APIs. The competitor monitor fetches competitor pricing and blog pages over HTTP and keeps snapshots on disk. The signal detector reads agent output files in a data folder. The sender script sends email by SMTP or by a command line mail tool using credentials from environment variables, and it keeps a send history file with a daily cap. The agent writes the strategy document, so it writes files or a document too.