Email permutation

How email permutation works

Most companies settle on a small set of local-part patterns for staff. Patterns such as first dot last, first initial plus last, and first only at the company domain show up again and again. An email permutation tool takes a first name, last name, and domain, then emits those candidates in a list 1.

RichAPI's Email permutator is a free browser tool that does exactly that 1. The page is explicit that the patterns are guesses 1. The tool cannot tell which of the candidates a company actually uses 1. That honesty matters, because a list of nine lookalike addresses is still a list of hypotheses.

The dangerous next step is blasting all nine addresses and reading bounce webhooks. That method trains mailbox providers to see a noisy sender. It also creates hard bounce events that damage sender reputation 1. The permutator page itself warns that sending to all nine and watching which ones bounce hurts sender reputation 1.

Two safer paths sit beside permutation. First, copy the format from one known good address at the same company, or look up a published company email format when it exists 1. Second, call an email finder that returns a single best address with a status field instead of a raw guess list 2.

RichAPI Email finder accepts a name and company domain, or a profile URL, and returns email plus email_status 2. A successful call costs 5 credits 2. A waterfall miss that finds nothing bills zero credits 2. New accounts get 100 free credits with no card required 2.

When a team still wants to test a short candidate list, email verification remains the gate before send. RichAPI Email verifier checks one address for 2 credits 3. It returns status, disposable, and mxFound so dead domains leave before the ESP ever sees them 3. A miss with no verdict bills zero 3. Permutation then becomes an input to verification, not a license to spray.

Why email permutation still shows up in GTM workflows

Permutation persists because it is cheap and local. A spreadsheet formula can spit out candidates without an API key. That convenience is also the trap. Cheap guesses feel free until the bounce rate shows up in Postmaster Tools and the domain needs a month to recover.

Modern GTM stacks should treat permutation as a brainstorming aid, not as a send list. The RichAPI permutator exists to make the guess step visible and to push people toward find-and-verify flows 1. Company profile pages that publish an email format give an even stronger prior when one real address already revealed the pattern 1.

Agencies building clay-style tables often generate permutations in bulk, then need a policy for what happens next. The policy should be: never send the raw permutation set. Run Email finder when a person identity exists 2. Run Email verifier on any remaining manual candidates 3. Keep catch-all domains on a slower track because SMTP acceptance there proves little.

Product builders who expose "guess email" features inside a CRM sidebar should show confidence honestly. Label outputs as candidates. Require a verify or find step before the sequence enroll button activates. Otherwise the product becomes a reputation liability for every customer domain connected to it.

Cost math favors finder-first for most B2B motions. One Email finder success at 5 credits often beats a stack of manual guesses on cost and clarity 2. Verifying eight leftover permutations costs 2 credits each on Email verifier 3. Verification still matters after the find when the status is weaker than valid 3. The 100 free credits on a new RichAPI account are enough to compare both paths on a sample 2.

Operators who skip these checks usually discover the damage in reply rate, not in the ESP accept log. The accept log only says the receiving server took the message. It does not say the message reached a person. Closing that gap is the point of the work before the next wave leaves the queue.

Example of using permutations without burning the sending domain

A recruiter has a name, a company domain, and no public address. They open the RichAPI Email permutator and generate the usual candidate set 1. Instead of mailing all of them, they call Email finder with the same name and domain 2.

The finder returns one address with email_status valid for 5 credits 2. That row enters the sequence. If the finder had missed, billed false would show zero credits, and the recruiter could fall back to Email verifier on two high-probability permutations before deciding whether to send 3.

A worse alternate path would paste all nine permutator outputs into a sequencer. Even if two accepted, the hard bounces on the rest would tax domain reputation for everyone else on that domain 1. The free permutator page exists to show the guesses, then to steer the workflow into find or verify 1.

New RichAPI accounts can run that comparison with the 100 free credits that arrive without a card 2. The lesson sticks after one sample: permutation is a generator, not a contact list.

Email permutation vs email finder

Permutation invents candidate addresses from patterns. An email finder returns one best address from providers, with a status field meant for automation.