Services Ongoing maintenance

You built it.
We’ll keep it working.

Software needs care after launch: updates, monitoring, fixes and the occasional bad night. We take that on with a senior engineer, a written agreement and no surprises.

production 30 days
  • Dependencies updated and tested
  • Security patch applied
  • Backup restore checked
  • Error spike triaged and fixed

What maintenance covers.

The assessment decides which of these your app needs and in what order. Nothing is bundled in for the sake of a longer list.

Technical assessment
A written review of the code, infrastructure and risks before we commit to anything.
Stabilization
Fix what causes outages, data loss and failed deploys before routine work begins.
Security and dependency updates
Framework, library and runtime updates on a schedule, tested before they ship.
Monitoring and incident response
Uptime and error alerts wired to us, with response during agreed business hours.
Hosting and infrastructure
Servers, databases, backups, domains and certificates kept current and documented.
Testing and CI/CD
Tests around the flows that make you money, and a deploy you can repeat.
Architecture
Small structural fixes that make the next change cheaper, raised before they become rewrites.
Feature work
Small improvements inside the monthly agreement. Larger features are scoped and quoted separately.

How it works.

  1. Assess

    A paid, fixed-scope review. You get a written report on risks, what to fix first and whether ongoing maintenance makes sense. Yours to keep either way.

  2. Stabilize

    A short, scoped project to fix the urgent problems from the assessment: broken deploys, missing backups, exposed secrets, failing tests.

  3. Maintain

    A monthly agreement with a defined amount of time, written response windows and a monthly summary of what changed.

  4. Improve

    Once it is steady, part of each month goes to the improvements that matter most to your users and your team.

Is this a fit?

A good fit if

  • Your app is live, or close to it, and people rely on it
  • Whoever built it has moved on, or is busy with new work
  • You want updates, monitoring and fixes handled without hiring
  • You can give us access to the code, hosting and accounts

Probably not a fit if

  • You need someone on call around the clock
  • You want unlimited changes for a flat fee
  • The app is a prototype you plan to throw away
  • You need a full product team for a large new build

App built with Lovable, Bolt, Replit or an AI coding assistant? Read about maintaining AI-built apps.

Questions.

Do you maintain software you did not build?

Yes. Most maintenance work is on code someone else wrote: a former employee, an agency, a freelancer or an AI coding tool. That is why every engagement starts with an assessment.

What technologies do you work with?

Web apps and APIs, native iOS and Android apps, PostgreSQL and the common hosting platforms. Tell us your stack in the form. If it is outside what we can support well, we will say so before you pay for anything.

Is support 24/7?

No. Monitoring runs all the time, and we respond within the windows written into your agreement, during business hours. We do not sell round-the-clock on-call because we cannot staff it honestly.

Is maintenance unlimited?

No. Each agreement includes a defined amount of time each month. Work beyond that, or larger features, is scoped and quoted before it starts.

Can you guarantee nothing will break?

No one can. We reduce how often things break, find out quickly when they do, and fix the cause instead of the symptom.

What does it cost?

It depends on the size and condition of the app. The assessment is a fixed fee agreed up front, and it tells us both what a monthly agreement should include.

What if we want to stop?

The notice period is written into the agreement before it starts. When you leave, you keep everything: code, documentation, credentials and the notes we wrote.

Stephen Way

Tell us what you’re running.

A few sentences about the app and what keeps going wrong. We reply within two business days with next steps or an honest no.

You work with Stephen Way directly, building for the web for 20+ years. Frontend, systems, CI and testing: the work that falls between teams. Built Fjord. More about Stephen

Takes about a minute. Stephen reads every inquiry himself.

What do you need?

A few sentences is plenty: what it does and what keeps going wrong.

Is it live? Optional
When do you want to start? Optional
Budget for the first piece of work? Optional
Add more detail
Who works on it today? Optional

Free first call. Reply within two business days.