Capital Discipline Protocol

Experiment Kill Policy.

"One of the biggest mistakes in software is continuing failed products. Define clear limits."

FRAMEWORK STATUS: ENFORCED • REVISION 2.4 • SEPTEMBER 2026

1. Core Philosophy: Sunk Cost Defense

RULE // 01

Conventional incubators and agencies frequently succumb to the sunk cost fallacy—investing continued engineering hours into stagnant products simply because capital was already spent. At XPELAB, we consider ending an underperforming experiment a measure of operational success, not failure. Killing an unvalidated idea preserves engineering bandwidth and redirects capital toward initiatives with high market adoption.

Guiding Axiom: "Never invest unlimited capital into an idea. Validate early, fail fast, salvage components, and compound working ventures."

2. The 5 Sequential Decision Gates

EVALUATION PIPELINE

Every software initiative incubated in our lab must successfully clear five sequential empirical gates before qualifying for subsequent funding stages:

GATE 1 // PROBLEM

Problem Validation

Do customers actually experience this pain frequently? If NO → Stop experiment immediately.

GATE 2 // INTEREST

Customer Interest

Will target businesses test an interactive prototype or pilot workflow? If NO → Pivot or stop.

GATE 3 // PAYMENT

Payment Validation

Will customers commit hard capital to solve the problem? If users like the product but won't pay, the business model is unviable.

GATE 4 // RETENTION

Active Retention

Do pilot users continue active utilization? We monitor monthly active usage (MAU), recurring log-ins, and churn rates.

GATE 5 // SCALABILITY

Unit Economic Scalability

Can customer acquisition and infrastructure scale while recurring revenue grows faster than operational costs? If YES → Allocate scale capital.

3. The 60-Day Decision Gate & Metrics

60-DAY SPRINT

Following initial prototype or pilot deployment, every incubated experiment operates on a strict 60-day evaluation countdown with predefined minimum viability quotas:

TIME LIMIT

60 Days Active

MINIMUM PILOTS

≥ 10 Verified Users

MINIMUM PAID

≥ 3 Paying Accounts

✓ OUTCOME A: CRITERIA ACHIEVED → SCALE

The hypothesis is validated with paid demand. Allocate Phase 2 expansion budget, productize features, and integrate into regular release cycles.

↻ OUTCOME B: PARTIALLY ACHIEVED → PIVOT ONCE

High user engagement with friction in payment checkout. Granted one 30-day pivot cycle to re-align pricing or core workflows.

✗ OUTCOME C: NOT ACHIEVED → TERMINATE EXPERIMENT

Shut down active servers, notify pilot participants, extract generic architectural code into reusable libraries, and reassign developers.

4. Level 1–5 Budget Ceiling Rules

INVESTMENT CAPS

Capital allocations are strictly tiered. Engineering leads may not bypass a budget tier without meeting the preceding gate:

Level	Stage	Budget Ceiling	Exit Deliverables
Level 1	Idea Validation	₹2,000 – ₹5,000	Customer interview notes, landing page test.
Level 2	Interactive Prototype	₹5,000 – ₹20,000	Clickable wireframes, core UI workflows.
Level 3	Core MVP	₹20,000 – ₹75,000	Auth, database, payments, working admin panel.
Level 4	Pilot Testing	₹50,000 – ₹2,00,000	10+ live users, feedback logs, performance fixes.
Level 5	Product Scale	Funded by Revenue	CAC < LTV, churn < 5%, positive unit economics.

5. Reusable Component Salvage Protocol

IP RECOVERY

When an experiment is terminated, its development time is never wasted. The engineering squad executes our Code Harvest Protocol:

Identify modular utilities developed during the sprint (e.g., custom OAuth bridges, webhook listeners, SMS dispatchers).
Decouple business logic and package the generic module into the XPELAB Reusable Core Library.
Publish sanitized documentation internally so subsequent client projects and MVPs can reuse the component on Day 1.

6. Monthly Operating Review Cycle

CALENDAR

Our review board convenes on a continuous 4-week cadence to evaluate all active lab experiments:

WEEK 1

Research & Problem Validation

WEEK 2

Prototype & Internal Testing

WEEK 3

Customer Demos & Pilot Feedback

WEEK 4

Decision: Scale, Pivot, or Stop