How to Keep Maintenance Fees Viable When the System Seems Too Stable

Background

A client (the "甲方") feels that a highly stable system leaves no work for the operations team, questioning how to continue charging maintenance fees.

1. Make Your Presence Indispensable

Ensure the client notices your involvement. For example, a SQL log grew massive due to crawler activity, filling disks. Instead of merely compressing logs, set up alerts (e.g., disk usage >95%) and notify the client, then manually clean the logs, keeping the client dependent on your intervention.

2. Generate Workload Deliberately

Increase the number of incidents or tasks. One responder shared that a security project that was too solid received a low rating (C) for appearing idle; deliberately lowering security thresholds created more work, leading to a higher rating (A) and larger bonuses.

3. Simulate Problems to Create Billing Opportunities

For long‑running projects that never reach acceptance, fabricate occasional failures—such as randomly stopping a service and claiming hardware faults—to trigger on‑site visits and charge for repairs.

4. Use Person‑Days and SLA Metrics

Quantify effort in person‑days and define clear Service Level Agreements (SLAs). Show the client the manpower invested, avoid double‑selling, and if the client pushes to cut costs, reassess whether SLA commitments can still be met; if not, adjust the SLA accordingly.

5. Leverage SaaS‑Style Pricing

Position the service as a SaaS offering: the client hosts the software on their servers, but you charge for server usage and ongoing maintenance, justifying the price increase as a legitimate cost.

6. Treat Maintenance Like Warranty

Explain that no work means no renewal, similar to a phone warranty. When maintenance is paused, future support will cost more due to staff turnover and knowledge loss; occasional new features can also justify continued fees.

7. Proactive Value‑Added Practices

Provide regular reports, drive progress with vendors, solve user issues directly, and enhance software security. Conduct system stability analyses, highlight reliability metrics, and turn internal reports into client‑facing documents to demonstrate ongoing value.