Process
A sequence you can follow.
Every engagement uses the same ten stages. The length of each stage changes with the project. The order does not, because skipping a stage is how estimates go wrong.
01 Discover
We interview the people who will use the system and the people who own the outcome. The output is a written problem statement, the constraints, and the decision this version must support.
02 Research
We inspect the data, the current tools and the adjacent products. Gaps are called out before a timeline is promised, especially where source data is incomplete or access is still pending.
03 Strategy
Scope is cut to the smallest release that proves the outcome. Success is defined as something that can be checked after launch, not a list of features.
04 Architecture
We choose the model, the application boundary and the integration points. The architecture note names what is built, what is bought, and what is deliberately left out of the first release.
05 UX and interface
Flows are prototyped against the real task. Copy, empty states and failure states are part of the design, because an AI product is judged on what it does when it is unsure.
06 Development
Work lands in the repository in reviewable increments. You see the running software each week, not a status slide. Feedback changes the next increment, not a backlog that waits until the end.
07 Quality assurance
We test the paths users actually take, including bad input, slow dependencies and the cases the model should refuse. Fixes are merged before the release candidate is called done.
08 Security review
Access, secrets, logging and dependency risk are reviewed against the environment the system will run in. Findings are fixed or explicitly accepted in writing before launch.
09 Launch
Deployment, monitoring and a rollback path are in place before traffic is switched. The first days after launch are staffed so a production issue has an owner.
10 Support
After release we watch the metrics that were agreed up front and schedule the next change from evidence, not from a feature wish list.
If you already know the problem, start at contact. If you want to see the kinds of systems this process is used for, read the work.