Straight answers, before you ask.

With a conversation, not a proposal. You tell us what is wrong or what you need, an engineer asks the questions that decide the shape of the job, and you get a written scope with one price. Nothing is billed until you have agreed to that scope.

The lead who scoped it, with the engineers the job needs. Ibi leads software and infrastructure work, Ilgar leads networking, and the person you meet at the survey is the person responsible from then on — there is no handover to a delivery team you have never spoken to.

Yes. A one-day network survey, a single afternoon fixing a deployment, a review of a codebase before you buy the company that wrote it. Small jobs are how most of our longer relationships began.

Happily. We take the slice they cannot get to, work in their repositories, their accounts and their review process, and write down what we did so it stays useful after we leave.

A fixed price for a scoped piece of work, quoted after the survey or scoping call. Longer projects are quoted release by release so you can stop at any point and still own something that works. Support is a monthly retainer sized to what is being covered.

A range, usually, from a short description. A firm number needs a survey, because the survey is what finds the things a description leaves out — the cabling nobody mapped, the server nobody documented. The survey is priced on its own, and its cost comes off the job if you go ahead.

You do. Repositories, cloud accounts, domains, licences and hardware are in your name from the start. We hold access while we work and hand it back when we finish; nothing you paid for lives on a platform of ours.

No. The scoping call, and the range that comes out of it, are free. You are charged from the point you agree to a written scope.

Every job comes with a support period, and the engineers who did the work are the ones who answer during it. After that you can take a retainer, call us as and when, or take the documentation and run it yourselves — all three are fine, and we will say which we think fits.

The office keeps London business hours, Monday to Friday, and enquiries are answered within them. A support retainer states its own cover and response time in writing; out-of-hours cover is part of a retainer, not something we improvise.

Where it is under a support retainer, yes — uptime, errors and cost, with an engineer paged when a threshold is crossed. Where it is not, we set the monitoring up so that you can see it, and leave you the runbook.

Usually. It starts with a review — what it does, what is fragile, what it costs to run — and a written plan before we touch anything. If it should not be supported in its current state, the review says so and says what would change that.

On-site work — network installation, surveys, cabling, office moves — is London and the surrounding counties. Software, cloud and security work is remote across the United Kingdom, with visits for kickoffs, workshops and anything easier around one table.

TradeOps is our own product: the quoting, scheduling and invoicing platform that this site and our customers’ sites run on. The services are the engineering work we do for clients. The one proves the other — we run on what we build — and a services client is never required to use it.

Yes. Security cleared engineers review your cloud accounts, networks and applications and hand you a report in plain English, with the fixes ranked by what to do first. Scope, deliverables and the questions people ask about audits are on the security audit page.

On that service’s own page, with the answers that depend on the discipline: software development, infrastructure and cloud, networking, and security audits. This page keeps to the questions that are the same whichever you need.