Create Your First AlphaTales Project

Create Your First Project

Beginner

Create your first AlphaTales project for an internal app or customer product, then capture the initial context your team needs to plan the work properly.

What you’ll learn

Open the project creation wizard
Choose between Internal apps and Customer apps
Complete the required intake fields
Understand where each journey goes next

Overview

Creating a project is the first planning action in AlphaTales. A project can represent an internal tool for your organization or a customer-facing product you want to build.

The wizard starts by asking which journey fits the work: Internal apps or Customer apps.

Open The Wizard

Open the project wizard from the dashboard, sidebar, or project list. The same wizard creates both internal and customer projects.

If you are in a team workspace, you can use the internal app flow. If the internal option is unavailable, check that you are working inside the right team workspace.

Create An Internal App

Choose Internal apps when the tool is for your own organization. AlphaTales shows internal tool types such as approval workflow, dashboard and reporting, admin console, data management, self-service portal, search assistant, automation orchestrator, and not sure.

Complete the required fields:

Enter the Application name.
Choose the Application type.
Describe what the app needs to do.

Add helpful context when you have it:

The business goal.
Users and roles.
Main tasks.
Data systems.
Rules, access, or reporting needs.
The success outcome.

After creation, AlphaTales takes you into Project Breakdown for the internal app journey.

Create A Customer App

Choose Customer apps when the product is for customers, partners, consumers, or developers outside your organization.

Complete the project name and description, then choose the customer context:

B2B for business customers.
B2C for consumers.
B2B2C for products that reach users through another organization.
Dev Tool for developer-facing products.

Choose the application types that apply, such as web, mobile, desktop, API, or other.

Review Before Creating

Before clicking Create Project, check that the audience is correct. Internal and customer projects use different planning paths, research focus, and handoff expectations.

Warning: If you choose the wrong journey, later planning output may focus on the wrong users, risks, and artifacts.

What Happens Next

Internal projects move through Project Breakdown, Internal Research, Workflow Alignment, Application Workflow, Features, Technical Architecture, and Dev Pack.

Customer projects move through Project Breakdown, Market Research, Workflow Alignment, Application Workflow, Features, Technical Architecture, PRD, and Dev Pack.

Next Steps

Open the new project and follow the next action shown on the project overview. Start with Project Breakdown so later planning steps have the right context.