Project Configuration

Overview

Project configuration captures the foundational choices that shape AlphaTales recommendations. App types, audience, and customer type help AlphaTales understand what kind of product you are building before it generates workflow, features, and Technical Architecture.

What Project Configuration Includes

Project configuration usually includes:

• Project name and description - The core product idea.
• App types - The surfaces you expect to build, such as web, mobile, API, desktop, or other.
• Audience - Whether the product is internal or external.
• Customer type - For external products, whether it is B2B, B2C, B2B2C, or developer-focused.

These inputs are captured during project creation and can influence later planning.

Select App Types

During project creation, choose all app types that apply. A product might need only a web app, or it might need a web app, API, and mobile app together.

App type choices help AlphaTales understand the expected product shape. They can affect workflow planning, feature scope, and Technical Architecture recommendations.

Tip: Select the app types you reasonably expect to build, even if the first version starts smaller. This gives AlphaTales better planning context.

Choose Audience And Customer Type

Choose Internal when you are building for your own team or organization. Choose External when the product is customer-facing.

For external products, customer type gives AlphaTales more context:

• B2B - You sell to other businesses.
• B2C - You sell directly to consumers.
• B2B2C - You reach end users through partners or customers.
• Dev Tool - You are building a developer-facing product.

These choices affect priorities such as integrations, collaboration, onboarding, scalability, and compliance needs.

How Configuration Affects Technical Architecture

After your planning context is ready, Technical Architecture can use configuration choices to recommend:

• Architecture style options.
• Frontend, backend, data, hosting, and supporting technologies.
• A high-level architecture diagram.
• The main technical direction for developer handoff.

When To Revisit Configuration

Revisit project configuration when:

• The product changes from internal to external, or the customer type changes.
• You add a new app type, such as mobile or API.
• Technical Architecture feels mismatched with the product scope.
• The team changes the target first version.

Warning: Changing configuration after generating recommendations may not automatically update existing outputs. Regenerate affected planning material when the change should influence later work.

Next Steps

After configuration is accurate, continue through Market Research, Workflow Alignment, Application Workflow, Features, and Technical Architecture.