Delivery workflow

Qualify and agreeLink

Confirm buyer, problem, desired result, site context, timing and fit. Decide whether diagnosis is necessary. Estimate founder effort, costs and risk; check price and capacity. Agree scope, payment and responsibilities before onboarding.

The proposal should identify client entity, approver, sites, environments, deliverables, exclusions, dependencies, fee, currency, confirmed taxes, payment evidence, review windows and acceptance checks. Include changes, defects, availability, backup and hosting responsibilities, handover, pause or termination, confidentiality, delegation, ownership, licensing, liability allocation and portfolio permissions. This is an agreement checklist, not ready-to-sign legal wording.

Establish a safe baselineLink

Confirm authorized access through an agreed secure method. Record system and vendor dependencies, known faults, backup ownership, recovery options and staging needs. Agree production approval and a rollback route before changes. Pause if essential access or a safe path is missing.

Execute and control changesLink

Keep a visible work and decision record. Use checkpoints proportionate to risk. Review delegated work, run relevant acceptance checks and document unresolved limitations. Communicate progress and dependencies through the agreed cadence.

A defect fails an agreed acceptance criterion. A change adds or alters behavior. Explain change effects on fee, allocation and schedule, then get written approval. Urgent uncertainty can use a small authorized diagnostic cap. Silence is not change approval.

Accept and hand overLink

Obtain acceptance against agreed checks, collect the relevant milestone and transfer agreed source files, access, dependency details, deployment notes and outstanding issues. Record continuing responsibilities and the next review. Offer monthly care only where there is a real recurring need.

Proposed defect-correction period: 30 calendar days from acceptance, limited to attributable defects within Nusigma’s scope. External updates, unrelated inherited faults and new requirements need assessment; this is not an automatic universal warranty.

Close and learnLink

Compare estimate with actual founder time, external cost, rework and communication. Record fee earned, receipts and contribution. Capture a case record and request separate publication permission if useful. Revise future scopes when the same avoidable issue recurs.