# cscron · your post-sale motion, on cron Explore Sales as Code . Role lander # See what each customer needs next. Help you keep the customers you win, understand whether they are getting value, and prepare expansion conversations you can justify. ## Customer success work you can inspect One of nine connected roles ### See what each customer needs next. Adoption, renewal and support signals become the customers who need attention, a proposed check-in, and an expansion case only when the evidence supports one. Preview Customer success work[Explore all nine roles](https://salesascode.com/#team) ## Before the role can act Needs | Produces | Your decision | Customer records in your CRM | Handoff brief and success plan | Confirm the owner and next step | Customer health and renewal evidence | Health and renewal review | Choose the customer action | Adoption and account evidence | Proposed expansion brief | Review fit and customer consent | Needs actual customers and connected customer signals: a CRM, and where you use them a billing account and a support or success platform, several of which are in preview. Before those exist it can explain the setup and prepare a handoff template; it will not manufacture a health report. Full role overview, examples and schedules [Start cscron](https://salesascode.com/signup) **$99/person/month, every role included** · runs on our servers, nothing to install · draft-first · ledger-gated touches [Build your team](https://salesascode.com/signup)[See this role's day](https://salesascode.com/docs/library/cscron) ## What lands on your desk CS ### Research that keeps its sources Open the saved work to review the evidence and context behind a recommendation. CS ### Work prepared for your review Your post-sale motion, on cron. ## It works with the rest of your team. Shared company context keeps the role's recommendations relevant. Open Today to review decisions across the roles you own. Example output **Customer success daily brief** ### Human ownership, whenever you are ready. Assign this role to a teammate. They take responsibility for its work and review actions under the configured permissions. [Explore role assignment →](https://salesascode.com/docs/library/team-on-cron) Explore the team ## What this role does for you How it starts from your website, the work it performs, what you receive, an example, the input it needs, how to judge it, where its work goes, and what it depends on. CS · Customer success Help you keep the customers you win, understand whether they are getting value, and prepare expansion conversations you can justify. The first sale becomes more valuable when the customer adopts, renews and has a reason to expand. This role carries the goals promised during selling into the work after purchase. ## How it starts with your website Receives the buyer goals and commitments from the sales handoff. It adds CRM, billing, support and success-platform signals as you connect them; without customers it explains the setup it needs and stays quiet. ## What the role does for you - Track realised value against what was promised, weekly, and list the customers with open threads awaiting a reply, daily. - Review adoption, engagement, support issues and renewal timing with the limits of each signal visible, and rank who needs attention and why. - Draft check-ins, review agendas and recovery plans for the accounts at risk, and a quarterly business review on a monthly schedule. - Prepare an expansion case only when usage and stated needs support it, and name reference candidates only with real evidence. - Send customer outcomes, objections and approved proof back to positioning and content. On its own schedule: 3 scheduled tasks, 5 more on request - Mondays · 06:15 UTC Value realized per account, folded into the health score - Monthly, day 1 · 06:15 UTC Customer QBR built from usage, outcomes and open risks - Daily · 06:15 UTC Replies scanned and responses drafted for the accounts that answered Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console. ## The work you receive - A customer handoff brief and a proposed success plan. - Health and renewal reviews with the evidence and the missing data named. - Check-in drafts, review agendas and the next action per account. - Expansion briefs and reference candidates that still need the customer's consent. ## An example in practice A customer's adoption falls while a support issue stays open. The role proposes a recovery conversation and asks the sales role to hold the planned expansion message until the issue is understood. A scenario to show the shape of the work, not a customer result. ## What it needs from you Confirm customer goals, own the relationships that matter, and decide on concessions or commercial changes. Review each proposed action. The role assembles the evidence so you are not reconciling usage reports and support threads by hand. The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup. ## Expected outcomes and how to judge them Visible customer needs and timely actions that support adoption, retention and expansion where it is earned. A health score is a signal, not proof a customer will renew. ### Measures worth watching - Time to the value milestones you agreed, where they are tracked. - Renewal coverage, at-risk actions completed, and how customers respond. - Renewal, retention, expansion and churn tied to customer records. ## How the handoff works Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next. - ### To Customer support **What moves:** A customer risk that needs an issue resolved. **What happens next:** Coordinate the response and bring the resolution back. - ### To Account executive **What moves:** A supported expansion need or a renewal conversation. **What happens next:** Prepare the commercial next step. - ### To GTM strategist **What moves:** Customer outcomes and recurring needs. **What happens next:** Improve targeting and the proof the site can use. ## When it is useful, and what it depends on Needs actual customers and connected customer signals: a CRM, and where you use them a billing account and a support or success platform, several of which are in preview. Before those exist it can explain the setup and prepare a handoff template; it will not manufacture a health report. - Customers on the record - CRM connected - Billing, support or success signals (optional, some in preview) Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue. Explore this role's capabilities ## The name is literal. cscron ships 3 scheduled tasks. This is the actual default week: the health pulse and the at-risk digest run whether or not anyone remembered to look, and every customer touch waits for your approval. When | What runs | Mondays · 06:15 UTC | Value realized per account, folded into the health score | Monthly, day 1 · 06:15 UTC | Customer QBR built from usage, outcomes and open risks | Daily · 06:15 UTC | Replies scanned and responses drafted for the accounts that answered | Times are UTC. The runtime dispatches three times a day, at 06:15, 12:15 and 17:15 UTC, and each task takes one of those windows. You can turn any of them off in the console. // the gate ### Nothing reaches a customer without you. cscron drafts. It does not send. A draft is refused at the send layer until a signed-in person approves that exact draft, and there is no scheduled path, agent or automation in the product that can do the approving. That is a check in the code, not a setting to remember. Sending is off on a new account and stays off until you turn it on. With it off, an approved draft is recorded as held rather than sent, so you can run the whole thing for a month and read what it would have said. ## Built to protect and grow the book. ### Renewals never sneak up A 90-day renewal forecast keeps every upcoming renewal in view with its risk and the play to run, so the save conversation starts in time, not the week before. ### Expansion from real usage Unused seats, adopted features, and growth signals become a drafted upsell aimed at the account that’s ready, not a blanket campaign. ### Draft-first, ledger-gated touches Customer touches are drafted and rate-limited by a contact ledger so accounts never get over-messaged. Nothing reaches a customer without your yes. ## The line we hold ### Draft-first Anything that reaches a customer waits for your yes. Touches, save plays, expansion nudges: drafted for you to send, never sent for you. ### Weighted by what it is worth The at-risk digest is ordered by ARR, not by how recently somebody complained. A quiet six-figure renewal outranks a loud small one, which is the ordering a CSM would choose with time to think and rarely has. ## Put your book on cron. $99 /person /month [Get started](https://salesascode.com/signup) [See pricing](https://salesascode.com/pricing#products) Licensed and steered from salesascode.com · siblings: gtmcron.com · salescron.com · leadercron.com · secronjob.com · partnercron.com · bdrcron.com · crocronjob.com · supportcron.com ## Questions people ask How much does cscron cost? $99 per person per month, or $1,089 a year. That is the price of the whole platform: one seat licenses cscron and every other role, and adding a teammate adds a seat at the same price. What does cscron include? A daily health pulse, an ARR-weighted at-risk digest, onboarding tracking, renewal forecasts, expansion signals, ledger-gated customer-touch drafts, reply tracking, a book scorecard, and a daily learning pass. Does cscron message customers on its own? No. Customer touches are drafted and rate-limited by a contact ledger so accounts are never over-messaged, and every draft waits for your yes before it sends. What does cscron run on? Our servers, on a schedule, with nothing to install. You connect your CRM and customer-success tools in the product; we custody those tokens encrypted and isolated per tenant, read them only on your schedule, never sell your data, and never use it to train models. You can revoke access anytime. --- 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).