Skip to content
Book a free 30-minute call with an engineer

Software Maintenance & Support

Monthly care for software that's already live.

Raheel Tech PM screens

Software that isn't maintained gets slower and less secure every month. Dependencies go out of date, OS updates break things, and small bugs pile up. Our maintenance plans keep your app healthy, whether we built it or another team did.

Each plan includes monitoring, security updates, bug fixes and a set number of hours for small improvements. You get a monthly report showing what we did, and a named engineer who knows your codebase.

What’s included

Pick the parts you need. Most projects use all of them.

  1. 01

    Monitoring & incident response

    Uptime and error monitoring, with agreed response times when something breaks.

  2. 02

    Security updates

    Regular dependency updates, patching and vulnerability scans.

  3. 03

    Framework & OS upgrades

    Keeping React, Next.js, Laravel, Flutter and mobile OS targets current.

  4. 04

    Bug fixing

    Triage and fixes with clear priorities and a shared ticket board.

  5. 05

    Performance work

    Speed checks, query tuning and caching as usage grows.

  6. 06

    Small features

    Ongoing improvements from a monthly hour bank.

What you walk away with

  • Onboarding audit of code, infrastructure and risks
  • Monitoring and alerting setup
  • Monthly maintenance report
  • Agreed response and resolution times
  • Named engineer and shared ticket board
Printgraphi screens

Printgraphi, Online printing marketplace

Tools we use

We choose per project. These come up most often for maintenance & support work.

InvoiceList.tsxTSX
1export function InvoiceList({ invoices }: Props) {​
2 const [filter, setFilter] = useState<Status>("open");​
3 const visible = useMemo(​
4 () => invoices.filter((i) => i.status === filter),​
5 [invoices, filter],​
6 );​
7​
8 return (​
9 <section>​
10 <StatusTabs value={filter} onChange={setFilter} />​
11 {visible.map((inv) => (​
12 <InvoiceRow key={inv.id} invoice={inv} />​
13 ))}​
14 </section>​
15 );​
16}​

How a project runs

Five stages, two-week sprints and a demo at the end of every one.

  1. 01  Week 1

    Discover

    A couple of workshops with your team. We map the users, the must-haves and the risks, then send a written scope with a fixed estimate.

    MVP roadmapSprint 4 of 6 · launch in 3 weeksLater2Next2Now2Done3Referral codesGrowthDark modeUIAdmin exportsBackendPush remindersMobileStripe checkoutPaymentsOnboarding flowDesignSign up & loginAuthBooking APIBackendStore listingReleasev1.0 live
  2. 02  Weeks 2 to 4

    Design

    User flows, wireframes and the visual design in Figma. You click through a prototype, and we test it with a few real users before any code.

    Home · v2StaylineLisbon, 3 nights12 to 15 May · 2 guestsFree cancellation until FridayTotal€486Book nowColourTypeAaHeading 32Body 16 / 1.5Caption 12ComponentsPrimarySecondaryToggleTested with 6 users ✓
  3. 03  2-week sprints

    Build

    Code, tests and a staging site you can open any time. Every sprint ends with a demo, so you always see what changed.

    app.yourcompany.com/ordersNorthdeskOverviewOrdersCustomersInventoryReportsSettingsOrders142 this month · $48,210+ New orderOrderCustomerStatusTotal#1042Maple StudioNew$3,400#1038Harlow LtdPaid$1,240#1039BrightwayPending$860#1040Okafor & CoPaid$2,115#1041NordlineShipped$540Order #1042 created
  4. 04  Go-live

    Launch

    Security checks, load testing, App Store and Play Store submission, then a production release with monitoring switched on.

    ~/app — zsh$ git push origin mainEnumerating objects: 14, done.To github.com:acme/app.git 4f2a1c9..b81e0d3 main → mainCI triggered: pipeline #482Instances3 / 3 healthyCPU 64% · autoscale onPipeline #482main · b81e0d3BuildTestDeploy
  5. 05  After launch

    Improve

    We watch the analytics, fix what users trip over and keep shipping features. Most clients keep us on after launch.

    Uptime · last 30 days99.98%30 days agoTodayResponse time142 msp95 · all regions09:0015:00Incident resolved · 4 minCheckout API latencyRolled back · on-call: SamDeployed to productionv2.14.1Today 09:12Latest

Maintenance & Support: common questions

Can you maintain software another team built?

Yes. We start with a short audit to understand the code, set up monitoring, and fix the highest risks first. After that it's regular maintenance.

How much does a maintenance plan cost?

Plans usually start from about $1,000 a month for smaller apps and scale with the hours and response times you need. We'll recommend a plan after the audit.

What response times do you offer?

Depending on the plan, critical issues get a response within 1-4 hours, around the clock on higher tiers. Non-urgent issues are handled during business hours.

Do unused hours roll over?

On most plans, unused hours roll over for one month, so a quiet month isn't wasted.

Is there a long-term contract?

No. Plans run month to month after an initial three-month period, which is the time it takes to get properly familiar with a codebase.

Related services