Build · Create · Writing & Content
Build an action-first professional request email
A structured request-email object whose subject line carries an approved precursor, whose body leads with the call-to-action before the context, whose recipients are well-formed and de-duplicated, and which states an explicit ISO deadline.
You receive: A JSON object: { subject: {precursor, line}, to: [emails], cc: [emails], body: {opening_action, context, availability_note}, deadline: {iso_datetime, phrase}, word_count }
Part of Pitch Investors
What's verified: STUD verifies the email's structure: valid precursor on the subject, well-formed and de-duplicated recipients within the cap, an action-first opening containing a required keyword, a body under the word limit, and a parseable future deadline. STUD does NOT judge tone, politeness, whether the recipient list is the RIGHT people, or whether the email will get a reply.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"allowed_precursors",
"cta_keywords",
"require_deadline"
],
"checkNames": [
"format_parses",
"precursor_valid",
"subject_nonempty",
"emails_wellformed",
"to_count",
"no_dup_or_overlap",
"action_first",
"body_brevity",
"availability",
"deadline_present"
],
"constants": {},
"deliverableLabel": "professional_request_email",
"documentKeys": [
"availability_note",
"body",
"cc",
"context",
"deadline",
"iso_datetime",
"line",
"opening_action",
"phrase",
"precursor",
"subject",
"to",
"word_count"
],
"enumLiterals": [],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.