Helper CTO Series 20 | What We Take and What We Don't: And Why We Say So Upfront

"You haven't even looked yet, and you're saying you can't quote a price?" That's right — and we'd rather make you a little annoyed on the very first call than have you discover three months into working together that we were thinking of two different things, because by then you'll have lost an entire quarter. You're not being screened out as a customer, you're having your time saved. Below are the following nine situations, and we'll spell out, for each one, whether we take it or not.

Saying What We Don't Take First Is Us Taking You Seriously

A company that takes everything usually isn't deep at anything. The more practical problem, for you, is the chain reaction that follows:

• Someone takes on work they actually can't do well, and you only find out months later.
• By then, both money and time are already spent, and the system is still stuck where it started.
• Switching providers means finding someone new, handing everything over again, and explaining the whole backstory all over again.

So we draw the line up front. You'll know from the first conversation whether you're in scope or not — if you're not, we'll say so directly, and you can go find someone better suited right away. That saves you far more time than a polished proposal ever would.

The Six Most Common Situations, at a Glance

The left column is the situation, the middle is whether we take it, and the right column is what actually matters — the reason:

This table is simple to use: find the row closest to your situation and look at the middle column. If it says "take it," we can keep talking. If it says "don't take it," you've just saved yourself a phone call today.

The Four Situations We Take

1. A system already exists and needs someone to own it long-term: built by an outsourcer, left behind by an engineer who quit, or built with AI tools — it all counts, as long as it's still running with no one looking after it.
2. Willing to let us look at the current state first: we only need to see the code, not production credentials. We can't tell whether or how to take it on until we've looked.
3. Willing to clean things up into a maintainable state first: no backups, no monitoring, a deployment process that only lives in one person's head — these need fixing first, quoted separately depending on the situation.
4. Looking for a long-term relationship, not a one-time fire drill: billed monthly, cancel anytime, the same team takes over, maintains, improves, and keeps building.

When all four line up, working together is usually smooth. This is also what what Helper CTO actually is covers: like your company's tech lead, just not on your payroll — and a tech lead was always meant to be a long-term position anyway.

The Five Situations We Don't Take

1. Business consulting: how you should run your business isn't something we know better than you, and it isn't our place to decide for you.
2. Business model planning: a system is built to support a model you've already worked out, not to work out the model for you.
3. Company registration, accounting, legal, or marketing: each of these has its own specialty, and being a one-stop shop for all of them just means none of them get done well.
4. Pure staffing that wants hands, not judgment: our value is in judging what should happen first, what shouldn't happen, and who looks after it once it's done.
5. Demanding a quote without a health check first: covered in its own section next, because this is the one most often mistaken for us being difficult.

The first three are "not our specialty," the fourth is "not our value," and the fifth is "not fair to you." As for how to prioritize competing requests, which feature should come first lays out a ruler you can reuse for that.

Why We Always Refuse "Quote Me a Price Without Looking"

A maintenance price quoted without ever seeing the code can only go one of two ways, and neither is good for you:

• Quoted too high: risk you don't actually have gets priced in, and you overpay every month.
• Quoted too low: once work starts, the problems turn out to be worse than expected, and then it's either constant add-on charges or corners get cut.

So the first step is always a system health check: it's paid, priced by system size, no lock-in contract. A 60-minute online meeting, we only need to see the code, and within 3–5 business days you get a one-page report with one of three conclusions: take it over as-is, clean it up first, or a rebuild would actually be cheaper. If someone hands you a monthly number without ever looking, that number isn't an estimate — it's a guess. You can borrow the thinking from managing outsourcing without knowing how to code and just ask them: how did you arrive at that number?

How Nerdtechnic Works With You

• We look before we quote: the number comes only after the health check, with one of three conclusions, and you decide whether to move forward after reading it.
• The same team sees it through, start to finish: takeover, maintenance, improvement, continued development — never handed off to a different group midway.
• Billed monthly, cancel anytime: basic maintenance starts at NT$6,000/month, with no lock-in contract keeping you in.
• The documentation stays yours when it's over: files and records belong to you, so switching providers never turns into a black box.

This list isn't a barrier — it's a manual. Read it, and you'll know exactly where you stand.

Spelling out what we take and what we don't, upfront, is the first step of working together. Nerdtechnic takes over, maintains, improves, and keeps building on systems that already exist, in the role of your Helper CTO, with the same team seeing it through start to finish. The first step is a 60-minute system health check — we only need to see the code, no production credentials required, and within 3–5 business days you get a one-page report you can actually understand, then you decide whether to move forward. If your situation falls into one of the "take it" rows above, we can start talking today: Helper CTO: System Maintenance Plan.