kitfly 0.1.2 → 0.2.1

package/dist/_raw/content/templates/pipeline.md

@@ -0,0 +1,151 @@
+---
+title: Pipeline Template
+description: Data pipeline operations with stages, sources, destinations, and manifests
+---
+
+# Pipeline Template
+
+The `pipeline` template creates a structured site for data pipeline operations. It extends `minimal` with sections designed for teams that build, run, and maintain data pipelines — index builds, content extraction, transfer/reflow, and validation.
+
+## When to Use
+
+- Data pipeline operational documentation
+- ETL/ELT process runbooks
+- Data migration projects
+- Batch processing operations
+- Any workflow with sequential stages moving data from sources to destinations
+
+## What You Get
+
+Everything from `minimal`, plus:
+
+```
+my-pipeline/
+├── site.yaml              # Configured with pipeline sections
+├── index.md               # Pipeline status dashboard with quick links
+├── CUSTOMIZING.md         # How to customize (AI + human friendly)
+├── content/
+│   ├── pipeline/
+│   │   ├── overview.md          # End-to-end dataflow
+│   │   ├── index-build.md       # Index build stage
+│   │   ├── extract.md           # Content extraction stage
+│   │   ├── transfer.md          # Transfer / reflow stage
+│   │   └── validate.md          # Validation stage
+│   ├── sources/
+│   │   └── index.md             # Source system catalog
+│   ├── destinations/
+│   │   └── index.md             # Destination catalog
+│   ├── operations/
+│   │   ├── run-pipeline.md      # Full execution procedure
+│   │   └── schedules.md         # Pipeline schedule table
+│   ├── troubleshooting/
+│   │   └── common-issues.md     # Pipeline-specific issues
+│   └── reference/
+│       ├── manifests/
+│       │   └── index.md         # Job manifest YAML templates
+│       ├── field-mappings/
+│       │   └── index.md         # Source → destination mappings
+│       ├── metrics/
+│       │   └── index.md         # Pipeline KPIs and SLAs
+│       ├── checklists/
+│       │   └── pre-run.md       # Pre-run verification
+│       └── contacts/
+│           └── directory.md     # Team contacts and escalation
+└── ...
+```
+
+## Sections
+
+| Section             | Purpose                     | Typical Content                                                   |
+| ------------------- | --------------------------- | ----------------------------------------------------------------- |
+| **Pipeline**        | Core dataflow documentation | Stage definitions, data movement, processing logic                |
+| **Sources**         | Input systems               | Connection details, schemas, auth profiles, data formats          |
+| **Destinations**    | Output systems              | Target structures, path layouts, landing zones                    |
+| **Operations**      | Run procedures              | Execution steps, schedules, checkpoint/resume                     |
+| **Troubleshooting** | Problem resolution          | Auth expiry, index locks, duplicate conflicts, collision handling |
+| **Reference**       | Supporting materials        | Manifests, field mappings, metrics, checklists, contacts          |
+
+### Pipeline vs. Runbook
+
+Both are operational templates, but they serve different shapes of work:
+
+| Aspect              | Runbook                          | Pipeline                                 |
+| ------------------- | -------------------------------- | ---------------------------------------- |
+| **Focus**           | Service operations               | Data movement                            |
+| **Structure**       | Procedures + incidents           | Sequential stages + sources/destinations |
+| **Key question**    | "What do I do when X breaks?"    | "How does data flow from A to B?"        |
+| **Reference model** | Interfaces, contacts, checklists | Manifests, field mappings, metrics       |
+
+## Usage
+
+```bash
+kitfly init data-ops --template pipeline
+kitfly init data-ops --template pipeline --brand "Data Platform"
+
+# With AI assistance instrumentation
+kitfly init data-ops --template pipeline --standalone --ai-assist
+```
+
+## The Pipeline Section
+
+The core of this template. Each stage is documented with:
+
+- **Objective** — what the stage accomplishes
+- **Prerequisites** — what must be in place before running
+- **Procedure** — step-by-step execution
+- **Verification** — how to confirm success
+
+The default stages follow a common data pipeline pattern:
+
+```
+Source → Index Build → Content Extraction → Transfer/Reflow → Validation → Destination
+```
+
+Adapt these to your actual pipeline. Add, remove, or rename stages as needed.
+
+## Growing Your Pipeline Docs
+
+As your pipeline matures, consider expanding:
+
+**Multiple pipelines** — add subdirectories under `content/pipeline/`:
+
+```
+content/pipeline/
+├── overview.md
+├── daily-sync/
+│   ├── index.md
+│   ├── extract.md
+│   └── validate.md
+└── quarterly-migration/
+    ├── index.md
+    └── stages.md
+```
+
+The sidebar automatically organizes these into collapsible groups — each subdirectory becomes an expandable section in the navigation.
+
+**Multiple sources/destinations** — add a page per system:
+
+```
+content/sources/
+├── index.md           # Catalog table
+├── salesforce.md      # Source details
+└── data-warehouse.md  # Source details
+```
+
+## Example Use Cases
+
+**Cloud Data Migration**
+
+- Pipeline: S3 scan → content probe → key rewrite → validation
+- Sources: AWS S3 buckets with legacy key structure
+- Destinations: GCS with date-partitioned layout
+- Operations: Weekly full sync, daily incremental
+- Reference/Manifests: Job definitions per source bucket
+
+**ETL for Analytics**
+
+- Pipeline: Extract from APIs → transform/enrich → load to warehouse
+- Sources: REST APIs, SFTP drops, webhook events
+- Destinations: Snowflake tables, Parquet files in S3
+- Troubleshooting: Rate limits, schema drift, partial loads
+- Reference/Metrics: Row counts, freshness SLAs, error rates

