Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My launch date cannot move and the software is not ready

Short answer

When the date cannot move, the only things that can change are what is included and how it is launched. List what must work on day one, move the rest to a second release, and test that short list fully. A smaller launch that works is better than a full one that fails in front of customers.

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

Does this sound like your situation?

  • The date is tied to an event, a contract or an announcement.
  • Features are still being added with only weeks left.
  • Nobody has tested the whole thing from start to finish.
  • The developer says it will make it, but cannot show it.
  • I am afraid to launch and afraid to postpone.

Why does this happen?

  1. Scope grew while the date stayed

    Features were added without removing others. The result is more work in the same time, and the schedule quietly slips.

  2. Testing was left for last

    Bugs found in the last weeks need time to fix and recheck. When testing starts late, it fills the whole remaining time.

  3. Nobody agreed what 'launch' means

    A launch can be a public release, a small group of customers or a demo for an investor. Each needs a very different amount of work.

  4. Outside parties work on their own timetable

    App store review, payment account approval or domain changes are decided by others. Plan for them early as fixed delays.

What can I do about it today?

  1. Write the one-sentence purpose of the dateWhat must be true on that day? Be specific, for example that customers can sign up and pay.
  2. List must-have, nice-to-have and laterMark every feature under one of the three. Only the first group is allowed to block the launch.
  3. Ask for the whole path testedRequest a test of the full customer path from start to finish, on a real device, this week.
  4. Check the outside stepsAsk which steps depend on another company, such as store review or payment approval, and whether they are started.
  5. Prepare a plan BAgree in advance what you will say or do if a part is not ready, so the decision is not made in a panic on the last day.

When should I bring someone in?

  • Less than a few weeks remain and the must-have list is not finished.
  • Nobody can give a straight answer about what is working.
  • The launch includes payments or personal data, where a rushed release is risky.

How do I handle it?

  1. Find what really worksI run what exists and sort it into working, broken and not started, in writing.
  2. Cut scope with youTogether with you I move everything not needed on day one into a second release, and write it down.
  3. Test the short list properlyThe must-have path is tested end to end, including a backup before release and a tested way back.
  4. Launch in a controlled wayWhere it is possible, release to a small group first, watch the system, and then open it to everyone.

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?

Should I move the date instead?

Sometimes that is the better choice, especially with payments or sensitive data. The page helps you decide from facts about what works.

Can extra developers make it faster?

Rarely at the last minute. New people need time to learn the code, and that can slow the work.

What if the app store has not approved it?

Review time is decided by the store. Submit early and keep a plan that does not depend on a specific approval day.

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.