Skip to content
Process

A Clear, Milestone-Based Process

Projects are divided into clearly defined stages. Each stage includes an agreed set of features, deliverables, exclusions, costs, and acceptance criteria.

Payment terms are agreed in advance for each milestone. You always know what is being delivered, what it will cost, and how acceptance will be determined.

Stage 1: Initial Conversation

Understand the business, identify the operational problem, understand current workflows, identify users, discuss constraints, and determine whether technology can help and what kind of solution is appropriate. This conversation is free.

  • Understand the business
  • Identify the operational problem
  • Understand current workflows
  • Identify users
  • Discuss constraints
  • Determine whether technology can help and what kind of solution is appropriate

Stage 2: Discovery and Definition

Larger or unclear projects may require a paid discovery phase to define scope accurately before milestones are planned.

  • Workflow review
  • Requirements clarification
  • User roles
  • Business rules
  • Data sources
  • Integration requirements
  • Security considerations
  • AI suitability
  • Risks
  • Dependencies
  • Deployment needs

Stage 3: Milestone Plan

Each milestone defines features, deliverables, exclusions, acceptance criteria, dependencies, schedule, cost, and payment terms. Future milestones may be revised based on lessons from earlier stages.

  • Features
  • Deliverables
  • Exclusions
  • Acceptance criteria
  • Dependencies
  • Estimated schedule
  • Fixed milestone cost or agreed billing structure
  • Payment terms

Stage 4: Development

Working software is reviewed regularly and kept maintainable. Changes outside the agreed scope are discussed and estimated separately — unlimited changes are not included.

  • Progress updates
  • Regular working-software review
  • Maintainable architecture and implementation
  • Separate scope-change discussion

Stage 5: Review and Acceptance

The client tests the milestone against agreed acceptance criteria. Defects within scope are corrected; new features and scope changes are documented separately.

  • Acceptance testing
  • Defect correction within scope
  • Scope-change documentation
Every task he has been assigned, was completed in time and at the best quality level possible.
Boris VernoffChief Architect, API Governance
Read full recommendation

Stage 6: Deployment

We prepare the approved solution for production, configure the required services, migrate agreed data, verify integrations, and confirm that the system is operating correctly.

  • Production preparation and deployment
  • Agreed data migration and integrations
  • Monitoring and backup setup where applicable
  • Production verification

Stage 7: Handoff and Ownership

You receive what you need to run and maintain the system independently. Secrets are never placed in documentation or source control.

  • Source code and agreed deliverables
  • Account and service inventory
  • Deployment and maintenance documentation
  • Technical handoff information

Stage 8: Optional Support

Support is optional and can be structured however makes sense for your business.

  • Maintenance
  • Support retainers
  • Monitoring
  • Security updates
  • Additional milestones
  • Feature development
  • Technical consulting