Get in Touch
Overview
AmpliFabrik runs the Amplience discovery phase that turns a rough commerce brief into a buildable, signed-off implementation plan for commerce brands in the US and Canada. Discovery is where stakeholders align on what is Amplience for their specific commerce program - the platform's role in the composable commerce platform stack, its relationship to the commerce engine, and the editorial workflow it will support. The discovery phase is the foundation of every successful Amplience headless CMS implementation - the work that resolves stakeholder ambiguity, scopes the program honestly, and produces the requirements documentation that engineering builds against.
AmpliFabrik discoveries are run jointly by an Amplience-certified solutions architect and a business analyst, both with senior production experience across multiple Amplience implementations and composable commerce architecture programs. Outputs include stakeholder findings, current-state platform audit, a recommended Amplience content model approach, prioritized requirements, integration strategy with the commerce engine (Commercetools, SFCC, BigCommerce), risk register, and a documented implementation plan with milestones and effort estimates. Discovery is engaged as a fixed-price, time-boxed phase that can stand alone or roll directly into the next delivery phase.
Why an Amplience Discovery Phase Determines the Success of the Whole Implementation
Skipping discovery is the most common reason composable commerce projects fail
Content modelling decisions made in discovery shape the platform for years
Discovery surfaces integration risk before it becomes program risk
Discovery produces the documentation engineering and stakeholders both need
What an AmpliFabrik Amplience Discovery Engagement Covers
Stakeholder Interviews and Workshop Facilitation
Current-State Platform and Content Audit
Amplience Content Model Recommendation
Composable Commerce Integration Strategy
Requirements Documentation and Prioritization
Implementation Plan with Effort and Milestones
What AmpliFabrik Delivers
Documented Requirements Catalog
Amplience Content Model Recommendation
Composable Commerce Integration Architecture
Implementation Plan with Effort, Milestones, and Risks
Frequently Asked Questions
A standard Amplience discovery runs four to eight weeks depending on scope. A focused single-brand single-market discovery is typically four weeks. A multi-brand or multi-market discovery, or a discovery with significant migration scope from a legacy CMS, runs six to eight weeks. AmpliFabrik publishes a discovery timeline as part of the engagement scoping conversation.
Discoveries are priced fixed for a defined scope. Pricing depends on engagement scope - team composition, duration, depth of audit work, and number of stakeholder interviews. AmpliFabrik publishes a fixed-price discovery quote after a 30 to 60 minute scoping call. There are no open-ended hourly engagements for discovery work.
Discovery requires committed time from commerce leadership, merchandising and editorial leads, IT and engineering owners, and any internal Amplience champion if one exists. AmpliFabrik handles facilitation - your team's role is honest input. A typical discovery requires 8 to 16 hours of stakeholder time per workshop participant across the engagement.
Yes. Discovery is engaged as a standalone, fixed-price phase. Many AmpliFabrik clients run discovery to inform a vendor selection process, then choose AmpliFabrik or another vendor for implementation based on the discovery output. The discovery deliverables are vendor-agnostic and stay with you regardless of who builds the platform.
Discovery exists to surface problems early, when they are cheap to address. If the discovery output indicates that scope, timeline, or budget should change, AmpliFabrik documents the recommendation with rationale and presents it to your leadership. The discovery deliverable is the truth as AmpliFabrik finds it - not a justification for a predetermined implementation plan.
Discovery is structured around an Amplience implementation. If you are evaluating Amplience against Contentful, Contentstack, Storyblok, AEM headless cms or other alternatives, AmpliFabrik runs that as a separate Amplience consulting engagement before discovery. Once Amplience is selected, discovery defines how to implement it well.
Discovery output is documented in a format the implementation team builds against. Most AmpliFabrik clients move directly from discovery into the content modelling phase or, for smaller scopes, into implementation. The same solutions architect typically continues into downstream phases, providing continuity. There is no second discovery in the next phase - the artifacts produced in discovery are the artifacts engineering executes against.
