# Factronics USA — Cold Call Cadence Email Templates **Created:** November 10, 2026 **Author:** Coordenadas **Use:** Outbound call cadence for the sales team. The drafting agent creates these as drafts in each rep's own mailbox, so every template carries the rep's name and personal HubSpot meeting link. **Scope:** Generic across all supplier lines (Linx, Anritsu, EBS, MarkinBOX, ITW Dynatec, Kooltrak, AlTech, Standard Bots). The deal owner fills the application and the product. ## Rules these templates were written against - `../rules/Factronics_Linx_Naming_Rule.md` — every closing names a real product. - `../rules/Factronics_Compliance_Language.md` — the equipment enables compliance, Factronics does not perform it. - `../../Factronics_brand_guide.md` — Hormozi-style direct response, short sentences, one idea per sentence, 5th grade reading level, no em dashes or en dashes. - `05.Factronics_MessageBlockLibrary.html` — buyer vocabulary, not brand speak. All proof points below are drawn from here, nothing invented. - `Factronics_Email_Sequences.html` — house email structure, max 6 lines, no exclamation marks, sign off with name plus `Factronics USA · Medley, FL`. --- ## Token reference | Token | Fill with | Notes | |---|---|---| | `{contact_first_name}` | First name only | | | `{company_name}` | Account name | | | `{application}` | Line-level noun phrase: `date coding`, `metal detection`, `checkweighing`, `part marking`, `cold chain monitoring` | Never a compliance phrase like `FSMA compliance`. "We support manufacturers on FSMA compliance" crosses the positioning line in the compliance rule | | `{product_name}` | **Required.** A real, documented product: `Linx 9800 Series`, `Linx Iris`, `Linx PrinterNet`, `Linx SureClean`, `Anritsu XR75`, `Anritsu M6`, `Kooltrak data loggers`, `MarkinBOX MB3T`, `Patmark PM2` | Never a category like "coding systems." Never an invented model or spec. See the persona-to-product table in the Linx naming rule | | `{owner_name}` | Rep's name | | | `{owner_meeting_link}` | See table below | | ### Meeting links per rep | Rep | `{owner_meeting_link}` | |---|---| | Jovan Gutic | `https://meetings.hubspot.com/jovan-gutic` | | Alejandro Gutic | `https://meetings.hubspot.com/alejandro-gutic` | | Frank Castellanos | `https://meetings.hubspot.com/frank-castellanos` | | Jesus Castro | `https://meetings.hubspot.com/jesus-castro-factronics` | | Nicanor Nunez | `https://meetings.hubspot.com/nicanor-nunez-factronics` (placeholder, TBD) | ### Required validation before any draft is sent - [ ] `{product_name}` is filled with a real product name, not blank and not a category. An unfilled token breaks a standing CEO directive. - [ ] `{application}` is a line-level noun phrase, not a compliance claim. - [ ] `{owner_meeting_link}` matches the rep whose mailbox holds the draft. - [ ] No em dashes or en dashes anywhere, subject line included. - [ ] No exclamation marks. --- ## E1 — Day 1, call with no answer or voicemail **Trigger:** `call_1` no answer or voicemail **Subject:** `I called about your {application} line` ``` Hi {contact_first_name}, I called earlier today and missed you. I am {owner_name} with Factronics USA, in Medley, 15 minutes from Doral. We install and support {application} equipment on manufacturing lines across the Southeast. Most plants only look at {application} after it stops the line. That is the expensive way to do it. {product_name} is what we would put in front of you. Grab 15 minutes here and I will come prepared with your line in mind: {owner_meeting_link} {owner_name} Factronics USA · Medley, FL ``` --- ## E2 — Day 5 **Trigger:** `email_2` **Subject:** `What a 4-hour line stop actually costs` ``` Hi {contact_first_name}, I reached out earlier this week about {application} at {company_name}. Here is why. A single 4-hour line stop runs $3,000 to $8,000 in lost product, labor, and late shipments. Most plants treat that as normal. It is not. {product_name} is built to take that failure point off your line. We have done this for more than 19 manufacturers in food, pharma, and industrial, and we will bring the equipment to your plant to prove it. Is {application} on your list right now? {owner_meeting_link} {owner_name} Factronics USA · Medley, FL ``` --- ## E3 — Day 12 **Trigger:** `email_3` **Subject:** `15 minutes on your {application} line` ``` Hi {contact_first_name}, Timing matters, so I will keep this short. Fifteen minutes is enough for me to tell you whether {product_name} fits your {application} line, or whether you are better off leaving it alone. Either answer is worth having. If someone else runs {application} at {company_name}, point me to them and I will take it from there. {owner_meeting_link} {owner_name} Factronics USA · Medley, FL ``` --- ## E4 — Day 15, cadence close **Trigger:** `call_5` no answer, cadence close **Subject:** `Last note from me on {application}` ``` Hi {contact_first_name}, I have not been able to reach you, so this is my last note for now. If {application} becomes a priority at {company_name}, {product_name} is the one to ask me about. Reply here or book a slot directly: {owner_meeting_link} We are local, we answer the phone, and we drive to the plant. {owner_name} Factronics USA · Medley, FL ``` --- ## EB — Busy on the call, no time agreed **Trigger:** `email_followup`, contact was busy, no date agreed **Subject:** `A better week for {company_name}` ``` Hi {contact_first_name}, Thanks for picking up. You were in the middle of something, so I will not add to it. Short version. We put {application} equipment on lines across the Southeast, and we are 15 minutes from Doral. A visit costs you nothing but the 15 minutes. When the line calms down, {product_name} is the one to look at. Pick any slot that works: {owner_meeting_link} {owner_name} Factronics USA · Medley, FL ``` --- ## ET — Contact asked for information **Trigger:** information requested on the call **Subject:** `The {product_name} details you asked for` ``` Hi {contact_first_name}, Thanks for the time on the phone. Here is what you asked for: [ADD REQUESTED MATERIAL] Two things worth noting as you read it. {product_name} handles the {application} side of your line, and IQ/OQ/PQ documentation is included with every installation we do, ready for your auditor to review. Once you have been through it, 15 minutes is enough to answer whatever it raises: {owner_meeting_link} {owner_name} Factronics USA · Medley, FL ``` --- ## What changed from the v0 drafts and why The v0 templates were structurally sound as a cadence but read as generic SDR boilerplate. Any distributor could have sent them. Specific corrections: | Change | Reason | |---|---| | Every closing now names a product through `{product_name}`, placed in the second half after the pain | The Linx naming rule is a June 2026 CEO directive and applies to emails. All six v0 templates failed its first self-check item | | Removed the em dash from the E1 subject line | Standing style rule, no em dashes or en dashes anywhere in copy | | Dropped "Best regards" | House style is peer-to-peer. The sequences library signs off with the name plus `Factronics USA · Medley, FL` | | Replaced brand speak with buyer vocabulary. Cut "that is the area where Factronics supports manufacturers," "I can share how teams in similar operations approach it," and "we work with manufacturers on {application}" | The Message Block Library's stated language rule is buyer vocabulary, not brand speak | | E3 no longer says "whether Factronics is a fit." It now promises a useful answer either way | The v0 line framed the 15 minutes around Factronics qualifying the prospect. The house pattern frames the ask as value delivered to the prospect, as in "¿15 minutos para una evaluación de tu línea?" | | Replaced "Reply with a time that works for you" with the rep's meeting link | Removes the scheduling work from the prospect. The meeting link was already the documented CTA destination | | Added the documented differentiators: Medley and 15 minutes from Doral, Southeast coverage, more than 19 manufacturers in food, pharma and industrial, equipment brought to the plant, we drive out | Every one of these is in the Trust and Diff blocks of the Message Block Library and all were missing from v0. Nothing here is invented | | Added the $3,000 to $8,000 line-stop figure in E2, restated line-agnostic | Pain 04 in the Message Block Library. Hormozi-style copy needs a number and a consequence. V0 had neither | | Rewrote the `{application}` sentences so the token reads naturally in context | "we work with manufacturers on {application} at {company_name}" produced awkward output for most token values | ### Deliberate exceptions, logged - **ET names the product in the subject line.** The Linx naming rule says the product belongs in the second half and never in the opening hook. That rule targets cold content. ET is a warm reply to an explicit request, where the product name is the most useful thing in the inbox. Decided, not missed. - **`{product_name}` as a token rather than a hardcoded product.** The naming rule assumes content written for one product line. These templates serve every supplier line, so compliance moves from authoring time to send time. This is why the validation checklist above treats an unfilled `{product_name}` as a blocker. ### Compliance check No template claims Factronics performs compliance work. The only compliance-adjacent line is in ET, "IQ/OQ/PQ documentation is included with every installation we do, ready for your auditor to review," which is listed verbatim in the Allowed column of `../rules/Factronics_Compliance_Language.md`. --- ## Open items 1. **Roster mismatch.** `../../04_hl_subaccount_config/v1/research/07_team_members.md` is marked source of truth and lists Michael Hernandez in sales, with no Nicanor Nunez. The meeting link list above has Nicanor and no Michael. If Michael is still selling he needs a link. If he has left, that file needs updating. 2. **Nicanor's meeting link is a placeholder.** `nicanor-nunez-factronics` is assumed, not confirmed. Verify before the agent drafts on his behalf. 3. **Spanish variants not written.** Cluster #1 is Miami food and beverage and the Hermes sales pipeline spec calls for Spanish-first there, so these six need ES twins before the cadence runs on that cluster.