Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Do I need a CTO, or is a good developer enough?

Short answer

You need a CTO's job done when nobody owns the technical decisions: which tools, who has access, what it costs, whether the developers' work is sound. That does not have to be a full-time hire. Many small businesses need that job part time, and a developer alone does not cover it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I cannot judge whether my developer's advice or quotes are fair.
  • Nobody can tell me what my app, servers and accounts are, or who owns them.
  • Releases are late and nobody can say why.
  • I am about to hire developers or sign with an agency and do not know what to ask.
  • An investor or a buyer is asking technical questions I cannot answer.

Why does this happen?

  1. Developers build, but nobody owns the decisions

    A developer writes code. Someone else has to decide priorities, tools and risk, and check the work. In a small business that someone is often the owner, who is not technical.

  2. Technology grew project by project

    Apps, sites, servers and vendors were added one at a time. Nobody drew the whole picture, so costs, accounts and risks sit with whoever set each one up.

  3. A full-time CTO is not always the right size

    A company with a small team may need direction, review and planning for a few days a month, not a full-time executive.

  4. The first technical hire is hard to judge

    Without someone to read a CV, a quote or a test project, a non-technical owner may pay for the wrong skills.

What can I do about it today?

  1. Write the list of what you ownApps, websites, domains, servers, store accounts, paid tools and the person behind each.
  2. Confirm every account is in your nameDomain, hosting, Apple and Google developer accounts, code repository. These are the things that hurt when a developer leaves.
  3. Write your three biggest technical worriesSlow releases, outages, cost, security, a key person. Plain words, one line each.
  4. Ask your developer to explain one decisionA good one can explain a choice in words you understand. Note how the answer feels.
  5. Do not sign a long contract yetGet the picture first, then choose the size of help.

When should I bring someone in?

  • A big decision is coming, such as a rebuild, a new vendor or a funding round.
  • Your only developer is a single point of failure.
  • Spend or outages keep growing and nobody is accountable.

How do I handle it?

  1. A short discovery callYou tell me about your business, your systems and your worries. A written scope follows the call.
  2. A map of what you haveA plain-language list of systems, accounts, owners and risks.
  3. Direction in sprintsPriorities planned in two-week sprints, code and vendor review, and releases kept under control.
  4. Hands-on where neededI also write code, so a decision is checked against real work. You can stop at any point.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is a CTO the same as a senior developer?

No. A senior developer builds well. A CTO is accountable for direction, risk and cost across the whole technology.

Can it be part time?

Yes. That is what a fractional CTO is. See the plan page for how it works.

When is a full-time CTO better?

When the technology is the core product and the team is large enough to need daily leadership.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.