ReplyBudget / METHODOLOGY
Keep the assumptions
beside the answer.
Our tools model work, cash and credits. This page explains their conventions and the evidence required for software claims.
Updated October 20, 2026 · Local preview
Sequence workload
A cohort enters on a working day. Each step applies its retained share to the original cohort and falls after the number of working days you specify. Weekends and excluded dates are skipped. Shares of 1, 0.8 and 0.4 for 1,000 prospects mean 1,000, 800 and 400 actions.
The entry horizon ends when new prospects stop entering. The action calendar continues until every modeled step is finished. Capacity and time reserved for handling replies are separate assumptions. The planner preserves fractional modeled actions; they do not represent a count of people actually observed.
Payments, service and time
Cash includes payments due inside the numbered-month window. Each payment is spread evenly over the service months it buys. The portion consumed inside the window is kept separate from prepaid service beyond it. The model does not infer refunds, calendar-day proration, interest or accounting treatment.
Optional time value equals monthly hours multiplied by the stated hourly rate and window. Economic cost combines consumed cost and time value. Meeting costs require a matching closed cohort and window with a positive denominator; otherwise the ratio is withheld.
Credit units and expiry
Billable action counts are multiplied by their declared weights. Eligible free repeats are subtracted from request counts; a repeat already belongs inside that count. A free status costs no credits, while an unknown billing rule remains unknown when it can affect the result.
Each period follows available quota, consumption, expiry and purchased balances. The model buys a whole number of packs of the size you chose. It does not choose an optimal vendor or pack combination. Different pools need different ledgers. Calendar-based vendor rules must be classified into the numbered periods before calculation.
Precision, blanks and exports
The engines preserve exact decimal or rational quantities before display rounding. Currency amounts use half-up rounding at the final cent; separately rounded values can differ by a cent. Exported fractions keep the underlying precision.
A blank amount means unknown, not zero. Known subtotals stay visible when a complete result is unavailable. CSV exports carry the assumptions and units. Changing calculator inputs marks the old result stale and disables the export until recalculation.
Software evidence
Pricing claims use dated primary sources and identify currency, unit, included functions and commitment. A monthly equivalent is distinguished from an upfront invoice. Conflicting source statements are described rather than silently combined.
A public-page observation is not a product trial. We use “tested” only for an action actually executed and described with its conditions. Comparisons need the same job, window and required functions. Public prices alone cannot establish data coverage, deliverability, support quality or a universal winner.
Illustrative workload and conversion inputs are labeled hypothetical. We have no measured traffic, customer outcomes or financial returns to report for this site. AI assistance may be used in research and development; it is not evidence of a test or a replacement for source checking and independent review.
Changes and corrections
Visible check dates identify when a source was read, not a promise that its offer remains available. Refresh a quote before buying. A correction should identify the affected URL, statement, source and date; the public contact channel is still being prepared.
See the tools, worked guides, privacy and how funding will be disclosed.