package/dist/_raw/content/templates/productbook.md

@@ -0,0 +1,187 @@
+---
+title: Productbook Template
+description: Product and domain documentation for complex greenfield engagements
+---
+
+# Productbook Template
+
+The `productbook` template creates a documentation site that captures both **product definition** and **business domain knowledge**. It extends `minimal` with six sections designed for greenfield engagements where the product operates in a complex business domain.
+
+## When to Use
+
+- Greenfield product development in complex business domains
+- Client engagements that need to capture domain expertise alongside product specs
+- Products with regulatory, industry, or process complexity
+- Projects where the team needs a shared reference for "how this business works"
+- Any situation where product decisions depend on deep domain understanding
+
+## What You Get
+
+Everything from `minimal`, plus:
+
+```
+my-productbook/
+├── site.yaml              # Configured with 6 sections
+├── index.md               # Home page with product status and quick links
+├── CUSTOMIZING.md         # How to customize (AI + human friendly)
+├── content/
+│   ├── product/
+│   │   ├── overview.md            # Vision, users, capabilities
+│   │   ├── features/
+│   │   │   └── index.md           # Feature catalog
+│   │   └── releases/
+│   │       └── index.md           # Release log
+│   ├── domain/
+│   │   ├── overview.md            # Business domain context
+│   │   ├── processes/
+│   │   │   └── index.md           # Business process catalog
+│   │   ├── data-dictionary.md     # Terms and definitions
+│   │   └── industry-notes.md      # Regulations and standards
+│   ├── planning/
+│   │   ├── roadmap.md             # Phases and priorities
+│   │   ├── decisions/
+│   │   │   ├── index.md           # Decision log (ADR pattern)
+│   │   │   └── adr-template.md    # ADR template
+│   │   ├── specs/
+│   │   │   └── index.md           # Specification index
+│   │   └── research/
+│   │       └── index.md           # Research index
+│   ├── operations/
+│   │   ├── environments.md        # Dev, staging, production
+│   │   └── deployment.md          # Deployment procedures
+│   ├── guides/
+│   │   ├── getting-started.md     # Onboarding guide
+│   │   └── user-guide.md          # End-user documentation
+│   └── reference/
+│       ├── architecture/
+│       │   └── overview.md        # System architecture
+│       ├── integrations/
+│       │   └── index.md           # Integration catalog
+│       ├── data-models/
+│       │   └── overview.md        # Schemas and data flow
+│       ├── contacts/
+│       │   └── directory.md       # Team and vendor contacts
+│       └── metrics/
+│           └── overview.md        # KPIs and dashboards
+└── ...
+```
+
+## Sections
+
+| Section        | Purpose              | Typical Content                                            |
+| -------------- | -------------------- | ---------------------------------------------------------- |
+| **Product**    | What we're building  | Vision, features, releases, acceptance criteria            |
+| **Domain**     | The business reality | Processes, terminology, data dictionary, industry context  |
+| **Planning**   | Why and when         | Roadmap, ADRs, specifications, research                    |
+| **Operations** | How we run it        | Environments, deployment, configuration                    |
+| **Guides**     | How to use it        | Onboarding, tutorials, user documentation                  |
+| **Reference**  | Look-up material     | Architecture, integrations, data models, contacts, metrics |
+
+## The Domain Section
+
+This is what makes productbook different from every other template. It captures the **complex business reality** that the product operates in.
+
+For a propane delivery company, this might hold:
+
+- **Processes**: Tank monitoring workflow, delivery scheduling, seasonal demand forecasting
+- **Data Dictionary**: What "will-call" vs "automatic" delivery means, ERP entity definitions
+- **Industry Notes**: DOT regulations for hazmat transport, state-level propane licensing
+
+For a healthcare platform:
+
+- **Processes**: Claims adjudication, prior authorization, formulary management
+- **Data Dictionary**: CPT codes, NDC numbers, explanation of benefits
+- **Industry Notes**: HIPAA requirements, CMS guidelines, state insurance mandates
+
+This section is the "context dump" that every new team member and AI agent needs. It turns tribal knowledge into navigable documentation.
+
+## Planning Artifacts
+
+The planning section includes built-in support for common planning patterns:
+
+**Decision Records (ADRs)** — each decision documented with:
+
+- Context: What prompted this decision
+- Options: What we considered
+- Decision: What we chose and why
+- Consequences: What follows from this choice
+
+**Specifications** — feature specs with:
+
+- Problem statement
+- Proposed solution
+- Acceptance criteria
+- Status tracking
+
+**Research** — structured research outputs:
+
+- Market analysis
+- User research findings
+- Technology assessments
+
+The sidebar organizes these into collapsible groups — decisions, specs, and research each appear as expandable subsections under Planning.
+
+## Usage
+
+```bash
+kitfly init client-docs --template productbook
+kitfly init client-docs --template productbook --brand "Project Atlas"
+
+# With AI assistance instrumentation
+kitfly init client-docs --template productbook --standalone --ai-assist
+```
+
+## Productbook vs. Other Templates
+
+| Aspect          | Handbook     | Runbook                | Productbook                 |
+| --------------- | ------------ | ---------------------- | --------------------------- |
+| **Orientation** | How we work  | How we keep it running | What we're building and why |
+| **Assumes**     | Team exists  | System exists          | Starting from scratch       |
+| **Key section** | Guides       | Procedures             | Domain                      |
+| **Audience**    | Team members | Operators              | Product team + stakeholders |
+| **Tone**        | Explanatory  | Imperative             | Analytical                  |
+
+## Growing Your Productbook
+
+As the engagement matures, the sections grow naturally:
+
+**Domain deepens first** — business process docs accumulate as the team learns the domain:
+
+```
+content/domain/processes/
+├── index.md
+├── order-fulfillment.md
+├── returns-processing.md
+├── inventory-reconciliation.md
+└── seasonal-forecasting.md
+```
+
+**Product fills in as features ship** — feature pages link to the domain processes they automate:
+
+```
+content/product/features/
+├── index.md
+├── auto-scheduling.md      # References domain/processes/delivery-scheduling
+├── tank-monitoring.md       # References domain/processes/tank-monitoring
+└── customer-portal.md
+```
+
+**Planning captures decisions over time** — the ADR log becomes a valuable historical record.
+
+## Example Use Cases
+
+**Enterprise SaaS for Complex Industry**
+
+- Product: Platform features, integrations, user workflows
+- Domain: Industry processes, regulatory requirements, competitive context
+- Planning: Roadmap, ADRs for technology and vendor choices
+- Guides: Customer onboarding, admin guides
+- Reference: API architecture, third-party integrations, data models
+
+**Client Engagement with Legacy System Modernization**
+
+- Product: New platform capabilities replacing legacy functions
+- Domain: Existing business processes, data structures, edge cases the legacy handles
+- Planning: Migration specs, cutover decisions, research on replacement options
+- Operations: Parallel-run environments, migration deployment procedures
+- Reference: Legacy system documentation, data mapping, vendor contacts

