Design & DesktopEST. 1999
FAMILY OWNED
PROCESS · SIGNATURE TO DELIVERY

How a project moves from a signature to software in production.

01 DISCOVERY
02 PROPOSAL
03 SIGNING
04 KICKOFF
05 DESIGN
06 BUILD
07 QUALITY & UAT
08 GO-LIVE
09 HYPERCARE & SUPPORT
01 / 09 · Discovery
01DiscoveryPre-sale · 1–2 weeks

A partner-led session to understand the business, the systems in place and the outcome that matters. NDA signed before anything sensitive is shared.

DELIVERABLES
Discovery notes · NDA
SIGN-OFF
Client sponsor
02ProposalPre-sale · 1 week

Fixed scope, architecture outline, team, milestones and commercial terms — in one document, priced by milestone.

DELIVERABLES
Proposal · Architecture brief
SIGN-OFF
Client sponsor
03SigningContract · —

Master services agreement and statement of work. Named delivery lead, escalation path and acceptance criteria agreed up front.

DELIVERABLES
MSA · SOW · RACI
SIGN-OFF
Both parties
04KickoffMobilise · 1 week

Access, environments, stakeholders and communication cadence set. Project workspace opened with the client.

DELIVERABLES
Kickoff pack · Project plan
SIGN-OFF
Delivery lead
05DesignDefine · 2–4 weeks

Workflows, data model and interface designed with the people who will use the system. Prototypes validated before build.

DELIVERABLES
Specs · Prototype · Data model
SIGN-OFF
Product owner
06BuildDeliver · 2-week sprints

Engineering in fortnightly sprints with a demo at the end of each. AI components evaluated against agreed benchmarks.

DELIVERABLES
Working increments · Sprint reports
SIGN-OFF
Product owner
07Quality & UATVerify · 2–3 weeks

Automated testing, security review and user acceptance with real data. Nothing ships without written sign-off.

DELIVERABLES
Test reports · UAT sign-off
SIGN-OFF
Client sponsor
08Go-liveRelease · 1 week

Planned cut-over, data migration and training. Rollback plan rehearsed before release day.

DELIVERABLES
Release · Training · Runbook
SIGN-OFF
Both parties
09Hypercare & supportOperate · Ongoing

Thirty days of hypercare, then an SLA-backed support and evolution plan. The relationship continues.

DELIVERABLES
SLA · Monthly reporting
SIGN-OFF
Account partner
Fixed scope, signed
Every engagement starts with an SOW and acceptance criteria both sides sign.
Named ownership
One delivery lead, one account partner, one escalation path — from day one.
Weekly visibility
Status, burn and risks reported every week. Demos every two weeks.
Governed AI
Models evaluated against agreed benchmarks, with audit trails and human oversight.
Process | Design & Desktop