What does a website maintenance retainer comparison show?
This calculator compares two monthly retainers and one per-ticket maintenance quote using the same monthly work schedule.
A low retainer can become expensive when hours exceed the allowance, while quiet months can leave paid hours unused.
Use actual quotes before renewing a maintenance agreement or choosing a support arrangement for an existing website.
The decision differs from commissioning a new website or comparing the full lifetime cost of a custom platform with SaaS.
This model connects included hours, rollover, expiry, excess charges, minimum commitments, and payment months.
Amounts are KRW cash payments on one consistent tax-inclusive basis; the model does not calculate tax rates, deductions, or legal entitlements.
Read three outputs together
- Total cash payable for the same maintenance requests
- Excess charges, expired hours, and the closing balance of eligible hours
- Cash needed for advances, following-month invoices, and remaining minimum-term fees
Align the maintenance scope before comparing prices
Two vendors can define a request differently.
Text and image updates, bug fixes, security updates, and a new payment integration may fall into different contractual categories.
Separate paid maintenance from free defect correction and separately quoted new functionality, then include only paid maintenance requests and hours in the monthly schedule.
Confirm these terms in writing
- The definition of one ticket and rules for splitting or combining requests
- Covered websites, pages, plugins, work types, and exclusions
- How work hours are measured and approved, including authorization of excess work
- Defect correction terms and separate development quotes
Use each option’s separate monthly quote for agreed out-of-scope work.
A fixed monthly amount cannot reproduce an irregular development invoice exactly, so keep a separate budget when payment timing varies materially.
Matching prices alone do not establish matching services or responsibilities.
Enter monthly requests and total work hours
Enter between 1 and 24 observation months, with the paid request count and total work hours for each month.
The per-ticket option uses the count, while retainer excess charges use the hours.
A simple banner update and a difficult bug fix may each count as one request but consume very different time.
- Remove free defect correction and separately commissioned development from the maintenance log.
- Enter request counts separately for ordinary months and campaign or redesign months.
- Enter the total hours needed for those requests in the same month.
- If demand will rise, revise both the relevant count and hours.
A month without requests must have zero requests and zero work hours.
A positive count with zero hours, or positive hours without a request, requires correction.
Blank is not treated as zero; entering zero explicitly represents no work or no charge.
Understand the retainer, allowance, and rollover cap
The monthly retainer is payable even when little work is requested.
Included hours are the current month’s allowance, and the rollover cap limits how much unused current allowance can move into the next month.
This calculator supports rollover that lasts for the next month only, with no re-rollover of the previous month’s balance.
Consume the older balance first
Work first uses valid opening rollover and then the current month’s allowance.
Any remaining work is charged at the hourly excess rate.
Unused opening rollover and unused current allowance above the rollover cap expire.
The balance eligible to roll forward at the end of the observation period is shown separately.
It is not deducted as a refund or cash saving.
Quarterly pooling, multi-month accumulation, or indefinite rollover requires a different ledger or a revised quote on the supported terms.
How hours are used, carried, and charged
Consumption and excess
Rollover used = min(opening rollover, work hours)
Current allowance used = min(included hours, max(0, work hours − opening rollover))
Excess hours = max(0, work hours − opening rollover − included hours)
The next month’s balance
New rollover = min(rollover cap, included hours − current allowance used)
Expired hours = opening rollover − rollover used + included hours − current allowance used − new rollover
Excess charge = monthly round(excess hours × hourly excess rate)
Each month’s excess charge is rounded to the nearest whole KRW before summing.
For fractional hours, this can differ from rounding the entire period only once.
Confirm any minimum billable duration, per-task rounding increment, or out-of-hours surcharge separately with the vendor.
Include the complete minimum commitment
A retainer’s billable months equal the greater of observation months and minimum-term months.
Observing three months of work does not remove a six-month contractual fee commitment.
Months after the observation period are modeled with no requests or work, and their base fees are identified as remaining commitment beyond the observed period.
Retainer cash = setup fee + billable months × monthly fee + observed monthly excess charges + observed months × separate monthly quote + emergency cash
Per-ticket cash = setup fee + total requests × ticket price + observed months × separate monthly quote + emergency cash
Enter every quote and unit price on the same confirmed tax-inclusive payment basis.
Mixing a tax-exclusive quote with an inclusive quote can make a tax-basis difference look like a contract advantage.
The calculator does not determine tax treatment, input-tax recovery, or accounting deductions.
Automatic renewal, early-termination penalties, refunds, discounts, and deposits are not applied automatically.
Separate advance fees from following-month invoices
Equal totals can require different cash at the start.
Setup fees are paid in month one, and base retainer fees are paid at the start of each prepayment block.
The final block includes only the remaining billable months, rather than adding months after the modeled contract ends.
- Monthly payment places one month’s base fee in each month.
- Three-month prepayment collects up to three months of base fees at the start of the block.
- Excess work, ticket fees, and separate monthly quotes are paid in the month after the work.
- Emergency cash is paid in the selected disruption-scenario month.
The last observed work month can therefore leave a ticket or excess invoice payable in the following month.
The payment schedule reconciles to contract cash; estimated business loss is not added to that schedule.
If your actual invoice and settlement dates differ, reconcile the modeled months with the written payment terms.
A worked example with uneven monthly demand
Assume requests of 2, 8, and 2, requiring 2, 8, and 2 work hours across three months.
Setup fees, separate monthly quotes, and disruption costs are initially zero.
All example prices are synthetic calculation inputs, not market averages or recommended rates.
Synthetic terms and total cash for two website maintenance retainers and a per-ticket quote| Item | Retainer A | Retainer B | Per ticket |
|---|
| Base fee or ticket price | 100,000 KRW/month | 150,000 KRW/month | 30,000 KRW/ticket |
| Included hours / rollover cap | 4 / 2 hours | 6 / 0 hours | Not applicable |
| Hourly excess rate | 30,000 KRW | 20,000 KRW | Not applicable |
| Minimum term / prepayment cycle | 3 / 3 months | 6 / 1 months | Not applicable |
| Total contract cash | 360,000 KRW | 940,000 KRW | 360,000 KRW |
A carries two unused hours from month one into month two, leaving two excess hours in that busy month.
Its 300,000 KRW base fees plus 60,000 KRW excess charge produce 360,000 KRW total cash, with zero expired hours during observation and a two-hour closing balance.
B costs 900,000 KRW for six months of base fees plus 40,000 KRW excess, totaling 940,000 KRW; 450,000 KRW of base commitment falls beyond observation.
The per-ticket quote costs 12 × 30,000 = 360,000 KRW.
Interpret the example’s timing and unused hours
A’s advance and excess invoice
A requires 300,000 KRW in month one and pays the second month’s 60,000 KRW excess charge in month three.
Its two-hour closing balance is eligible for the next month; no refund is assumed.
The ticket option’s later cash payments
The ticket option pays 60,000 KRW in month two, 240,000 KRW in month three, and 60,000 KRW in month four.
It ties A on total cash but differs in initial funding and final payment month.
Unused hours alone do not prove a retainer is poor value.
The agreement may also cover reserved support capacity or recurring checks that must be compared in the service scope.
Do not multiply expired hours by an excess rate and treat the result as money owed back.
The hour ledger describes usage rather than a refund entitlement.
Break-even means a uniform-demand integer transition
The sensitivity analysis divides total work hours by total request count to obtain hours per request.
It then replaces the observed demand with the same request count in every observation month, testing 0 through 200 requests per month in whole-number steps.
It reports adjacent integer intervals where the retainer-versus-ticket cost relationship changes and preserves ties.
The example has 12 hours ÷ 12 requests = 1 hour per request.
A is more expensive than tickets at 3 requests each month and cheaper from 4.
B ties at 18 requests each month and becomes cheaper from 19.
These results retain the example’s observation period, rates, and minimum commitments.
This uniform scenario is separate from the original uneven request schedule.
With zero total requests, hours per request cannot be defined and the sensitivity result is withheld.
No transition within 0–200 does not establish superiority at every possible demand level.
Seasonality, work duration, separate charges, and disruption assumptions can change the relationship.
Keep response time separate from disruption loss
Response time concerns contact or the start of a response after a request, rather than complete service restoration.
Check business-hour rules, weekends, holidays, and incident priority before treating two response promises as equivalent.
A response time beyond the required maximum, or an unconfirmed SLA basis, withholds the like-for-like lowest-cost conclusion.
Enter confirmed disruption-scenario hours, a common loss per hour, and each option’s emergency cash separately.
The model does not derive restoration time or incident probability from a response promise.
Emergency outsourcing payments and scenario-valued business losses should remain distinguishable.
Adding a disruption scenario to A
Two disruption hours × 50,000 KRW loss per hour = 100,000 KRW loss.
Adding 20,000 KRW emergency cash changes A’s contract cash to 380,000 KRW and its scenario-inclusive cost to 480,000 KRW.
The 100,000 KRW loss is not counted again in the payment schedule.
Turn the result into a written quote request
- Replace synthetic examples with actual vendor names, quotes, and monthly work records.
- Confirm the same tax-inclusive payment basis and maintenance scope.
- Confirm rollover validity, excess authorization, minimum term, and prepayment cycle in writing.
- Enter response times on the same SLA basis and build disruption scenarios separately.
- Read cash, remaining commitments, payment months, and sensitivity together.
- Download the TXT comparison and request written clarification of missing terms.
Confirmation boxes start unchecked.
Loading an example does not establish that a contract has been verified, and the lowest-cost conclusion stays withheld until all three options satisfy the comparison conditions.
Equal-cost options remain tied; the calculator does not rank vendor quality, reliability, or legal compliance.
Frequently asked questions
Is the lowest monthly retainer always cheaper?
Compare included hours, excess rates, minimum commitments, and separate fees together.
A busy month’s excess charges can reverse the apparent advantage.
Can unused hours accumulate indefinitely?
This model allows next-month-only rollover with no re-rollover.
Indefinite balances or quarterly pooling require different calculations.
Should free defect correction count as paid requests?
Separate work confirmed as free under the actual agreement from paid maintenance.
The calculator does not determine a legal entitlement to free correction.
Where do I put new functionality?
Enter confirmed out-of-scope charges in the separate monthly quote.
Keep an additional budget for large one-off development or different payment dates.
Why does a three-month plan show six months of fees?
A six-month minimum term remains a six-month base-fee commitment.
Termination rights, refunds, and penalties must be checked separately against the agreement.
Does a faster response automatically reduce downtime?
Response and restoration are separate conditions.
Enter the confirmed disruption scenario for each option independently.
Why can sensitivity differ from my monthly result?
The main result uses the actual uneven schedule, while sensitivity uses uniform monthly demand.
Rollover limits and expiry can change excess charges even at the same total request count.
Are the initial prices market estimates?
They are synthetic examples for checking the calculation.
Use current actual quotes and confirm scope, the tax-inclusive payment basis, and contractual terms.
Official references and verification date
References were checked on 2026-11-16.
KOSA’s notice registered on 2020-12-30 and the Ministry of Science and ICT’s distribution material dated 2020-12-31 provide reference structures for scope, agreed changes, and payment terms in maintenance contracts.
These are verified 2020 distribution materials, not a claimed latest 2026 contract revision.
The references do not set universal included hours, revision counts, or rollover caps.
Recheck actual prices, scope, validity periods, SLAs, and billing conditions whenever the quote or agreement changes.
Prepare a maintenance requote using real work records
Enter actual monthly work and quote terms above, then identify busy months and upfront funding as well as total cost.
Share the normalized result to negotiate included hours and payment terms more precisely.