Skip to content
David Technologies

Delivery process

Predictable delivery, honest communication, clear ownership.

Every engagement — defined project, ongoing support, or managed team — runs on the same six-stage process. What changes is which stages carry the weight and how long each one lasts.

CLIENT PARTICIPATIONFEEDBACK LOOPDiscover01FIT & SCOPEArchitect02DESIGN REVIEWBuild03QA · CLIENT REVIEWLaunch04HANDOVEROptimize05METRICS REVIEWSupport06CONTINUOUSSYS/PROCESS · 001
01

Discover

Understand the users, the goal, and the real constraints — including the ones you already work around.

Activities

  • Structured discovery calls with the people doing the work
  • Review of existing systems, tools, and documentation
  • Stakeholder mapping and success-criteria capture
  • Written summary of what we heard and how we understood it

Deliverables

  • Written discovery brief
  • Success criteria
  • Initial constraints list
Client involvement
One or two working sessions plus a review of the written discovery brief.
Decisions made
Whether the engagement is worth doing, and whether we are the right partner for it.
Communication
Working sessions live; async written notes shared within 24 hours.
Quality controls
Nothing progresses to Architect until the discovery brief is reviewed and approved.
Gate to next stage
Signed-off discovery brief.
02

Architect

Design a practical, maintainable path to the outcome — written down before code, content, or accounts are touched.

Activities

  • Chosen approach and technical/operational shape
  • Scope, deliverables, and success measures
  • Milestones, timeline, and cost
  • Risks, assumptions, and open questions

Deliverables

  • Architecture / scope document
  • Milestone plan
  • Cost estimate
Client involvement
One review call plus a written approval of the architecture document.
Decisions made
Approach, scope boundary, milestones, and commercial terms.
Communication
One structured review; async questions before the call.
Quality controls
Explicit trade-offs — what is in scope, what is out, and why.
Gate to next stage
Signed-off architecture document and commercial terms.
03

Build

Implement in measured increments so you can see progress every week.

Activities

  • Weekly demos of the live working system
  • Written status: shipped this week, planned next week, risks
  • Change notes for any scope adjustments
  • Reviewed code, content, or configuration

Deliverables

  • Working increments each week
  • Change notes for any scope adjustments
Client involvement
Weekly demo, weekly async review, ad-hoc questions.
Decisions made
Approving each week's work, resolving open questions, approving any change notes.
Communication
Written weekly status; live weekly demo; async chat during the week.
Quality controls
Reviews, tests where they matter, and staged deployment before anything customer-facing.
Gate to next stage
Feature-complete and pre-launch reviewed increment.
04

Launch

Ship carefully, with review, documentation, and clear handover.

Activities

  • Pre-launch review across scope, quality, and access
  • Staged rollout with monitoring
  • Handover documentation, credentials, and admin runbooks
  • Post-launch check-in within the first week

Deliverables

  • Live system
  • Handover pack (documentation, credentials, runbooks)
Client involvement
Sign-off on pre-launch review; walkthrough of handover materials.
Decisions made
Go / no-go on release; who owns post-launch response.
Communication
Live launch walkthrough; written post-launch summary.
Quality controls
No release without a pre-launch review and rollback plan where relevant.
Gate to next stage
Launched and handed over.
05

Optimize

Measure what matters and iterate on what actually moves the outcome.

Activities

  • Baseline measurement against agreed success criteria
  • Prioritized improvement list based on real data
  • Iterative changes with each impact measured
  • Monthly report with commentary, not just numbers

Deliverables

  • Monthly performance report
  • Prioritized improvement backlog
Client involvement
Monthly review; approval of the priority list each cycle.
Decisions made
What to optimize next; when a change earned its keep.
Communication
Monthly report; weekly async update on active improvements.
Quality controls
Every change is tied back to a measurable outcome — or it doesn't ship.
Gate to next stage
Quarterly review of whether to continue, expand, or wind down.
06

Support

Continue ownership when you want an ongoing partner — maintenance, iteration, and continuous improvement.

Activities

  • Monitoring, patches, and dependency upgrades
  • Ongoing iteration on features, content, or operations
  • SOP maintenance and knowledge continuity
  • Regular strategic reviews of what to invest in next

Deliverables

  • Ongoing maintenance and iteration
  • Updated SOP library
  • Monthly report
Client involvement
Monthly review; ad-hoc requests through a single point of contact.
Decisions made
What to prioritize each month; when to scale scope up or down.
Communication
Named point of contact; monthly report; weekly async update.
Quality controls
SLAs where they are earned; documented escalation path always.
Gate to next stage
Quarterly scope review; renewal or amicable wind-down at any time.

How the process adapts

The six stages are constant. Which ones carry the weight depends on the shape of the engagement.

Defined projects

Discover → Architect → Build → Launch, with an optional Optimize / Support extension. Ends at handover unless you renew.

Ongoing support

Compressed Discover, no formal Architect gate. The engagement lives in Optimize + Support, with weekly execution and monthly reviews.

Managed remote teams

Discover → light Architect → ongoing Optimize + Support with SOP-driven Build increments. Quarterly scope review sets direction.

Ready to run this on your project?

Answer a few structured questions and we’ll recommend which stages your engagement needs to spend the most time in.

Explore solutionsStart an assessment