# What runs at 06:15 · Sales as Code [← All posts](https://salesascode.com/blog) // the blog # What runs at 06:15 By Sales as Code · 2026-09-04 product engineering Two claims are everywhere in this category right now. One is that the product learns from every deal. The other is that it never sleeps. Both are taken, both are unfalsifiable, and neither tells you when anything happens. Ours is a cron. It fires at 06:15, 12:15 and 17:15 UTC. You can set your watch by it, which is the entire point of publishing the times. ## What a pass actually does At each of those three times a dispatcher walks the roles you own and asks each one which of its skills are due. Due is per skill, not per product: a skill on a daily cadence and a skill on a weekly one do not both run because the clock struck. Around a hundred skills ship across the nine roles, and on any given pass a small number of them are due for you. A skill that runs produces a draft or a ranked item, not an action. It lands in your queue with its reasoning attached, and the morning is four blocks: what is waiting on you, the line, the standup, and closing the day. ## Why fixed times and not continuous Because a founder's attention is not continuous either. A system that trickles work at you all day is a system you check compulsively and then stop checking. Three fixed passes means the queue is a thing that is full when you sit down and empty when you get up. The 06:15 pass is the one that matters: it is the reason there is something to read before the first meeting rather than after the last one. There is a fast lane beside it, for the signals that genuinely decay in minutes: an inbound form, a champion leaving, a usage collapse. Those do not wait for the next pass, and each carries its own target response time. Everything else waits, because everything else can. ## Why we say the times out loud Because a schedule you can state is a schedule you can be held to, and because "overnight" and "nightly" were both false when this page said them. There is a test in the repository that fails the build if the marketing copy describes the schedule as anything other than what the dispatcher does. That is a strange thing to have to enforce. It is also the difference between a claim and a fact. [Run it on your company → free audit](https://salesascode.com/audit?utm_source=blog&utm_medium=content&utm_campaign=post) --- More for agents: [llms.txt](https://salesascode.com/llms.txt), [full reference](https://salesascode.com/llms-full.txt), [OpenAPI](https://salesascode.com/openapi.json), [sitemap](https://salesascode.com/sitemap.xml).