do you work with our existing developers or agency?
often. we do the parts they don't cover (usually security, infrastructure, or paid ads) and stay out of their way on the rest. we'll agree who owns what in writing so nothing lands in the gap between us.
a lot of companies already have someone technical: an in-house developer, a freelancer, or the agency that built the site. that doesn't rule us out. it usually means there's a gap around that person, and the gap is what we take.
where we usually fit
- security is the common one. your developers keep building and we find the ways in. we test on a scope you sign in writing, hand your team a report with the steps to reproduce and a named fix for each finding, and retest for free once they've fixed things.
- infrastructure rarely has an owner: hosting, backups, monitoring, DNS, accounts and access. developers rarely want to own it, so we sit alongside whoever handles the helpdesk and take that side.
- with paid ads we run the campaigns and the tracking. when a fix needs code, we either ship it ourselves with access to the repository or send your developer something specific to ship.
how we stay out of each other's way
before anything starts we agree in writing who owns what: which systems, which accounts, who deploys, who gets called when something breaks. no task should land in the space between two teams where each assumes the other has it.
existing code gets a short review and a written assessment before we touch it. we work in your repository under your name, so your team can read every change, and if a task is really theirs we say so.
tell us who's already in place when you get in touch, and we'll propose a split.