Platform, Security & Operations
QA, support and ongoing operations
What this category covers
Two related businesses sit under one heading. On one side is everything that happens before a release — manual QA and test plans, automated suites that run on every deploy, and load testing that establishes how much traffic a system genuinely holds. On the other is the staffed work that happens continuously afterwards — a tier-one helpdesk, managed IT for companies without an IT department, content moderation for platforms carrying user submissions, and back-office and virtual assistance for owners absorbing administration at their own hourly cost.
They are bought by different people for different reasons and they share one characteristic that matters commercially. This work does not finish. A product that ships weekly needs checking weekly, a queue does not stop because a quarter ended, and devices and accounts need managing every month of their life. That makes these engagements ongoing rather than one-off, and it makes measurement the centre of the relationship rather than an extra at the end.
Buyers usually arrive with one of two problems. Either a release is coming and nobody independent has verified it, which is a question of risk before a fixed date. Or something is already running and nobody is answering it properly — tickets, devices, moderation queues, admin — which is a question of capacity that has been absorbed by people whose time is worth more elsewhere. Both are solvable, and in both cases the value is in what gets written down and reported back, not just in the hours worked.
- Services
- 7
- Detailed pages
- 7
18
QA, Support & Ongoing Operations
7 services
-
01
Manual QA & test plans
Structured testing, bug reports and release sign-off.
-
02
Test automation
Playwright or Cypress suites that run on every release.
-
03
Performance & load testing
How much traffic the system holds — with the proof.
-
04
Helpdesk / tier-one support outsourcing
Chat, email and phone support, staffed by the studio.
-
05
Managed IT services
Devices, accounts, software and helpdesk, monthly.
-
06
Content moderation
User-generated content reviewed and policy enforced, at scale.
-
07
Virtual assistant & back-office ops
Admin, data entry, scheduling and CRM hygiene.
How the work runs.
-
01
Scope
What you actually need from QA, Support & Ongoing Operations, written as deliverables rather than adjectives.
A day or two
-
02
Price and date
A fixed scope, a number and a delivery date, agreed before anyone starts.
Same week
-
03
Build
The work itself, with something you can open and look at rather than a status report.
The bulk of it
-
04
Handover
Files, access and a walkthrough. Nothing is held hostage.
Final day
See where the site stands before you brief anyone.
Before scoping QA, Support & Ongoing Operations work, it helps to know what the site is doing today. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.
Questions people ask before they commit.
- Where should we start if we have never had formal QA?
- Manual QA on the next release, almost always. It costs least, it tells you where your product is actually weak, and it produces the regression pack — the fixed set of routes checked before every release. That pack is what makes automation worth buying later, because you will be automating routes you know matter rather than guessing. Buying automation first usually means paying to discover the same information more slowly.
- What do you refuse to promise in this category?
- Three things, because all three are traps. Zero bugs, which no product has ever achieved and which turns every future defect into an argument. Full test coverage, which measures lines of code rather than business routes and can be perfect while a pricing rule silently overcharges people. And round-the-clock support on a small team, because a week contains 168 hours and one person covers about 40 — genuine cover is a five-person rota once leave, sickness and training are counted, not something three people absorb. We will quote extended hours, named routes and measured defect escape instead.
- How are these services priced?
- In four different shapes because they are four different kinds of work. Testing time is hourly. Automation and performance work is a project with a defined outcome. Staffed services — helpdesk and moderation — are per agent per month. Managed IT and back-office support are a monthly retainer rather than a headcount. What sets the number is covered on each service page, and coverage hours are the biggest single factor on anything staffed.
- Do you fix the problems you find?
- Not in the same engagement, and that separation is deliberate. Testing finds and documents, developers fix, then we verify and add a permanent regression case. Performance work names the bottleneck rather than rewriting the query behind it. Anyone who both makes the change and signs it off has removed the only independent check you were paying for.
- Which parts of the agreement cause the most disputes?
- The same four every time — which environment is being tested and what happens when it is broken, the exact browser and device list rather than the word all, how many test cycles a release includes, and what actually counts as a release. Each of those is one line, and each of them prevents a month of friction. We put them in writing before starting rather than discovering the disagreement at invoice time.
- Can support and QA be bought together?
- They work better together than apart, and the reason is one-directional. Support sees what customers actually hit in the real world, which is often not what testing predicted, and those findings become test cases. Testing prevents the releases that generate support volume in the first place. The monthly report that names the five causes generating the most tickets is where the two meet, and it is usually the most useful page either service produces.