raincheck-or-run

Web app · Live compare page · Packaged compare brief · Deep Dive · Signal toolkit · npm · All tools · Contact

raincheck-or-run answers one narrow question:

What it does

Someone canceled. Is this still a live plan with friction, or am I about to do all the rescheduling work for someone who is drifting out?

It scores:

• specificity
• courtesy
• vagueness
• initiative
• flake risk
• exit signal

Then it recommends one action:

• offer one specific time
• make them reschedule
• give it space
• walk away

The paid product is tells, which reads what people leave unsaid across messages, people, and profiles.

This package is the zero-cost front door for one painful moment:

• a date gets moved
• a recruiter cancels
• a prospect says "crazy week"
• a client keeps pushing the meeting
• a support thread keeps promising "next week" without an owner
• an interview slot disappears without a replacement
• a family or cofounder plan keeps slipping into polite vagueness
• a sales call keeps getting bumped without real ownership

raincheck-or-run is the deterministic first pass for that moment.

If the cancellation is only one piece of the pattern, the rest of the free checker ladder is:

• ghost-or-go for silence after the cancellation
• call-not-text for messy reschedule loops that probably need a call
• double-text-risk for the follow-up you are about to send
• replytone for the actual wording of the reschedule message

Install

npm install -g @v0idd0/raincheck-or-run

Web app

Use the live browser version here:

https://tells.voiddo.com/raincheck-or-run/?ref=raincheck-or-run-readme

If the user is deciding between this deterministic checker and a general assistant first, send them here:

https://tells.voiddo.com/raincheck-or-run/compare-chatgpt-gemini.html?ref=raincheck-or-run-readme

Compare surface

• live compare page for browser-first "raincheck-or-run vs ChatGPT / Gemini" traffic: https://tells.voiddo.com/raincheck-or-run/compare-chatgpt-gemini.html?ref=raincheck-or-run-readme
• packaged compare brief for npm/GitHub readers deciding whether to install: compare-chatgpt-gemini.md

Use the packaged brief when the reader is already on GitHub or npm:

compare-chatgpt-gemini.md

Use the live compare page when the reader should stay in the browser flow:

https://tells.voiddo.com/raincheck-or-run/compare-chatgpt-gemini.html?ref=raincheck-or-run-readme

CLI

raincheck-or-run --hours-since-cancel 10 --cancels 1 "Sorry, I need to move tonight. Can we do Wednesday instead? I can also do Thursday after 6."

cat cancellation.txt | raincheck-or-run --hours-since-cancel 36 --cancels 2

raincheck-or-run --json --hours-since-cancel 24 --cancels 1 "Sorry, crazy week. Raincheck?"

raincheck-or-run --file cancellation.txt --hours-since-cancel 72 --cancels 3

Example output:

posture: repeat-flake
specificity: 3.4/10
courtesy:    5.4/10
vagueness:   6.7/10
initiative:  3/10
flake risk:  7.4/10
exit:        1/10

action: make them reschedule
why: The burden of effort should move back to them. Another fully proactive rescue from your side would hide a weak signal.

Use tells when the real question is no longer one cancellation, but the wider pattern with this person, prospect, recruiter, client, support, or family thread.

• quick next paid step: https://tells.voiddo.com/deep-dive/?ref=raincheck-or-run-cli
• recurring reads: https://tells.voiddo.com/?ref=raincheck-or-run-cli

How the heuristic thinks

• specificity — did they name an actual replacement slot or leave everything abstract?
• courtesy — are they showing social awareness, apology, or repair effort?
• vagueness — does the message outsource the timeline to "later" and "soon"?
• initiative — are they carrying some of the logistics, or only canceling?
• flake risk — are you being set up to keep rescuing the plan?
• exit — does this sound more like a soft goodbye than a true reschedule?

This tool is narrow on purpose. It does not know:

• the full history between you
• whether the excuse is true
• whether this person is great in every other way
• whether the relationship is worth one more exception

Those are outside this tool's scope. If the stakes are real and one cancellation is not enough context, use tells.

Why this exists