package/dist/_raw/content/templates/runbook.md

@@ -0,0 +1,193 @@
+---
+title: Runbook Template
+description: Operational procedures, troubleshooting, and incident response
+---
+
+# Runbook Template
+
+The `runbook` template creates a structured site for operational documentation. It extends `minimal` with sections designed for on-call engineers, SREs, and operations teams.
+
+## When to Use
+
+- Operations documentation
+- On-call runbooks
+- Incident response procedures
+- System administration guides
+- Deployment and maintenance checklists
+- Any docs that answer "what do I do when..."
+
+## What You Get
+
+Everything from `minimal`, plus:
+
+```
+my-runbook/
+├── site.yaml              # Configured with ops sections
+├── index.md               # Home page with quick links
+├── CUSTOMIZING.md         # How to customize this site (AI + human friendly)
+├── content/
+│   ├── procedures/
+│   │   └── deployment.md         # Step-by-step procedures
+│   ├── troubleshooting/
+│   │   └── common-issues.md      # Problem → solution guides
+│   ├── reference/
+│   │   ├── interfaces/
+│   │   │   └── api-template.md   # Integration/API documentation
+│   │   ├── contacts/
+│   │   │   └── directory.md      # Team and vendor contacts
+│   │   ├── checklists/
+│   │   │   └── pre-deploy.md     # Verification checklists
+│   │   └── analytics/
+│   │       └── dashboards.md     # Metrics and KPI definitions
+│   └── incidents/
+│       └── escalation.md         # Incident response paths
+└── ...
+```
+
+## Sections
+
+| Section             | Purpose                          | Typical Content                                      |
+| ------------------- | -------------------------------- | ---------------------------------------------------- |
+| **Procedures**      | How to perform operational tasks | Deployment steps, maintenance tasks, migrations      |
+| **Troubleshooting** | Diagnose and fix issues          | Error codes, symptoms → causes, remediation          |
+| **Reference**       | Look-up information              | Interfaces, contacts, checklists, glossary           |
+| **Incidents**       | Emergency response               | Escalation paths, severity definitions, post-mortems |
+
+The **Reference** section consolidates supporting materials:
+
+| Subsection              | Purpose                                              |
+| ----------------------- | ---------------------------------------------------- |
+| `reference/interfaces/` | API specs, protocol docs, vendor integration details |
+| `reference/contacts/`   | Team directory, vendor contacts, escalation matrix   |
+| `reference/checklists/` | Pre/post deployment, audit, maintenance checklists   |
+| `reference/analytics/`  | Dashboard links, KPIs, SLA definitions               |
+
+## Usage
+
+```bash
+kitfly init ops-docs --template runbook
+kitfly init ops-docs --template runbook --brand "Platform Team"
+```
+
+## Design Principles
+
+Runbooks differ from handbooks in key ways:
+
+| Aspect           | Handbook      | Runbook                    |
+| ---------------- | ------------- | -------------------------- |
+| **Audience**     | Learning      | Doing (often urgently)     |
+| **Reading mode** | Sequential    | Jump to specific procedure |
+| **Goal**         | Understanding | Task completion            |
+| **Tone**         | Explanatory   | Direct, imperative         |
+
+## Procedure Document Format
+
+Each procedure should follow a consistent structure:
+
+```markdown
+# Procedure Name
+
+## Objective
+
+What this procedure accomplishes and when to use it.
+
+## Prerequisites
+
+- [ ] Required access or permissions
+- [ ] Tools or systems that must be available
+- [ ] Related procedures to complete first
+
+## Steps
+
+1. **First action**
+   - Expected output: `what you should see`
+
+2. **Second action**
+   - Verification: How to confirm success
+
+## Verification
+
+How to confirm the procedure completed successfully.
+
+## Rollback
+
+If something goes wrong, how to revert.
+
+## Related
+
+- Link to related procedures
+- Escalation path if this fails
+```
+
+## Growing Your Runbook
+
+As your runbook matures, consider:
+
+**Numbered sections** for ordering (enterprise pattern):
+
+```
+content/
+├── 00-bootstrap/    # Initial setup, first-run procedures
+├── 01-operations/   # Day-to-day operational tasks
+├── 02-incidents/    # Emergency response
+└── 99-reference/    # Templates, glossaries, checklists
+```
+
+**Recipes** - reusable procedures organized by topic:
+
+```
+content/procedures/
+├── security/
+│   ├── rotate-credentials.md
+│   └── access-review.md
+├── database/
+│   ├── backup.md
+│   └── restore.md
+└── deployment/
+    ├── standard-deploy.md
+    └── hotfix-deploy.md
+```
+
+## The Customizing Guide
+
+Every runbook includes `CUSTOMIZING.md` - a commissioning guide for both humans and AI assistants:
+
+**What it covers:**
+
+- How to add content to each section
+- Adding new sections to `site.yaml`
+- Conventions used in this runbook
+- File linking and cross-references
+
+**Important limitations:**
+
+- Content must live within the site folder (kitfly cannot include files from outside)
+- External resources should be linked via URL, not copied
+- Binary files (PDFs, images) go in `assets/` and are linked, not rendered
+
+This guide helps onboard team members and ensures AI coding assistants understand the structure when helping maintain the runbook.
+
+## Example Use Cases
+
+**Integration Runbook** (like Blossman/Cargas)
+
+- Procedures: Data sync, batch processing, error recovery
+- Troubleshooting: Connection failures, data format errors, timeout issues
+- Reference/Interfaces: ERP API specs (extracted from vendor PDF), protocol details
+- Reference/Contacts: Vendor support, internal integration team
+- Incidents: Sync failure response, data reconciliation
+
+**Platform Runbook**
+
+- Procedures: Deploy service, rotate secrets, scale cluster
+- Troubleshooting: High CPU, memory leaks, connection timeouts
+- Reference/Checklists: Production deploy, database migration
+- Reference/Analytics: SLA dashboard links, key metrics
+- Incidents: P1 response, rollback procedure
+
+**Security Operations**
+
+- Procedures: Credential rotation, access reviews, patch deployment
+- Troubleshooting: Auth failures, certificate expiry, firewall issues
+- Reference/Contacts: Security team, vendor security contacts
+- Incidents: Breach response, compromised credentials

