Maintenance, support and development for your existing systems

Having a system already does not mean you must start again. We review what you have, write down what is worth keeping and what must be fixed, then develop and maintain it under a clear plan.

Entry point
Monthly maintenance and support plan
Duration
Monthly
Price
Starting from 400 SAR per month

Overview

Many companies run a system that works, but nobody dares touch it: a developer who is no longer around built it, there is no documentation, and it is slow or fragile. Replacing everything is costly and disruptive. Leaving it alone is costly too, because every failure arrives at a bad time.

We start with a free call and define the review or repair scope in a written offer. A comprehensive assessment of a complex project has a paid diagnostic agreed in advance. Nothing changes before the work plan is approved; then we carry out priced batches of fixes, performance work, interfaces, data, reports and integrations within scope.

You can add a monthly maintenance plan: an agreed number of hours, a monthly report of what was done and what remains, and a defined way to raise requests. The 14 days of free fixes apply to what we delivered, after delivery, and are separate from the paid maintenance plan.

What the service covers

Development, maintenance and technical support

Already having a system does not mean you need to start over.

We can:

  • Review the current system
  • Fix problems
  • Improve performance
  • Add new features
  • Develop the interfaces
  • Improve databases
  • Add reports and admin dashboards
  • Connect the system to new services
  • Carry out periodic maintenance
  • Provide technical support
  • Run continuous development plans

Who this is for

  • An outside developer built your system and is no longer available, and nobody in your company knows how it works.
  • Screens or reports are slow, and sometimes stop at busy times.
  • You want to add a feature but fear breaking something that works.
  • You have no backup that has actually been restored as a test.
  • Your team works around the system with Excel files because it does not cover what they need.
  • You do not know what the next changes will cost and want to know before you start.

Problems we solve

A system with no documentation

Nobody knows how it works, so every change is a gamble and the knowledge sits with one person who may leave.

Repeated failures with no diagnosis

Symptoms get patched again and again without finding the cause, so the same failure returns a few weeks later.

An addition that breaks something else

When changes are not tested against what already works, a healthy part can fail because of an edit in another part.

Slowness and risk to data

A database that grows unmanaged and backups never restored as a test, so the owner finds the problem on the day the copy is needed.

Change costs you cannot predict

A developer works by the hour with no ceiling, and you learn the cost only when it is billed. That is why we price every change and get your approval before doing it.

What you receive

Every deliverable has written acceptance criteria, and you review it before paying the instalment tied to its stage.

A written review report

It describes the system's structure and risks and what can be fixed quickly, with a work list ranked by impact and cost. No change starts before it is approved.

Agreed fixes, verified before and after

Each problem has a description and a clear way to check it, so we show that it is gone instead of saying we dealt with it.

Performance improvements against agreed checks

Before work we agree which screens and reports we measure and how, then compare afterwards. We do not promise figures we cannot measure.

New features, reports and admin dashboards

Each addition is priced before it is built and has written acceptance criteria, and is tested against what already works so it does not disturb it.

Database tuning and a restore test

We tune what slows queries, clean what we agreed to clean, and set up backups whose restoration is actually tried and written down.

Documentation of the system as it is

A file describing components, accounts, dependencies and procedures, so any developer after us can carry on.

A monthly report for plan subscribers

What was done, hours used, open requests, and our recommendations for the next month.

How the work runs

Five steps. At each one there is something for you to review or approve before we move on.

  1. 1

    A call to define the work

    A free call identifies the problem, systems and permissions, followed by written repair or review scope. A paid diagnostic is agreed for complex projects only.

    Your part: You review scope and costs before any implementation or access to your accounts.

  2. 2

    Work list and written offer

    We rank the work by impact and cost and write an offer for the first batch, with a scope and acceptance criteria for each item.

    Your part: You choose what is done first and approve it in writing, then pay the first instalment (40%).

  3. 3

    Small batches with a preview

    We work on a test copy first, take a backup before any change, and show you the result before it is moved to the real system.

    Your part: You see the improvements and fixes on the test copy. The second instalment (30%) is paid when they are previewed.

  4. 4

    Regression testing and acceptance

    We test what we changed and what surrounds it, to confirm that what worked still works, and write down the results of the agreed checks.

    Your part: You review the results and accept the delivery in writing. The final instalment (30%) is paid after that.

  5. 5

    Handover and the monthly plan

    After the last payment we move the changes, hand over the documentation and leave the temporary access. We fix defects in what we delivered free for 14 days, and an optional monthly maintenance plan is available.

    Your part: You decide whether to subscribe to the plan, and how many hours suit you.

What we need from you

  • Temporary access to the system, code, database and hosting, opened by you in your name and left after handover.
  • Any documentation, earlier contracts or notes from the previous developer, even if incomplete.
  • A list of known problems, with screenshots or examples of cases that actually happened.
  • A person who decides which changes are approved and in which order.
  • A test copy of the system, or a safe way to test changes before they reach the real one.

What this looks like in practice

How to start

Start with a free call and an offer defining the work. Monthly support is optional, with written hours, scope, target response time and a monthly report. If the system needs rebuilding or enterprise integrations, a separate paid diagnostic precedes the implementation offer.

Monthly maintenance and support plan

An optional plan after the free-fix period ends, with a scope and number of hours agreed in advance.

Duration
Monthly
Price
Starting from 400 SAR per month

Complex-project diagnostic (5 working days)

For complex work that needs assessment before implementation can be priced. Deliverables are agreed before the start; simple services begin with a free call and a written offer.

Duration
5 working days
Price
Fixed fee 1,200 SAR

All prices and offers

Questions about this service

Can you work on a system you did not build?

Yes, after reviewing it. We read the system and write down what we found and what can be done. If the source code or necessary access is not available, we tell you in writing what is and is not possible, before you pay anything for implementation.

What does the monthly maintenance plan include?

An agreed number of hours each month for monitoring and fixing failures and making small changes, plus a monthly report of what was done, hours used and open requests. Anything beyond the agreed hours is priced before it is done, and the plan renews only by our agreement. Service hours, the target response time and coverage are defined in the written offer.

What is the difference between the 14 days of free fixes and the maintenance plan?

The free fixes cover defects in work we delivered, within 14 days of handover. The maintenance plan covers your systems in general, after that period, and is paid monthly. New features are not defects, and are priced before they are done.

Do you provide hosting?

We do not sell hosting. Hosting and licences are opened in your name and priced separately, and we work with temporary access. We help you choose what suits your system and configure it, and the account stays yours.

What if replacing the system is the better option?

We write that in the review report with the reasons and a comparison of developing versus replacing. The decision is yours, and we do not start a new project until you approve its scope in writing under a separate offer.

How are fees paid?

For each batch of work, in three instalments tied to the work: 40% at the start, 30% when the result is previewed, and 30% on acceptance and approval. The maintenance plan is a monthly subscription. We never ask for the whole fee upfront.

Describe your current system

Write to us about what you have and what bothers you about it, and we will reply with the next step. The introductory conversation is free.