The Outreach Operating System
A prompt pack gives you something to send. It does not tell you who to send to, how many per day, what to do with the replies, what to say when they push back, what to charge the client, or what to fix when week three comes back with nothing. Those are seven separate decisions, and this is those seven decisions written down.
Payment link is being wired. Files land on this page immediately after payment.
Each block below is a decision you stop making from scratch. That is the whole product.
01 Target list standard
After this file you can look at a list of two thousand addresses and tell whether it is worth sending to before you send, and you can spot the eight things that predict a bounce before the bounce happens. You get four tests a company has to pass to belong on the list, ten source types named with how to pull from each, and a volume formula so the number of records you need follows from your daily send count instead of being guessed.
02 The 90 day sending calendar
After this file you can open one table and see the whole quarter. Three 30 day phases, a 13 week ramp from five sends a day to forty, rest days marked, and a hard rule that caps any week at 25 percent above the last one so you cannot detonate a domain in a fit of enthusiasm. Each week lists which prompts fire, so you are never deciding what to write from a blank page.
03 Permission and compliance sheet
After this file you can write a compliant footer in about a minute, you know the four things an opt out has to do to count, and you can explain to a client why you will not send to a purchased list, in numbers rather than in principle. It ends with a 20 item check you run before a campaign goes out, and it says plainly, twice, that it is operating guidance and not legal advice.
04 Inbox triage decision tree
After this file you can open your inbox and clear it with a rule instead of a mood. Six branches, each one ending in numbered next actions: interested, not now, wrong person, hostile, out of office, and the one that is really a question in disguise. Each branch also names what not to do, which matters more than the action when a reply looks like a win and is not.
05 Objection library
After this file you have a reply for the twelve things buyers actually say, each under eighty words, written as an owner who has heard it before rather than as someone selling. It also covers why each reply works, so you can adapt the wording to your own voice instead of copying a script that will read like a script.
06 Pricing and packaging
After this file you can put a defensible price on your first three clients. The founding rate is derived in four arithmetic steps from what the work costs you to run, not picked to sound confident. Three tiers are separated by deliverable rather than by adjective, there are seven refusals written out so you can decline badly fitting work without improvising, and a four step method for raising your rate later with two scripts attached.
07 Failure runbook
After this file a flat week is a checklist rather than a crisis. Three named failures, each starting with a signal check so you know which one you are in, then three changes in order with one at a time, each with a test for whether it worked. Includes the things not to do, which usually means not rewriting the email for the fourth time.
$97 one time
No subscription, no renewal, no upsell waiting at checkout. Pay once, the files are yours, and you are not on a list that emails you every Tuesday.
What happens right after payment. The payment goes through, you land back on this page, and the download links are on it, in the same browser window, with nothing to confirm and no email to wait for. Seven files, listed, ready to save. If your browser closes before you get them, the link in your receipt opens the same page again.
Reply to support@xevolution.biz within 7 days of buying, with the word refund, and you get the full 97 dollars back. No form to fill in, no reason to give, no call to book first. You write one email from the address you paid with and the refund goes back through the original payment method.
That is the whole policy. It exists because a written system either earns its place on your desk or it does not, and you are the only one who can tell.