Specialists and responsibility

When to use a specialistLink

Use a specialist for a defined capability gap, bounded workstream or economically sound execution need. Confirm availability, scope, deliverables, fees, review points, access and fallback before committing to the client. Do not recruit merely to protect an unrealistic promise.

Commercial and quality gateLink

The specialist brief must map to the client scope. Vimal must be able to review the work competently or arrange qualified review. Include architecture, communication, integration, checks and risk in founder hours. Price the result using the internal floor after external costs; invoice markup alone is insufficient.

Collections must fund firm external commitments without depending on an uncertain final receipt. Confirm client disclosure or named approval requirements, confidentiality and permitted access. Retain usable source files, review records and technical knowledge with Nusigma.

Responsibility recordLink

For each engagement, name who owns each item: application changes; hosting; domain and DNS; mail; monitoring; backups; restore verification; licenses; content; business decisions; incident triage; approvals; and vendor escalation. Record the scope boundary and contact route beside each name.

This record is a proposed wiki operating template. Assign responsibility through the actual agreement; the list does not automatically make Nusigma responsible for every service.

Client-selected vendorsLink

Scope coordination separately and define responsibility for externally selected work. Do not accept full accountability without sufficient control over selection, access, review and quality. Record ownership and licensing arrangements before implementation.

Protect founder capacityLink

Specialists add execution capacity but retain demands on Vimal’s architecture, review and communication time. If oversight consumes company time or disrupts clients, reduce scope or concurrency. Reconsider a permanent team only through an explicit strategy decision.

Use least necessary access and an agreed secure credential channel. Record access granted and removal at completion. The wiki should reference secure credential locations, not contain passwords or tokens.