Story Points and the Wallet

Overview

Agiloop IMPLEMENT uses complexity-based pricing to measure the cost of feature implementation.

These complexity units are referred to as Story Points.

Each story point represents the estimated implementation effort required for Agiloop IMPLEMENT to perform:

• Code generation
• Validation
• Verification
• Review orchestration
• Supporting implementation processes

Story points are billed at:

• $0.25 USD per story point

Wallet System

Agiloop uses a two-level wallet system to manage story point balances:

• Account Wallet
• Project Wallet

This structure allows organizations to centrally manage purchased story points while controlling allocation across projects.

Account Wallet

Your Account Wallet stores all purchased story points for your organization or account.

When you purchase story points, they are added directly to the Account Wallet.

From there, you can distribute points to individual projects as needed.

Project Wallet

Each project has its own dedicated Project Wallet.

Project wallets are used by IMPLEMENT during feature generation and implementation workflows.

You may transfer story points:

• From your Account Wallet into a Project Wallet
• From a Project Wallet back into the Account Wallet

This provides flexibility when managing multiple projects or implementation priorities.

How Story Points Are Used

Feature Queuing

When a feature is queued for implementation:

• IMPLEMENT places a temporary hold on the required number of story points
• The hold is applied against the Project Wallet balance

This ensures sufficient balance exists before processing begins.

Feature Processing

When the feature transitions into the In Process status:

• The held story points are consumed from the Project Wallet
• Implementation and code generation begin

Once consumed, the story points are considered used for that implementation cycle.

Balance Requirements

To generate code for a feature using IMPLEMENT:

• Your Project Wallet must contain enough available story points to cover the feature cost

If insufficient balance exists:

• The feature cannot enter the implementation queue
• IMPLEMENT processing will not begin until additional points are added

Viewing Wallet Information

You can manage your story points directly from the wallet interface located in the application header.

From the wallet area, you can:

• View Account Wallet balance
• View Project Wallet balances
• Review transaction history
• Transfer story points between wallets
• Purchase additional story points

Understanding Feature Costs

Feature story point values are generated during the INVENT planning and estimation process.

Complexity factors may include:

• Backend architecture requirements
• Frontend complexity
• Infrastructure needs
• Security requirements
• Integration points
• Data modeling
• Validation and testing scope

Larger or more technically complex features generally require more story points.

Best Practices

• Maintain a reserve balance in active project wallets
• Regularly review transaction history and usage trends
• Allocate points based on project priority and roadmap planning
• Review feature estimates before queuing large implementation cycles
• Use project wallets to control spending across teams and initiatives

Example Workflow

1. Purchase 5,000 story points
2. Points are added to the Account Wallet
3. Transfer 1,000 points into Project A
4. Queue a feature estimated at 120 story points
5. IMPLEMENT places a hold for 120 points
6. Feature enters In Process
7. 120 story points are consumed from the Project Wallet
8. Generated code proceeds through review and approval workflows