Custom templates: we design the lure, we do not open the library

This is not the platform’s template library. It is a design service: we clone a real email or we build one from scratch, with published lead times.

How it works

How a commission comes in and a measurable piece goes out

Brief or original

If there is an email to clone, we receive it and the 48-hour clock starts when the original is usable. If there is no original, the brief defines pretext, gesture (click, credential, ransomware) and systems that may be named.

Design by type

Click-only: five business days from scratch. Credentials or simulated ransomware: ten business days, with a fake landing. We do not persist secrets. We do not encrypt anything real.

One round

One round trip on the brief. A scope redesign — another gesture, another system — restarts the SLA. There is no open creative loop.

Load into the module

The piece is ready to fire in simulations. The service does not operate the campaign: it delivers the lure. The native builder remains for what is already in the template library.

Why it matters

Why the template library does not close every request

Because some organizations live their risk in an email only they receive: a union portal, a shift system, a local bank, a payroll vendor. The global catalog will not have that piece with the right letterhead. Cloning it badly is how the…

Why the template library does not close every request
Deliverables

What you get

A piece the module can fire, with the SLA of the scenario type, not extra access to the library.

Clone or design

A clone in 48 hours if the original arrives usable; a from-scratch design in five or ten business days according to the gesture.

Landing when it applies

For credentials and simulated ransomware, the fake page is inside the ten days. No secret persistence and no real encryption.

Loadable piece

The deliverable lives in the simulations flow, not on a mood board. If the gesture cannot be measured, it is not done.

A rule against bad reuse

The piece is for the program. It is not a pack to forward by internal mail as if it were an HR notice.

Requirements and timelines

What we need from you

  • The original to clone, if that is the path, in a format that can be read: HTML, an .eml, a complete capture. An unreadable screenshot does not start the 48 hours. If it is from…
  • Also an owner who answers the round inside the SLA. If review takes two weeks, the clock moves. This service does not ask for a crisis committee or a plant map. It asks for an…
The program

How it fits native simulations

The custom template does not replace the library. It complements it when the catalog does not have the letterhead or the gesture. Once loaded, the module fires it like any other native campaign. The service is not a…

How it fits native simulations
Questions

Questions about custom templates

Is this the platform’s template library?
No. That library is product and lives in the module. This service is commissioned design, with SLAs. If the catalog is enough, do not ask for it.
How long does a clone take?
Forty-eight hours if you send a usable original. That clock does not start on an unreadable screenshot.
And from scratch?
Five business days if the gesture is click-only. Ten business days if there are credentials or simulated ransomware, and that includes the fake landing.
Does the landing store passwords?
No. The flow captures the gesture, not secrets. Simulated ransomware does not encrypt anything real.
Is there a price on the site?
No. It depends on the type and the plan quota. It is quoted. We do not publish a range.

Ask for the lure the library does not have

If the email to clone already exists, the clock is 48 hours. If it has to be invented, five or ten business days. Let’s talk the gesture.

Full catalog on Services