This is the most familiar form of engagement for organisations that have previously worked with technical architects. For a specific problem or initiative, I conduct analysis and provide clear architectural recommendations, solutions, and implementation guidance.
This model works best when the business has a well-defined problem or scoped initiative that requires architectural input.
It can also be a good option for organisations that want to trial my consultancy services before committing to a broader strategic engagement.
Types of Projects
I can support a wide range of architectural initiatives. My experience spans full-stack technical architecture, from product and platform design down to infrastructure (AWS, Azure, and on-premise environments).
Examples of projects where I can provide architectural support include:
Project Architecture Engagements
Improving performance, cost efficiency, resilience, scalability, or security for a specific product or area of a system.
Migration Projects
Supporting migrations to new technologies, platforms, or tooling. This may include application migrations, infrastructure changes, or data migrations. The scale of the migration will determine whether a short-term engagement is appropriate or if a longer strategic engagement is required.
Compliance Architecture (PCI, GDPR, etc.)
Designing or reviewing systems to ensure they meet regulatory and contractual compliance requirements.
Data Architecture & Design
Designing data systems that support regulatory compliance, contractual obligations, and long-term data governance through robust architectural patterns.
API and Event Architecture
Defining clear service contracts and architectural patterns for APIs and event-driven systems to ensure scalability, maintainability, and reliability of data in transit.
Engagement Format
Before starting any engagement, we will hold an initial scoping conversation to understand the problem space and define the most appropriate engagement structure.
During this discussion I will typically ask about:
- The specific problem or challenge the business wants advice on
- The number of deployed services or systems involved
- The approximate size and structure of the teams supporting the platform
- The outcomes the business hopes to achieve (e.g., cost reduction, migration plan, improved system resilience)
Based on this information, I will propose an engagement structure along with estimated timelines.
Each engagement is tailored to the organisation and problem, but a typical delivery structure may include:
Phase 1: Discovery & Assessment
A focused discovery phase to establish a deep understanding of the business context, current architecture, and organisational design.
Phase 2: Strategy & Target Architecture
Synthesis of discovery findings into a coherent technical strategy and target-state architecture.
Phase 3: Roadmap & Proposal
Translation of the agreed strategy into a pragmatic, prioritised roadmap.
Phase 4: Handover
A structured handover at the conclusion of the engagement to ensure stakeholders and delivery teams can confidently execute the recommended changes.
Example Expected Outcomes
At the start of the engagement we will agree on specific deliverables and outcomes for each phase.
Examples of deliverables may include:
- Assessment of the problem area and architectural gap analysis
- Solution options with cost/value analysis and trade-offs
- Documented current-state architecture
- Documented target-state architecture
- A practical implementation plan approved by the business
- Structured documentation and knowledge transfer to enable teams to implement the changes
Rates
Engagements can be structured on either an inside or outside IR35 basis, depending on the nature of the work and client requirements.
Day rates and commercial arrangements can be discussed following the initial scoping conversation.
