Ask ten business owners what does a CTO do, and you will get ten versions of "the best programmer in the company." That answer is wrong, and it is an expensive kind of wrong. It leads owners to hire a senior developer, give them an executive title, and then wonder why the technology roadmap still does not exist.

I have spent over a decade in and around this role, from leading a frontend division at a comics platform serving hundreds of thousands of users to running delivery for enterprise clients. The honest answer is this: a CTO is paid for judgment, not typing speed. The code is the easy part.

If you run a business between ten and two hundred people, this distinction matters, because it changes what you should hire, when, and at what price.

The Job Is Judgment, Not Code

A good CTO spends most of their time on decisions that never show up in a code repository:

  • Build vs buy. Should you build a custom inventory system, or will a Rp 500 thousand per month SaaS subscription cover 90 percent of your needs? Getting this wrong in either direction costs real money. Building what you could have bought burns six months of salary. Buying what you needed to own creates a ceiling you hit two years later.
  • Vendor and hire evaluation. When a software vendor quotes Rp 400 million for a project, is that fair, padded, or dangerously cheap? A CTO has seen enough proposals to smell all three.
  • Risk calls. Which shortcuts are safe to take before launch, and which ones will corrupt customer data at 2 AM on a public holiday? Every system has technical debt. The skill is knowing which debt charges interest.
  • Translation. Turning "we need to grow revenue 40 percent" into a concrete technical plan, and turning "the database needs sharding" into a business case the owner can approve or reject.

Notice that none of this requires the person to write your code. It requires them to have written and shipped enough code, and cleaned up enough disasters, that they can predict outcomes before you pay for them.

What a CTO Is Not

A few common mislabels worth clearing up:

  • Not your fastest developer. Great developers often make poor CTOs because the skills barely overlap. One optimizes for elegant solutions, the other for business outcomes under constraints.
  • Not your IT support. Fixing printers, managing laptops, and resetting passwords is IT operations. Important, but a completely different job at a completely different price point.
  • Not a project manager with a technical accent. A PM keeps a project on schedule. A CTO decides whether the project should exist at all.

If your "CTO" spends their week closing tickets, you have a developer with an inflated title, and nobody is doing the actual CTO work.

Most SMEs Do Not Need a Full-Time CTO

Here is the part most consultants will not tell you: a full-time CTO is overkill for the majority of small and mid-sized businesses.

A competent full-time CTO in Indonesia costs Rp 40 to 80 million per month, often more with equity. That salary makes sense when technology is your product and you make architecture decisions weekly. For a distribution company, a retail chain, or a services firm where software supports the business rather than being the business, the genuine CTO-level decisions arrive maybe once a month.

Paying a full-time executive salary for a few decisions a month is the same mistake as hiring a full-time lawyer to review two contracts a quarter. What you actually need is access to senior judgment when the decisions appear. That can look like:

  • A fractional or advisory CTO, a few days a month, who reviews vendor proposals, sets the roadmap, and sanity-checks major decisions.
  • A project-based engagement when you are undertaking something big, like replacing your core system or evaluating an ERP implementation.
  • A trusted technical partner on retainer who your team can call before signing anything expensive.

This is not a downgrade. It is matching the cost structure to the actual demand.

The Trigger Points: When You Genuinely Need One

There are moments when senior technical judgment stops being optional. Watch for these:

  1. You are about to spend more than Rp 200 million on software you cannot personally evaluate. Custom development, a big SaaS contract, an agency engagement. One review meeting can save you the price of the whole engagement.
  2. Technology decisions are blocking revenue. Orders lost because systems do not talk to each other, staff doing double entry between three tools, reports assembled by hand every month.
  3. You have two or more developers and no technical leadership. Developers without direction produce code, not outcomes. Someone has to decide what gets built and to what standard, and it should not be the loudest developer in the room.
  4. A vendor relationship has gone sideways and you cannot tell whether the vendor is incompetent or your requirements keep shifting. Often it is both, and scope creep is usually part of the story.
  5. You are raising money or selling the company. Investors and acquirers will do technical due diligence. Better to find the skeletons yourself, on your own schedule.

If none of these apply, you probably do not need a CTO yet. Bookmark the list and get back to running your business.

How to Evaluate the Person

Whether fractional or full-time, evaluate a CTO candidate on judgment, not credentials. Some questions that work:

  • "Tell me about a project you killed, and why." Someone who has never stopped a project has never made the hard call.
  • "When would you tell me not to build custom software?" A good answer includes specific SaaS alternatives and a cost comparison. A bad answer is enthusiasm about building.
  • "Walk me through the worst production incident you handled." You are listening for ownership and process, not heroics.
  • "What is the difference between a system that works in a demo and one that works for three years?" This one separates people who have operated software from people who have only launched it.

Be suspicious of anyone who leads with technology names instead of business outcomes. The stack matters far less than whether the person can connect technical choices to your P&L. Your business needs a technology strategy, and the CTO role exists to own it.

The Practical Takeaway

So, what does a CTO do? They make the expensive technical decisions correctly, before the money is spent. That is the entire job, and everything else is detail.

For most SMEs, the right move is not a Rp 60 million per month executive. It is structured access to senior judgment: a fractional advisor, a per-decision review, or a technical partner who has seen your situation a dozen times before. Buy the judgment when you need it, at the dose you need.

And if you are staring at one of the trigger points above right now, especially a large vendor proposal you cannot evaluate, get a second pair of senior eyes on it before you sign. I offer exactly this kind of engagement through my partnership model. One honest review is cheaper than one wrong contract.