Skip to content
Projectkhen

How We Work

Seven stages from first conversation to a system that keeps running. Not every project needs all of them — where you enter depends on what already exists.

  1. 01

    Discovery

    What happens

    • Clarify the problem, the users, and how success will be judged
    • Review available data, regulatory conditions, and budget range

    What you get

    • Requirements summary
    • Explicit list of assumptions we are working from
  2. 02

    Feasibility

    What happens

    • Assess whether the data, models, infrastructure, and devices can carry the idea
    • Identify where the technical risk actually sits

    What you get

    • Technical review
    • Risk list with what would mitigate each
  3. 03

    Architecture

    What happens

    • Design the system, data, AI, and security structure
    • Decide what belongs in the first release and what waits

    What you get

    • Architecture documentation
    • Delivery roadmap
  4. 04

    MVP

    What happens

    • Build the functionality that proves the core value

    What you get

    • A working build you can put in front of real users
  5. 05

    Validation

    What happens

    • Verify function, data, usability, and performance against the stated conditions

    What you get

    • Evaluation results with the conditions they were measured under
    • Prioritised fix list
  6. 06

    Deployment

    What happens

    • Release to the operating environment and set up monitoring

    What you get

    • Deployed build
    • Operations documentation
  7. 07

    Scale

    What happens

    • Extend to more users, countries, features, or devices as demand is confirmed

    What you get

    • Upgraded version
    • Expansion plan

Engagement models

Technical feasibility review

A bounded assessment before anyone commits to building.

Fixed-scope MVP

An agreed feature set delivered as a working build.

Phased build

Delivery in stages, with scope re-decided at each boundary.

Upgrading an existing service

Analysis of what you run today, then targeted extension.

Co-development

Building alongside your team rather than instead of it.

Technical advisory and architecture review

Review and direction without taking over delivery.

We do not publish fixed development fees. Cost depends on data readiness, regulatory conditions, external integrations, AI models, devices, and operating scale. The consultation form asks for a budget range so we can propose something realistic.

Where would your project start?

If you are unsure, describe the situation. We will tell you which stage fits and what it would involve.

Discuss Your Project