secronjob

Overview

secronjob runs an enterprise sales engineer's day on a schedule, on our servers. Ten scheduled tasks run the technical side of the deal 24 x 7 x 365: demo prep briefs, a weekday POC tracker with stall alerts, evening discovery synthesis and demo follow-up drafts, the Monday demo-environment health check, and Friday's SE synthesis + answer-library curation. On demand: RFP/security-questionnaire drafting, solution-architecture docs, and SE→CS handoffs that list every promise made in the cycle, verbatim, with source. There is nothing to install.

What this role does for a founder

Technical answers for the deal, before you have a sales engineer to give them. Help buyers understand whether your product solves their technical problem, using answers your team can stand behind.

Uses the product facts from your website and the confirmed brief, then the documentation, proof points and evaluation notes you add. An unknown capability stays unknown until you confirm it; the role never fills a gap with a guess.

Before it has work

• Product documentation and proof points
• An evaluation or buyer question to work
• Evaluation records entered by hand

Where its work goes

• To Account executive: A supported answer, an evaluation result, or an explicit gap. Update the deal plan and the reply to the buyer.
• To GTM strategist: Recurring technical needs and objections. Refine positioning and prepare content that answers them.
• To Partnerships: A technical win, and the enablement material a partner needs. Reuse the proof with partners instead of answering the same question twice.
• To You: Evidence of a product limit that affects buyers. Choose the product or commercial response.

Needs technical source material and a real question or evaluation. Evaluation records are entered by hand today; no integration feeds them. It does not invent certifications, validate security claims on its own, or promise roadmap features. The full overview, with the work, outputs, an example and the measures to watch, is on the Sales engineer page.

The two hard rules

• Draft-first. Anything addressed to a human waits for your yes.
• Technical truth only. Capability claims come from your product docs source and your answer library. A questionnaire question with no library answer is marked "needs product input", never improvised. Security answers are never guessed.

Get started

1. Buy a seat at /pricing ($99 per person per month, which licenses this role and every other one), then set up at /onboarding.
2. Open your console and connect your CRM and inbox in Settings. We custody each token encrypted and read it on the schedule; there is nothing to install.
3. In the console, run setup ("run secronjob setup"): identity, product-docs source, AE pairings, demo environment, answer library, connector checks, schedule registration.
4. Choose where drafts land in Settings: an in-app draft queue, or your Google Drive. Nothing is sent without your approval.

Works alongside salescron (your AEs) and leadercron (your leader, who then sees the whole technical cycle in team rollups). Licensing: Licensing & renewal.

Built-in SE craft library

secronjob ships with a deep, cited SE craft library so your technical drafts read like a seasoned pre-sales engineer from day one, before you have uploaded a thing. It covers technical discovery depth (the requirement behind the feature ask), POC success criteria and exit plans, the demo storyline (tell-show-tell, map-to-metric), same-day demo follow-up, answer-library discipline (vetted reuse, no bluffing), technical objection handling (real blocker vs FUD), technical multithreading, and the competitive teardown. On your first scheduled run these notes seed your knowledge library, so every AI draft grounds on real SE method instead of generic prose.

This craft grounds how to run a technical evaluation. Your proof points, the stats, benchmarks, and named results a draft cites, come only from the sources you upload in the console Library tab, so a draft never presents a playbook line as your customer's outcome. Full grounding model: Persona Console.

Your console (runs on our servers, nothing to install)

By the numbers (live). secronjob ships 13 hosted skills, 3 of them on an auto-run schedule (daily driver: discovery-synthesis). Tier: front-line. These counts are read from the live registry, not hand-typed.

secronjob has a control surface in your browser at /secronjob/console. It drives the hosted runtime that runs secronjob's agents on our servers on a schedule, so nothing depends on you keeping an app open. Scheduled AI work runs on your own provider key (Claude, OpenAI or OpenRouter; every tier is bring-your-own-key), after any platform-funded first-run allowance the deployment turns on. The free deterministic checks need no key. A key turns drafting on; nothing is sent until you turn the send layer on. Bedrock is built but not accepting keys yet; Settings shows it as coming soon until the transport is validated.

Today and Activity link to the original work in this workspace. Work also opens saved research and drafts. A direct link can retrieve an older finding or draft beyond the recent queue. Research expands its facts and quotes; historical drafts keep their status and disable unavailable edit actions.

Under its heading the console shows the one number secronjob was hired to move: the first week of connected data after the hire, day 30, day 60 and your target, or a note naming the connection that would supply a missing week. A role with no number the platform can measure says why instead. You pick the number and set the target on Home.

• Schedule. A runtime on/off switch, plus every skill with its cadence and tier. Toggle any skill or run one now.
• Draft queue and Runs. Review the drafts your runs produced and see what ran, when, and what it cost.
• Live coach (front-line seats). On-demand interactive coaching: practice a live buyer roleplay, build a pre-call brief for a connected meeting, draft a reply to an inbound thread, write a deal-specific battle card for a competitor, or draft the lesson out of a deal you closed. Draft-only, on your budget, nothing sent.
• Build. Probe an MCP server you have already connected to see the tools it offers, and check a custom skill draft against the same compiler the fleet runs. Both are read-only: probing lists tools without calling one, and validating saves nothing.
• Settings. Budget meter, identity, and bring-your-own-key.

Delivery. Output is draft-first and lands where you choose: your in-app draft queue by default, and optionally your Google Drive "Accounts" folder, where the console names the last files that landed so you can tell delivery is working without going to look. For a security-strict team that needs real Gmail or Outlook drafts and CRM writes on their own credentials, an optional self-hosted path (n8n on your own machine) is available. Nothing is ever auto-sent. Full walkthrough: Persona Console.