Helper CTO Series 11 | What's Included in Your Maintenance Fee, and What Isn't

"Two vendors quoted maintenance plans, one cheaper than the other, but I can't tell what the difference actually is." The gap in the cheaper plan usually doesn't show up until the day your server goes down — the vendor tells you "that's a separate quote," and while you're waiting for that quote, you're losing orders. You're not bad at comparing prices; no one ever told you where the line between "included" and "not included" usually falls. The following four things will help you make sense of any maintenance plan you're handed.

Called "Maintenance" Either Way, the Contents Can Be Very Different

There's no standard spec for a maintenance plan. A quote that says "monthly maintenance" can actually mean three completely different things:

• Just a guarantee someone will pick up the phone: you can reach someone when something breaks, but everything else is billed and scheduled separately.
• A guarantee someone is watching: the server, errors, and security updates are handled on a regular basis, and small changes are included too.
• A guarantee someone is moving things forward: on top of watching, a block of engineering time is set aside every month to push your system forward.

All three can be called "maintenance," so of course the prices differ. Before you compare prices, figure out which of the three categories the other vendor actually falls into, then talk about whether it's expensive. The article The Three Ways Maintenance Fees Are Calculated covers the billing structure — this one goes one level deeper, into what's actually inside a single monthly fee.

One Table Shows You "Included" and "Not Included"

Here's our own plan laid out as an example. The one you're holding might not look exactly like this, but every row should have a matching answer:

To judge whether a plan is offered in good faith, check whether the first four rows all fall on the "included" side. If security updates or bug fixes get pushed to "quoted separately," what your monthly fee is actually buying is just a point of contact. For why quotes can vary so much, the article Why Software Quotes Can Vary So Much goes into more detail.

What "Monthly Engineering Capacity" Means

This is the term people ask about the most. In plain terms: a fixed block of engineering time is set aside for you every month, and that time is yours to use for things like "small changes." Here are five ground rules:

• Small things get done right away: editing text, adjusting a field, adding a dropdown option — no need to send an inquiry and wait for a quote.
• Want more than that? It scales up: once something is big enough to count as a new feature, it moves into the development-work bucket and is billed separately.
• Unused time doesn't roll over: what's reserved is a person's time, not a savings account — if it isn't used this month, it's gone.
• Nothing gets upgraded quietly: moving up to a bigger scope always gets discussed with you first; it never just shows up on next month's invoice.
• Multiple requests in one month get prioritized: if several small things come in during the same month, we'll ask you which one is most urgent.

The third rule is the one people hesitate on most, but it's exactly because it doesn't roll over that we check in with you every month and ask, "Is there anything you'd like adjusted this month?"

Ask These Five Questions Before You Sign a Plan

You don't need to understand technology — five questions are enough to reveal what a maintenance plan really is:

1. Are security updates "included" or "not included"? How often are they done, and is the frequency written into the contract?
2. When a user reports a bug, is it fixed within the monthly fee, or is every single one billed and scheduled separately?
3. Where's the line for a "small change"? If editing one line of text counts, does adding a field or an extra option count too?
4. When you need a new feature, do you have to renegotiate the whole contract, or is there a way to scale up?
5. What happens if you want to cancel next month? Do you get your server, domain, documentation, and records back?

If two or more of these five questions can't be answered clearly, no matter how cheap the plan is, you still don't know what you're buying. For what the contract itself should actually say — especially response times, exit terms, and document ownership — you can check it line by line against the article What Should Be in a Maintenance Contract.

Where Nerdtechnic Draws the Line

• The same team handles all four stages: taking over, maintaining, improving, and continuing development — one team from start to finish, never handed off to a different group partway through.
• Pricing is spelled out upfront: basic maintenance starts at NT$6,000/month, billed monthly, and you can cancel anytime.
• Response times are stated in advance: 1 business day to respond to a server or service issue, 2 business days to respond with an assessment when you report a bug.
• Documentation stays yours: when the engagement ends, the documentation and records belong to you — handing off to someone else never turns into a black box, and you always have a choice.

The real value of a plan isn't how much it includes — it's that you always know exactly what you're buying.

Once you can tell "included" from "not included," all that's left is finding a team willing to draw that line clearly. Nerdtechnic maintains your system as your Helper CTO — like an in-house technical lead, just not on your payroll. The first step is a 60-minute system health check: we only need to see your code, no production credentials required, and within 3–5 business days you'll get a one-page report you can actually understand. If you're holding a maintenance plan you can't make sense of, bring it with you and we'll go through it line by line: Helper CTO: System Maintenance Plan.