Consulting offer

Architecture and Readiness Engagement

Create an agreed architecture and change path that leadership, internal teams and delivery partners can use before major implementation commitments are made.

Duration: Four to eight weeks
Commercial unit: Configured fixed-scope engagement
Commercial model: Fixed fee confirmed after scope

When it is useful

Customer technology has grown into a fragmented or overlapping estate.
A transformation programme needs current-state clarity and target direction.
The organisation is preparing a platform evaluation, consolidation or replacement.
AI and decisioning ambitions are ahead of data, governance or operating readiness.
Teams need a shared capability model, architecture and sequenced roadmap.

What it resolves

The engagement establishes the architecture, readiness gaps, operating implications and sequenced decisions needed before major implementation commitments.

Fit and non-fit

Good fit

There is an executive sponsor and a material decision or transformation mandate.
Relevant business, architecture, data, marketing and delivery stakeholders can participate.
The organisation will expose constraints, prior decisions and active dependencies.
The work can be bounded by agreed capabilities, business units, regions or decisions.

Not a fit

Complete enterprise architecture across unrelated domains.
Detailed solution design, implementation build or programme management.
Formal tender administration.
An engagement where the recommendation must favour a predetermined vendor.
An unbounded transformation role without sponsor access or decision rights.

Inputs, evidence and participants

Named executive sponsor and day-to-day decision owner.
Business strategy, programme mandate and success criteria.
Available current-state architecture, platform, data-flow and operating documentation.
Existing roadmaps, vendor commitments, material constraints and known risks.
Access to the agreed cross-functional stakeholder group.
Timely factual review and decisions at agreed gates.

How it works

01
Frame
Define the decision boundary, modules, stakeholders and evidence plan.
02
Diagnose
Establish current capabilities, constraints, dependencies and decision gaps.
03
Design
Develop target principles, architecture options and operating implications.
04
Test
Challenge feasibility with stakeholders, delivery realities and vendor constraints.
05
Sequence
Define decisions, roadmap, ownership and implementation readiness.
06
Align
Deliver executive playback and working-team handover.

Outputs and handover

Executive findings and decision summary.
Current-state capability and architecture view at the agreed level of detail.
Target principles and architecture blueprint.
Options, assumptions and decision log.
Gap, risk and dependency register.
Operating-model and governance implications.
Prioritised roadmap and implementation-readiness actions.
Executive playback and working-team handover.

Commercial terms and boundaries

The professional fee is fixed after the decision boundary, modules, stakeholder groups, evidence condition, decision complexity and delivery model are agreed.
30% to commence, 40% at the agreed midpoint and 30% on delivery.
Material changes to scope, evidence, stakeholder access, delivery locations or on-site dates require written change control and may affect fees and timing.
The written proposal records any Knowledge Hub access included with the engagement.
Engagements are designed for effective remote delivery. Where in-person participation materially improves alignment or decision quality, on-site delivery can be included in the agreed scope.
Approved travel and accommodation expenses are charged separately at cost. Specialist subcontractors and third-party services are separately scoped.

Client responsibilities

Provide agreed evidence, stakeholder access and decisions at the documented gates.
Review consolidated findings and factual corrections within the agreed windows.

Exclusions

Implementation delivery is not assumed and must be separately scoped.

Typical application

Illustrative, not a client case

A transformation sponsor needs one coherent view of the current estate, target architecture, readiness gaps and practical sequence before selecting or implementing platforms.

Questions buyers ask

Is Enterprise Martech independent of vendors?

Yes. Platform experience informs the advice, but the engagement does not assume a reseller or implementation-partner relationship unless one is explicitly disclosed.

Does Enterprise Martech implement the recommendation?

The standard offers provide advisory, architecture, readiness and assurance. Implementation may be completed by client teams or delivery partners. Any additional Enterprise Martech role must be separately scoped.

Can you work with our system integrator?

Yes. The role may include architecture alignment, vendor challenge and delivery assurance, provided responsibilities and conflicts are explicit.

Can the scope change after commencement?

Material changes to the decision, stakeholder group, evidence boundary, modules or deliverables require written change control.

Do you guarantee a particular outcome?

No. Enterprise Martech provides independent professional judgment based on the agreed evidence and access. Business, programme and technology outcomes remain dependent on client decisions and execution.

Are engagements delivered remotely or on site?

Engagements are designed for effective remote delivery. Where in-person participation materially improves alignment or decision quality, on-site delivery can be included in the agreed scope.

How is the professional fee determined?

The Decision Sprint has a published fixed fee. Architecture and advisory fees are confirmed after the decision boundary, required modules, stakeholder group, evidence condition, decision load and delivery model are understood.

How are travel and accommodation handled?

The professional fee reflects the agreed delivery model, including any reserved on-site capacity. Approved travel and accommodation expenses are charged separately at cost.

What happens if delivery locations or on-site dates change?

Changes to agreed locations or on-site dates may require revised fees and timing. Any material change is agreed in writing before the affected work proceeds.

Why is a fixed proposal required for larger engagements?

A written proposal makes the decision boundary, evidence, participants, outputs, delivery model, responsibilities and commercial assumptions explicit before capacity is committed.

Next step

Set a direction teams can use.

Share the transformation mandate, scope boundary and current evidence so the appropriate architecture modules can be defined.