a small team that owns the whole technical problem
rebootworks started because companies kept getting handed off. the web agency didn't do security. the security firm didn't do marketing. the marketing agency needed a developer nobody had. we do all three so nothing falls into the gap.
the gap we kept seeing
a company gets a site built. two years later the builder is unreachable, the domain renews to an abandoned inbox, the contact form has been silently failing since a plugin update, and nobody has ever tried to break in. every one of those is somebody's job, and at most companies that somebody doesn't exist.
that's the job we do, and it's ongoing work rather than a project with an end date. someone has to hold the whole picture: what's built, what it runs on, who can get to it, and whether anyone can find it.
how we work
six things we've put in writing, because they're the ones that get dropped when a project runs long.
plain language, always
if you can't repeat our explanation to your accountant, we explained it badly. we write in the words you already use.
one number, held
the price we quote is the price you're invoiced. if the scope changes, you get a new number to approve before we start on it.
you own everything
code, domains, cloud accounts, analytics, all in your name from day one. leaving should be easy, or the work wasn't good enough.
security is not an upsell
we attack every build before launch. it's included, because shipping something breakable isn't finished work.
we'll talk you out of things
the cheaper option, the off-the-shelf tool, the feature you don't need yet. losing scope beats losing your trust.
written down, not remembered
decisions, access, and how it all runs live in documents you keep, so nothing important sits only in our heads.
companies where software matters but nobody owns it
- founders shipping a first product without a technical co-founder
- owner-run businesses whose operations live in spreadsheets
- clinics, trades, and firms with booking, records, and compliance to handle
- teams that inherited a site and can't reach whoever built it
- agencies who need a technical partner behind their own client work
- anyone about to be asked hard security questions by a bigger customer
if you already have a strong in-house engineering team, you probably don't need us. we're still a decent second opinion.
the setup
small on purpose
a senior team you deal with directly. no account manager relaying messages to someone you never meet.
remote, responsive
we work across time zones and reply within one business day. calls when they help, writing when they don't.
english & portuguese
we work comfortably in both, including documentation and anything your customers will read.
build → grow → run
three practices, one contract, and one set of people who answer for all of it.
fixed price by default
hourly billing rewards slowness. we quote the outcome and carry the risk of our own estimates.
no lock-in, ever
month-to-month retainers, full handover on request, and documentation good enough to replace us.
how we know it worked
before a project starts we agree what would count as it working. it's rarely traffic. usually it's hours returned to a person, errors that stopped happening, or a deal that stopped being blocked. the measure goes into the scope, and it's the thing we report against.
- hours per week returned to a named human
- manual steps removed from a process
- time from enquiry to booked or quoted
- findings closed and retested
- qualified enquiries rather than raw sessions