Decision methodology
Visible assumptions, not a magic diagnosis.
Fixwise starts with category-level facts a consumer can verify. Model recognition and OCR are optional enrichment and always require confirmation.
Eight-year-old washer
If the repaired washer needs to provide roughly 4.3 additional working years before the comparable replacement becomes economically favorable, Fixwise shows that break-even requirement alongside evidence quality and the assumptions most likely to change it. This example is illustrative, not a prediction.
Inputs that lead the decision
Appliance category and age, repair quote, diagnosis quality, written scope, repair warranty, comparable installed replacement cost, prior failures, likely downtime, warranty or service-plan coverage, recall status, and typical category lifespan.
Core calculations
Repair-to-replacement ratio compares the repair quote with the complete installed replacement cost—not merely the shelf price. Break-even repaired life estimates how long the repaired appliance would need to keep working for repair spending to remain competitive with replacement. TrueCost scenarios may include delivery, installation, removal, required modifications, financing, rebates, and plausible operating-cost differences.
Confidence
Confidence reflects evidence completeness and quality. A written diagnosis, itemized scope, confirmed model information, and repair warranty can strengthen confidence. Unknown cause, verbal-only estimates, missing installed costs, possible recall status, or conflicting information can reduce it and lead to “verify first.”
Safety overrides economics
Potential hazards and possible recalls are surfaced before ordinary cost comparisons. Fixwise does not clear an appliance for continued use.
Sources and review cadence
Product rules and disclosures are reviewed before each distributed build. Category assumptions should be reviewed at least annually and when credible new official or industry evidence appears. Recall checks link users to authoritative sources rather than claiming a complete in-app recall determination. Methodology last reviewed July 29, 2026.