Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Monthly plan

A developer on call for small fixes, set up as a monthly plan

In the monthly bug fix plan you keep one engineer who knows your product, and you send small fixes and changes as they come up. I sort them by risk, fix them against a written scope and report back in writing. The price is quoted after a short discovery call, against a written scope.

Who is Monthly Bug Fix Plan for?

  • Owners of a working app or site that only needs a developer now and then, but the same one each time.
  • Teams whose product is stable and who want small issues handled without opening a new project for each.
  • People who hate chasing a stranger every time a form or a screen breaks.

What does Monthly Bug Fix Plan include?

  • A written review firstI get to know the code and the live system once, so later fixes are quick and I do not start from nothing.
  • A shared list of fixesYou send bugs and small changes into one list, and I sort them by how much they hurt users and the business.
  • Diagnosis before changesI find the real cause first and measure before and after, so a fix is proven and not guessed.
  • Small, safe releasesOne change at a time, a backup before production and a way back, so a small fix does not become a big problem.
  • Mobile, web and back endFlutter and native apps, React and Next.js front ends, and the APIs and databases behind them.
  • A written note per fixEach fix comes with a plain note of what was wrong, what changed and how I checked it live.
  • Honest sizingIf something on the list is really a project, I say so and scope it separately instead of squeezing it in.

What does Monthly Bug Fix Plan not include?

  • Large features or rebuilds. Those are scoped as projects.
  • A promise of a fixed response time. I reply within 24 hours, and urgent work is agreed in the scope.
  • A team of developers. I am one engineer.
  • Work without a written scope. Every month runs against one.

How does Monthly Bug Fix Plan work?

  1. Send me a few linesWhat the product is and what has been going wrong. I reply within 24 hours.
  2. A discovery callA call within 48 hours to understand the product and look at the first problems.
  3. A written scopeWhat the plan covers, how fixes are sent and prioritised and what I report back.
  4. KickoffTypically inside two weeks, with access set up and a backup taken before the first change.
  5. Month by monthFixes worked in order of risk, with written updates and one weekly call when there is something to discuss.

Is Monthly Bug Fix Plan a good fit for me?

A good fit when

  • Your product works but small things keep breaking.
  • You do not need a developer every week, only a trustworthy one when something goes wrong.
  • You want to ask for fixes in plain language, not technical tickets.

Not a fit when

  • You need fixes within the hour at any time of day.
  • Your product is still being built. That is project work.
  • You have a long list of big features rather than fixes.

What do people ask about Monthly Bug Fix Plan?

How is this priced?

It depends on how much change the product tends to need, so I quote after a short discovery call, against a written scope. I do not sell a fixed number of hours up front.

Can a plan cover a very quiet month?

The scope sets what the plan covers, and I review it with you each month, so it can match how much your product really needs.

What if I have an emergency?

Tell me in the first message. I reply within 24 hours, and the scope can name how urgent problems are handled, though I do not promise response times.

Do you fix code another developer wrote?

Yes. I read it first, and I tell you plainly if something is too fragile to patch safely.

Read next

Before you decide

Related projects

All projects

Enterprise · Field data

DCOR

An offline-first field app with three roles, GPS attendance, a dynamic form engine and five languages.

FlutterDartBLoCget_it

Own product · Taxi dispatch SaaS

TaxiDex

My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.

TypeScriptNode.jsAdonisJSNext.js

Consumer app

Raheeb

A consumer app shipped to both stores from one Flutter codebase on a .NET and Azure back end.

FlutterDart.NETAzure

Next step

Monthly Bug Fix Plan: let's talk

A discovery call within 48 hours, and a kickoff typically inside two weeks.