MCN procurement: build, buy or outsource

MCN procurement should compare workflow fit and long-term ownership. SaaS, in-house and outsourced development can each fit. Start with required workflows rather than using account count or a general budget threshold to choose the answer.

Use one brief for all three options

Specify client isolation, ownership, approvals, scheduling, outcomes and integrations. Assess SaaS configuration and exports, in-house staffing and maintenance, and outsourced handover. Compare with the same samples instead of assumed development timelines.

Include ongoing and migration costs

List expansion, report exports, storage, platform changes and staff handover beyond subscription or development fees. Check dependencies for credentials and historical IDs. Hosting and export claims require actual terms and demonstrations.

Validate the least replaceable workflow

Test a representative process with approvals, client isolation and failure handling, including revoked access and partial failure. Use a standard tool where it fits; assess extensions, hybrid designs or custom work for material gaps.

Request a reviewable proposal

Require scope, exclusions, access conditions, acceptance samples, source, documentation, deployment, maintenance and exit arrangements. Agree duration and pricing for the actual scope, and retain unresolved items with owners.

Next step: prepare a reviewable brief

Use the development service scope to identify modules. See the related assessment for the connected decision. Prepare target platforms, account ownership, existing software, redacted samples and acceptance needs. Review cost factors and contact Nara to discuss feasible scope.