Who operates the system after launch if we have no technical staff?
A company can run a system without a dedicated technical team, but it still needs an internal business owner and a custodian for privileged accounts. Wavesteam or another managed provider can handle monitoring, incidents, backups, patches, and releases under a defined service agreement.
“No technical staff” cannot mean that the client has no responsibilities. A provider can repair software and restore backups; it cannot decide who may see orders, whether a price is correct, or when a departing employee should lose access. Separate business decisions from technical operations before launch, and name a contact and escalation route for each.
When turning a business goal into an executable scope, also compare Will changing project staff or a key resignation disrupt our project?; the linked guidance adds context that should be considered in the same decision.
| Work | Client owns | Provider owns | Agree jointly |
|---|---|---|---|
| Users, permissions, business rules | People and policy approvals | Console and enforcement | Privileged approval flow |
| Content and master data | Correct products, prices, and organization | Import, validation, logs | Bulk change and rollback |
| Monitoring, backup, patches | Business impact and maintenance windows | Execution and reporting | Recovery objectives and downtime |
| Incidents | Symptoms, impact, recovery acceptance | Diagnosis, repair, rollback, review | Priority and workaround |
| Enhancements | Priority and business acceptance | Estimate, implementation, testing | Scope, quote, release |
At minimum, name an empowered product or business owner, a primary-account custodian, and a finance/contract contact. Provider-side contacts should include a service desk, coverage hours, incident owner, and escalation contact. Urgent issues should not depend on one developer's private chat account; the agreed ticket or email channel should retain impact, timing, action, and closure.
Buy a defined operating service, not “call us if anything happens.” State covered environments, cloud services, third-party interfaces, versions, and included capacity. An SLA needs service hours, severity levels, initial response, restoration or workaround targets, measurement, exclusions, maintenance, and remedies. A 30-minute response means acknowledgement unless the contract explicitly says restoration. Availability also needs a window, monitoring point, and treatment of provider, cloud, and client-network failures.
ISO/IEC 20000-1:2018 describes a service-management system spanning planning, transition, delivery, and improvement. A smaller client need not seek certification, but can use these concepts to distinguish managed operations from ad hoc firefighting.
Before launch, rehearse without the original developer in the room. Client staff create and revoke an account, inspect a log, export data, and file a ticket. A second operator uses the documentation to deploy, roll back, and restore a backup. Simulate failure of a core interface and record alert delivery, degradation authority, restore point, recovery time, escalation, and actual data loss.
Wavesteam can provide managed technical operations under contract, but that is not unlimited responsibility. Warranty, baseline operations, enhancements, and third-party failures need separate scope and pricing. The client should retain exports, accounts, and current documentation for future insourcing or replacement. Our service process is descriptive; the actual SLA, rehearsal record, and asset access are the evidence.