package/dist/_raw/content/templates/servicebook.md

@@ -0,0 +1,163 @@
+---
+title: Servicebook Template
+description: Professional services catalog with offerings, methodology, and delivery documentation
+---
+
+# Servicebook Template
+
+The `servicebook` template creates a documentation site for **professional services practices** — what you sell, how you deliver, and proof of capability. It extends `minimal` with six sections organized around service offerings, delivery methodology, and engagement operations.
+
+## When to Use
+
+- Consulting practices documenting their service portfolio
+- Professional services teams standardizing delivery methodology
+- Technical assessment or advisory services needing consistent scoping
+- Organizations building a body of case studies and industry expertise
+- Any situation where the deliverable is expertise, not a product
+
+## What You Get
+
+Everything from `minimal`, plus:
+
+```
+my-servicebook/
+├── site.yaml              # Configured with 6 sections
+├── index.md               # Home page with service catalog summary
+├── CUSTOMIZING.md         # How to customize (AI + human friendly)
+├── content/
+│   ├── offerings/
+│   │   ├── overview.md            # Service tiers, engagement models
+│   │   └── assess/
+│   │       ├── overview.md        # Example: assessment service
+│   │       ├── deliverables.md    # What the client receives
+│   │       └── scoping.md         # How we scope an engagement
+│   ├── methodology/
+│   │   ├── phases.md              # Explore → Analyze → Synthesize → Deliver
+│   │   ├── tools.md               # Tools used in delivery
+│   │   ├── frameworks.md          # Assessment frameworks, scoring models
+│   │   └── decisions/
+│   │       ├── index.md           # Methodology decision log
+│   │       └── mdr-template.md    # Decision record template
+│   ├── delivery/
+│   │   ├── engagement-lifecycle.md  # End-to-end engagement flow
+│   │   ├── client-onboarding.md     # Prerequisites, setup, kickoff
+│   │   ├── quality-gates.md         # Checkpoints throughout delivery
+│   │   └── templates/
+│   │       └── index.md             # Deliverable templates and report shells
+│   ├── verticals/
+│   │   └── overview.md             # How to document industry context
+│   ├── case-studies/
+│   │   └── index.md               # Case study catalog with template
+│   └── reference/
+│       ├── team-expertise.md      # Capabilities, specializations
+│       ├── pricing-models.md      # Engagement pricing structures
+│       └── contacts/
+│           └── directory.md       # Team contacts, escalation
+└── ...
+```
+
+## Sections
+
+| Section          | Purpose               | Typical Content                                          |
+| ---------------- | --------------------- | -------------------------------------------------------- |
+| **Offerings**    | What we deliver       | Service tiers, engagement models, deliverables, scoping  |
+| **Methodology**  | How we do it          | Phases, tools, frameworks, methodology decisions         |
+| **Delivery**     | Engagement operations | Lifecycle, onboarding, quality gates, templates          |
+| **Verticals**    | Industry context      | Regulations, terminology, common challenges per vertical |
+| **Case Studies** | Proof of capability   | Past engagements (anonymized), outcomes, lessons learned |
+| **Reference**    | Look-up material      | Team expertise, pricing models, contacts                 |
+
+## The Methodology Section
+
+This is what makes servicebook different. It captures **how your practice delivers value** — not just what you sell.
+
+For a technical assessment practice, this might hold:
+
+- **Phases**: Explore (stakeholder interviews) → Analyze (gap analysis) → Synthesize (recommendations) → Deliver (presentation)
+- **Tools**: Interview frameworks, scoring rubrics, analysis templates
+- **Frameworks**: Maturity models, SWOT analysis, weighted scoring for vendor evaluation
+- **Decisions**: Why we switched from 3-phase to 4-phase methodology (MDR-001)
+
+For a management consulting practice:
+
+- **Phases**: Current State → Target State → Gap Analysis → Roadmap
+- **Tools**: Workshop facilitation tools, benchmarking databases, financial modeling
+- **Frameworks**: Operating model canvas, capability mapping, value stream analysis
+- **Decisions**: Why we standardized on a specific assessment framework
+
+The methodology section turns "how we work" from oral tradition into documented, repeatable process.
+
+## Usage
+
+```bash
+kitfly init consulting-docs --template servicebook
+kitfly init consulting-docs --template servicebook --brand "Apex Advisory"
+
+# With AI assistance instrumentation
+kitfly init consulting-docs --template servicebook --standalone --ai-assist
+```
+
+## Servicebook vs. Other Templates
+
+| Aspect          | Productbook                 | Servicebook                | Handbook          |
+| --------------- | --------------------------- | -------------------------- | ----------------- |
+| **Orientation** | What we build               | What we sell & deliver     | How we work       |
+| **Assumes**     | One product, iterated       | Multiple service offerings | Team exists       |
+| **Key section** | Domain                      | Methodology                | Guides            |
+| **Audience**    | Product team + stakeholders | Delivery team + clients    | Team members      |
+| **Tone**        | Analytical                  | Professional, prescriptive | Explanatory       |
+| **Lifecycle**   | Product releases            | Engagement lifecycle       | Knowledge updates |
+
+## Growing Your Servicebook
+
+As the practice matures, the sections grow naturally:
+
+**Offerings expand as services are defined** — each service gets its own folder with overview, deliverables, and scoping:
+
+```
+content/offerings/
+├── overview.md
+├── assess/
+│   ├── overview.md
+│   ├── deliverables.md
+│   └── scoping.md
+├── advisory/
+│   ├── overview.md
+│   └── engagement-models.md
+└── implement/
+    ├── overview.md
+    ├── deliverables.md
+    └── scoping.md
+```
+
+**Verticals deepen with experience** — each industry vertical captures specialized knowledge:
+
+```
+content/verticals/
+├── overview.md
+├── healthcare.md
+├── financial-services.md
+└── manufacturing.md
+```
+
+**Case studies accumulate** — the portfolio of evidence grows with each completed engagement.
+
+**Methodology evolves through decisions** — the MDR log tracks why the practice changed its approach.
+
+## Example Use Cases
+
+**Technical Assessment Practice**
+
+- Offerings: Security assessment, architecture review, cloud readiness evaluation
+- Methodology: Discovery interviews, tooling analysis, gap scoring, recommendations
+- Delivery: 2-4 week fixed-scope engagements with standardized quality gates
+- Verticals: Healthcare (HIPAA), finance (SOC 2), government (FedRAMP)
+- Case Studies: Anonymized assessment outcomes with measurable improvements
+
+**Management Consulting Practice**
+
+- Offerings: Strategy advisory, operating model design, transformation planning
+- Methodology: Current-state analysis, target operating model, roadmap development
+- Delivery: Retainer-based advisory with milestone-based transformation work
+- Verticals: Retail, energy, telecommunications
+- Case Studies: Transformation outcomes, efficiency gains, capability maturation