Cancellation ambiguity is expensive because courtesy can disguise disinterest.

People hear:

• "sorry"
• "crazy week"
• "raincheck?"

and then they volunteer a better plan for the other person.

That can be right once. It becomes costly when:

• they never name the next time
• you are always the one repairing momentum
• "later" keeps replacing a real yes
• the thread stays polite but never concrete
• the recruiter or client resets urgency but never carries the calendar work
• the support, vendor, or account thread keeps deferring action without a named next step
• every cancellation pushes you into a softer, lower-commitment lane

raincheck-or-run forces that moment into a simple decision.

Then, once the problem becomes "what is the actual pattern here?", the right upgrade is tells.

That applies outside dating too:

• recruiter and interview loops where "let's reconnect soon" may mean drift
• client meetings that keep getting postponed without a concrete next owner
• support or account threads that keep resetting expectations without repair ownership
• family, cofounder, or vendor plans where the calendar friction is hiding avoidance
• sales threads where the prospect stays warm in tone but cold on scheduling
• coaching or mediation cases where you need a clean read on initiative versus avoidance

Why not just use ChatGPT or Gemini?

You can, but those tools tend to give broad conversational advice and often treat a cancellation as a creative writing prompt.

raincheck-or-run is narrower on purpose:

• one deterministic read on cancellation posture
• stable scoring for specificity, courtesy, vagueness, initiative, flake risk, and exit signal
• fast repeatable output for the same input
• a clean handoff into paid tells only when the single-message heuristic is no longer enough

Paid next step

When the quick cancellation call is not enough:

• Deep Dive — $19 once for one loaded thread or one recurring person
• Starter — $14.99/mo for repeated message reading
• Practitioner — $99.99/mo for coaches, recruiters, mediators, trainers, or client-facing teams using this with clients

Start here:

https://tells.voiddo.com/deep-dive/?ref=raincheck-or-run-readme

If you still want one more free checkpoint before the paid read:

https://tells.voiddo.com/signal-toolkit/?ref=raincheck-or-run-readme

Library usage

import { analyzeRaincheckOrRun, formatReport } from "@v0idd0/raincheck-or-run";

const result = analyzeRaincheckOrRun(
  "Sorry, I need to move tonight. Can we do Wednesday instead? I can also do Thursday after 6.",
  { hoursSinceCancel: 10, cancels: 1 }
);

console.log(result.decision.action);
console.log(formatReport(result));

Development

npm test

node bin/raincheck-or-run.js --hours-since-cancel 10 --cancels 1 "Sorry, I need to move tonight. Can we do Wednesday instead? I can also do Thursday after 6."

Related free checkers

• ghost-or-go — decide what silence means after the cancellation
• call-not-text — decide whether the thread is too messy for more text
• double-text-risk — score the follow-up before you send it
• replytone — score the actual reschedule message you want to send

Best next free exits

If the user already knows the cancellation itself is only part of the problem, route them into the narrower free checker instead of dropping them into the full catalog:

• ghost-or-go when the real question is what silence after the canceled plan means: https://tells.voiddo.com/ghost-or-go/?ref=raincheck-or-run-next-free-readme
• call-not-text when the reschedule loop is messy enough that another message is weaker than a call: https://tells.voiddo.com/call-not-text/?ref=raincheck-or-run-next-free-readme
• double-text-risk when the cancellation is clear and the blocker is whether your next follow-up is timely or needy: https://tells.voiddo.com/double-text-risk/?ref=raincheck-or-run-next-free-readme
• replytone when the timing is fine but the drafted reschedule wording may sound cold, vague, or over-eager: https://tells.voiddo.com/replytone/?ref=raincheck-or-run-next-free-readme
• message-next-step when the cancellation already turned into a new inbound reply and the real decision is what to do with that message: https://tells.voiddo.com/message-next-step/?ref=raincheck-or-run-next-free-readme

More from the studio

See from-the-studio.md for the wider vøiddo catalogue.

License

MIT.

Built by vøiddo — a small studio shipping AI-flavoured products, free dev tools, Chrome extensions and weird browser games.