Skip to content
BBuild Stage

How do we make it repeatable?

The Build stage is about creating repeatability through codification and standardization. Turn expertise into artifacts. Decide what gets standardized (70%) and what stays configurable (30%). The art of productization is finding the line between over-standardizing (agencies cannot use it) and over-customizing (you are running a development shop with product theater).

Stage Objectives

  • Identify and prioritize tacit expertise that must be codified
  • Create decision trees, templates, and training materials
  • Apply the 70/30 principle to every product feature
  • Define what is standardized core vs. configurable surface
  • Establish configuration vs. customization boundaries

Key Activities

Expertise Codification

Identify the tacit knowledge and delivery expertise that must be codified to make your product repeatable. Use interviews and observation to capture expert judgment.

Standardization Decisions

Apply the 70/30 principle: 70% standardized core (security, compliance, core functionality, infrastructure) and 30% configurable surface (workflows, reporting, integrations, UI).

Configuration Design

Design configuration capabilities that let customers adjust without code changes: workflow parameters, reporting options, UI preferences, business rules.

Custom Scope Boundaries

Define what falls outside the product and requires professional services. Custom work gets separate scope, timeline, and CLIN structure.

Stage Outputs

Codified expertise artifacts (decision trees, templates, procedures)
Standardization decision matrix with zone assignments
Feature list with 70/30 ratio analysis
Configuration vs. customization boundary documentation