Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I am starting a new product and want a second opinion on the technology

Short answer

For a new product the right technology is the one your team can build, hire for and run for years, not the newest. Ask why it was chosen, who else can work in it, what it costs to host and what happens if the developer leaves. An independent review compares the choice against your actual needs.

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

Does this sound like your situation?

  • The developer picked the technology and I do not know why.
  • Two people recommend different things and both sound sure.
  • I have heard a choice is 'the future' and cannot check it.
  • I plan to hire later and do not know if people will know this stack.
  • I want to avoid being locked in to one person or one company.

Why does this happen?

  1. Choices follow what the builder knows

    A developer or agency recommends what they work in best. That can be a good reason, but it is not the same as the best fit for your product.

  2. Fashion can beat fit

    New tools are promoted widely. A fashionable choice may have fewer experienced people, fewer answers online and a less certain future.

  3. The needs are not written down

    Expected users, offline use, payments, notifications and integrations should drive the choice. Without a written list, any technology looks fine.

  4. The long-term cost is hidden

    Hosting, upgrades and hiring cost far more over years than the first build. These costs rarely appear in the first proposal.

What can I do about it today?

  1. Write the needs in plain wordsList what the product must do in year one, including who will use it, on what devices, and what it connects to.
  2. Ask for the reasons in writingAsk the person proposing the stack to give three reasons, what they considered instead and what the weaknesses are.
  3. Ask who else could take overFind out how many developers know the technology and whether your own future hire could work on it.
  4. Check ownershipWhatever is chosen, the code, hosting and store accounts should be in your company's name from the first day.
  5. Do not decide under time pressureA stack is hard to change after the build. A short review before the build costs far less than moving later.

When should I bring someone in?

  • You are about to commit a large budget on a choice you cannot judge.
  • The people advising you will also be paid to build it.
  • The product has special needs, such as offline use, live data or heavy video.

How do I handle it?

  1. Start from your needsI turn the idea into a short list of requirements: users, devices, data, integrations and the first year's growth.
  2. Compare a few real optionsEach option is weighed in writing against the list: speed to first version, hiring, running cost, and what could force a move later.
  3. Check the official statusSupport and version status of any framework are taken from its official site, not from opinion.
  4. Give a clear written recommendationThe review ends with one recommendation, the reasons and the risks, so you can show it to anyone else involved.

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 it better to pick the most popular technology?

Popular choices are easier to hire for and have more help available. The right choice still depends on what your product must do.

Should my developer's choice be rejected?

Not automatically. The goal is to understand the reasons and the weak points before you commit.

Can the technology be changed later?

Often yes, but at real cost. This is why the choice deserves an early, independent check.

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.