Process

A Better Build Starts With a Better Diagnosis.

GDS defines the problem, desired outcome, users, data, dependencies, and risk before prescribing technology. That keeps scope clearer, spend easier to justify, and delivery easier to test.

Discovery

Business model, customer journey, acquisition channels, current workflow, friction, impact, users, data, integrations, compliance, budget, and decision constraints.

Solution design

One validated problem statement, target outcome, recommended architecture, intentional exclusions, dependencies, risk level, pricing basis, and next step.

Proposal

Deliverables, exclusions, responsibilities, timeline, one-time and recurring fees, third-party costs, payment schedule, revisions, ownership, and warranty are made explicit.

Build & review

Implementation follows defined acceptance criteria. Normal website/design work includes at least two client revision rounds; defects remain GDS responsibility.

Launch gate

Function, mobile behavior, forms, booking, payments, auth when relevant, security, SEO, accessibility fundamentals, analytics when included, performance, ownership, and approval are checked.

Handoff & care

Client ownership is preferred for domains, billing, production systems, and critical accounts. Custom builds include a 60-day defect warranty, with maintenance scoped separately.

Payment standards

Commercial terms stay clear.

  • Projects of $750 or less: normally 100% upfront
  • Fixed-price projects over $750: normally 50% to begin and 50% before production launch/final handoff
  • Large/custom projects may use milestone billing such as 40/30/30
  • Monthly services are paid in advance for the service period
  • Third-party spend is paid directly to the provider whenever practical
Discovery
Free

Initial discovery is normally free and usually 30–60 minutes. Substantial technical discovery may become a paid scoped engagement when accurate architecture requires deeper investigation.

Bring the problem. Leave with a clearer next step.

The free 30-minute discovery call is designed to clarify the constraint, avoid unnecessary scope, and determine what is worth doing next.