Skip to content

supportmaintenanceautomation

You already shipped it.Now somebody has tokeep it alive.

We take over support, maintenance and automation for teams who have a working product and nobody left to look after it.

Book a callHow it works

30 minutes · no deck

currently keeping 14 systems running for teams in social, telehealth, fintech and ops

  • Slash PostSlash Post logo
  • CompiledCompiled logo
  • LedgerlineLedgerline logo
  • FieldnoteFieldnote logo
  • Harbor OpsHarbor Ops logo
  • Relay PayRelay Pay logo

Three things, and we do all three properly.

Support, maintenance and automation are the same job wearing different hats: keeping something that already works from quietly getting worse.

01

Software support

Your users email us, not you. We triage in your tracker, reply in your tone, and escalate to someone who has read the code. Nights and weekends are a rota, not hope.

12

open

on callyouus

  • shared inbox
  • on-call rota
  • bug triage
  • incident write-ups

02

Maintenance

Frameworks go end-of-life whether or not anyone is watching. We keep versions current, patch CVEs before your auditor finds them, and refactor the parts that make every change expensive — in small, reversible steps.

  • dependency upgrades
  • security patches
  • EOL migrations
  • cost review

03

Automation

Most of what a company calls process is a person retyping data between two tools it already pays for. We find those, and replace them with something that runs at 06:00 and says so when it does not.

  • internal tools
  • workflow automation
  • integrations
  • reporting

Three steps, in order, and then it just runs.

Handover is the part most people get wrong. We do it slowly on purpose — one service at a time, with the previous owner still in the room.

  1. 01week 1

    Audit

    We read everything — repo, infrastructure, tickets, the runbook nobody updated since the last person left. You get a written map of the system, the risks in it, and what we would do first. It is useful even if you stop here.

    output · system map + risk register

  2. 02weeks 2–4

    Handover

    Access, credentials, deploy paths, on-call. We shadow whoever holds it now, take the pager one service at a time, and write down the parts that only ever lived in someone’s head.

    output · runbooks in your repo

  3. 03ongoing

    Steady state

    We hold the queue. Every Friday you get a note: what came in, what shipped, what is scheduled, what is getting worse. One call a month. Nothing else for you to manage.

    output · weekly note, monthly call

Numbers, with the qualifier attached.

An unqualified metric is marketing. These are the four we report to clients every month, including the months they are not flattering.

  • 0.00%99.95%

    uptime across managed services

    rolling 90 days · production only

  • 0m18m

    median first response

    p50, business hours · retainer clients

  • 041

    systems maintained

    across 12 active clients

  • 0yr6yr

    longest engagement

    still running · since 2019

Three of the ones we can write about.

Compressed to the shape they actually had: what was wrong, what we changed, what happened next.

note 01

Slash Post · social scheduling · 18 staff

next.js · node · aws · redis

Both developers left in the same month.

problem

Publisher queue stuck at 340 open tickets, a Next.js app nobody had touched in eight months, and a deploy process that lived in one person’s terminal history. Scheduled posts were failing silently on weekends.

intervention

Took the inbox in week two. Wrote the deploy down, then automated it. Patched the Redis worker that dropped weekend jobs, then upgraded Node and the queue pipeline in merges small enough to revert.

outcome

Queue under 20 by the end of the quarter. Failed scheduled posts down 94%. Deploys went from 40 minutes and a phone call to 6 minutes and a button.

note 02

Compiled · telehealth platform · 120 staff

python · django · gcp · airflow

A nightly export had been failing quietly for eleven weeks.

problem

The job that sent encounter and billing data to their clearinghouse died on a schema change and logged nothing. Clinical ops and finance had been reconciling by hand long enough to assume that was normal.

intervention

Rebuilt the job with retries and a dead-letter queue, added alerting that pages a person rather than filling a channel, and backfilled the missing period under their BAA.

outcome

Eleven weeks of encounter data recovered in four days. Finance stopped reconciling by hand. Nightly export success at 99.8% for the following quarter.

note 03

Relay Pay · fintech ops · 25 staff

node · stripe · xero

Nine hours a week of copy-paste, every week, for two years.

problem

Ops exported invoice lines from Stripe, pasted them into a spreadsheet to fix the mapping, then keyed them into Xero. Month-end close carried whatever they mistyped.

intervention

One small service reads the Stripe API, maps line items, writes to Xero, and puts anything it is unsure about on a single exceptions page. No new vendor, no new subscription.

outcome

Nine hours a week back — about 470 hours a year. Manual errors stopped showing up in close two months later.

Three ways to work with us.

Most people start on a retainer after the audit. If you still have engineers, on-call is usually the cheaper answer — we will say so.

Retainer

You hand over the whole thing.

best for
No engineers left in-house
scope
Support, maintenance and the upgrade roadmap
response
≤ 30 min, business hours
cover
Business hours plus on-call rota
commitment
3 months, then 30 days’ notice
from
$4,800 / mo

On-call

You keep your developers. We cover what they cannot.

best for
A small team that is stretched
scope
Escalation and out-of-hours cover only
response
≤ 15 min on P1
cover
24/7 rota
commitment
Rolling monthly
from
$1,200 / mo

Automation project

One process, fixed and handed back.

best for
A specific manual process
scope
Scoped build, then handover
response
Weekly check-in
cover
Project hours
commitment
Fixed scope, fixed end
from
$8,500 fixed
Book a call

not sure which — the audit answers it

The six we get asked every time.

Send us the thing you are worried about.

Book a call

30 minutes · no deck · we will say if we are not the right fit