Architectural Project Support provides deep, hands-on technical architecture for a specific initiative, platform challenge, or migration.

Led by Jessica Brentnall, this service is designed for organisations that already have a defined problem or scoped piece of work and need focused architectural expertise to design the solution and guide implementation, without committing to a broad platform overhaul.

When Project Support Makes Sense

This engagement works best when your team knows what needs to be achieved, but needs senior architectural direction to figure out how to build it reliably. It is also an ideal, low-risk way to try working with JBrentnall Digital on a discrete piece of work before exploring broader strategic advisory.

Targeted Project Architecture

Designing or improving specific components within your technical estate, focusing on performance, cost efficiency, resilience, or scalability for a defined product area or service.

Technical & Platform Migrations

Architectural guidance for moving applications, infrastructure, or data to new platforms, cloud environments (AWS, Azure), or modern tooling, ensuring the transition happens safely without disrupting ongoing delivery.

Compliance by Design (PCI, GDPR, & Security)

Designing or reviewing system architectures specifically to satisfy regulatory, security, or contractual requirements using patterns that engineering teams can actually maintain.

Data Architecture & Design

Designing data systems that support compliance, contractual obligations, and longer-term governance, using patterns the organisation can actually operate.

API and Event Architecture

Clear service contracts and patterns for APIs and event-driven systems, so data in transit stays scalable, maintainable, and reliable.

Engagement Format

Work begins with a straightforward scoping conversation focused strictly on the specific problem or initiative at hand.

That discussion typically covers:

  • The exact challenge, migration, or feature set requiring architectural input.
  • The systems, databases, or third-party services involved.
  • The approximate size and structure of the teams supporting the platform
  • The desired commercial or technical outcome (e.g., lower cloud expenditure, PCI compliance, seamless migration).

While every project is sized to your timeline and scope, engagements are typically structured around four practical stages:

Phase 1: Scoping & Problem Framing

Clarifying requirements, technical constraints, and current-state architecture for the target system.

Phase 2: Solution Design & Trade-off Analysis

Developing target-state architecture options, comparing cost/value trade-offs, and agreeing on the technical direction.

Phase 3: Roadmap & Proposal

Creating clear, actionable technical specifications, API contracts, or migration plans for internal engineering teams.

Phase 4: Implementation Guidance & Handover

A structured handover so stakeholders and delivery teams can execute the recommended changes with confidence.

Example Expected Outcomes

Specific deliverables are tailored to the project brief, but typical outputs include:

  • Current-state and target-state architectural documentation.
  • Solution options analysis with explicit cost, risk, and effort trade-offs.
  • API specifications, service contract designs, or data architecture blueprints.
  • Practical migration or implementation plans your engineering teams can execute directly.
  • Structured knowledge transfer and handover sessions for internal stakeholders.

Commercials & IR35

Engagements can be structured on either an inside or outside IR35 basis depending on the brief, scope of work, and operational context.

Day rates and commercial arrangements are tailored to the project requirements and agreed transparently following the initial scoping conversation.

Who provides this service

This service is provided by Jessica Brentnall.