Nairobi, Kenya

Maintenance & Support

Someone accountable for the software after it launches.

Launch is the start of the cost, not the end of it. A retainer covers the unglamorous work that keeps a system healthy: dependency and security updates, monitoring the things that actually break, small improvements, and a defined route to reach a human when something goes wrong.

Typical investment

KES 25,000180,000

Per month

The response time we commit to in writing, hours included each month, and whether we are on call outside business hours. As a planning rule, budget 15–25% of the original build cost per year.

The band narrows to a single fixed price in a signed statement of work before any work begins. See bands for every service.

What you get

Deliverables, not adjectives

These are the items written into the statement of work. Anything you need beyond them is quoted separately rather than assumed.
  • Security patching and dependency updates on a regular schedule
  • Uptime and error monitoring, with alerts going to us rather than to you
  • Backup verification, including periodic restore tests
  • An agreed pool of hours each month for small changes and fixes
  • A named contact and a written response commitment during support hours
  • A monthly report of what was done, what changed and what needs attention

Good fit for

Is this the right service?

If none of these describe your situation, say so on the call — we would rather redirect you than take on work that is a poor fit.
  • Companies with a live system and no in-house engineer
  • Teams inheriting software whose original builder has moved on
  • Businesses that need patching evidence for audit or compliance

Technologies

The ecosystems we work in

Read these as options our engineers are experienced with, not a fixed stack. The actual choice is made with you during scoping, based on what you already run and who will maintain it afterwards.

Monitoring

Uptime checksSentryLog aggregationSynthetic tests

Patching

Dependency scanningAutomated update PRsCVE tracking

Resilience

Automated backupsRestore drillsStaging environments

Ticketing

Shared issue trackerEmail intakeChange log

How we work

From first call to handover

  1. 01

    Discovery call

    A free 30-minute conversation about the problem, the constraints and the budget range. If we are not the right fit, we say so on this call.

  2. 02

    Scope & written quote

    We define what the first release includes and excludes, then quote it as a fixed price in a statement of work you can take to procurement.

  3. 03

    Design & architecture

    Screens and data model agreed before the build. Changing a diagram is cheaper than changing a shipped feature.

  4. 04

    Build in increments

    Short cycles with something reviewable at the end of each. You see progress in a working environment, not in a status report.

  5. 05

    Test & launch

    Functional, performance and security checks, a staged rollout with a rollback path, and a launch date agreed rather than announced.

  6. 06

    Handover & support

    Documentation, training and code in a repository you own — followed by a support retainer if you want us to keep it running.

Questions

What buyers ask before signing

Will you maintain software you did not build?

Yes, after a short paid review to see what we would be taking on. If the codebase is in a state where we cannot support it responsibly, we will tell you what would need to change first.

What is your response time?

It is written into the retainer and tiered by severity — a payment outage is not a copy change. We commit to hours we can actually meet with the team we have.

Do unused hours roll over?

The retainer states this explicitly. Our default is that a portion carries into the following month so you are not pushed into making work up.

Let's scope your maintenance & support work

Tell us the problem and the constraints. You get a written scope and a fixed price within three working days — or an honest note that this is not something we should take on.