Five engineering practices
Most engagements use two of these. A replatform usually starts as an advisory review; an assistant is worth little until the content behind it is integrated; an application nobody operates becomes the next thing that needs replacing.
Index
Which one fits the problem
- Software engineering
5 phases · 1 to 2 weeks to start
Web applications and internal tools, taken from a spreadsheet or a dead codebase to something a team can change safely. - Automation and integration
4 phases · 1 week to start
System-to-system integration and process automation, with the exception paths designed rather than discovered in production. - Applied AI
4 phases · 1 to 2 weeks to start
Assistants grounded in your own content, with retrieval, guardrails and an evaluation set that produces a number before launch. - Platform and cloud operations
4 phases · 2 weeks to start
Identity, endpoints, Microsoft 365 and networks, run as a documented service with access you can actually audit. - Technical advisory
4 phases · 3 days to start
Architecture reviews and assessments that end in a recommendation with costs, risks and a dissenting view recorded.
Where an engagement spans more than one practice, it stays under one team and one prioritised list rather than being split between groups who have to meet to agree.