How VSN works

A clear path from first brief to final handover.

We start with discovery, write the scope, review the work at agreed points, then hand over what was built and what comes next.

Team mapping project milestones on a wall during a planning session

PROJECT PATH

ILLUSTRATIVE

Milestones with sign-off points

Discover
Scope
Design
Build & QA
Handover
Scope signed off before build

WRITTEN SCOPE

Proposal or SOW

The process

Six stages from first conversation to managed operations.

Each stage has a clear output, so you know what is being decided before the next one begins.

● PLAN

● DELIVER

● OPERATE

01

STEP 01

Qualify

Understand the business problem, decision makers, budget range and timing.

02

STEP 02

Discover

Map users, requirements, risks, content, integrations and measurable outcomes.

03

STEP 03

Scope

Issue a proposal or SOW covering deliverables, milestones, responsibilities and commercial terms.

04

STEP 04

Design

Validate journeys, architecture and interface direction before expensive implementation.

05

STEP 05

Build & QA

Develop in reviewable increments with security-minded engineering and acceptance checks.

06

STEP 06

Launch & Operate

Deploy, hand over agreed assets and continue with support, growth or managed operations when needed.

Commercial model

Different work needs different billing.

Fixed-scope products can use simple packages. Complex engineering, BPO and advisory work should use a proposal or SOW rather than forcing every client through the same checkout.

MODEL 01

Productized services

Authority profiles and tightly scoped website packages can use published starting prices and clear inclusions.

TYPICAL BILLING

Published starting prices

MODEL 02

Custom projects

Apps, SaaS, e-commerce and automation are normally milestone-based after discovery and written scope.

TYPICAL BILLING

Milestones after written scope

MODEL 03

Recurring services

Social media, maintenance, BPO and managed support are normally monthly or quarterly retainers tied to capacity and service levels.

TYPICAL BILLING

Monthly or quarterly retainer

Project control

No surprise scope.

A strong engagement separates agreed deliverables from new requests. Significant changes should be documented before they affect cost or delivery.

WHEN A NEW REQUEST ARRIVES

Request
Documented
Impact agreed
Scope updated

Every SOW should define

Deliverables and exclusions

Milestones and acceptance criteria

Client dependencies

Revision limits

Security and access responsibilities

Payment schedule

IP ownership and handover

Support / warranty period

Ready to scope the work?

Share the business outcome you need. VSN can route the request to the right service line and commercial model.

Review points

Decisions stay visible as work moves forward.

Projects lose time when feedback arrives after the underlying decision has been built into every screen or workflow. We agree which outputs need your sign-off and who has authority to approve them.

SIGN-OFF SEQUENCE

Typical checkpoints

01

Scope

Confirm the outcome, exclusions and dependencies.

02

Direction

Review journeys, content and technical approach.

03

Working build

Test the agreed core flows and record changes.

04

Handover

Review access, documentation and unresolved items.

Frequency and acceptance criteria vary by engagement and are written into the proposal or SOW.