Requirements Gathering

Applies to: App Generation projects that use the SaaS Engine template

The AI Architect gathers the information that AppWizzy needs to create your initial application. It asks follow-up questions until the project is ready.

Start with the business result

State the problem that the application must solve. Describe the people who use it and the result that each person needs.

Include these items when they apply:

  • the main user roles.
  • the records that users manage.
  • the important fields for each record.
  • the relationships between records.
  • the main workflows and approval steps.
  • the permissions for each role.
  • required dashboards and reports.
  • required integrations.
  • required tenant or organization boundaries.
  • visual style and brand requirements.

Do not start with a long list of page names. Start with the real work that users must complete.

Example first request

Create a customer support portal for agents, managers, and customers. Include tickets, messages, priorities, teams, service levels, and reports.

The AI Architect can ask about ownership, status changes, permissions, metrics, and other missing details.

Use the creation interface

  1. Open Create New App.
  2. Select SaaS Engine in the template selector.
  3. Enter your first requirement in Build anything.
  4. Add relevant images when they help explain the required interface.
  5. Send the request.
  6. Answer each follow-up question with specific business rules.
  7. Review the selected machine size and privacy option.
  8. Wait for AppWizzy to start generation.

You can leave the template selector on Auto. Confirm that the final recommendation is SaaS Engine for an App Generation project.

The interface can improve the wording of your first request. Review the improved text before you send it.

Describe the data model

Name the main record types in business language. Examples include Customer, Contract, Ticket, Invoice, Location, and Appointment.

For each record, describe its required fields and relationships. State which values must be unique, required, private, or calculated.

Use clear singular names for record types. Use the same term throughout the conversation.

Read Create Schema for schema guidance.

Describe roles and permissions

List each role and its allowed actions. State who can create, view, update, approve, export, and delete each record type.

Describe ownership rules explicitly. State whether users can see all records, team records, organization records, or only their own records.

If each customer organization needs separate data, state that the application requires multitenancy.

Describe workflows

Describe each important state change. Include the person, trigger, required data, next state, and resulting notification or action.

For example, define what happens when a manager approves a request. State which fields change and which users receive access.

Know when the requirements are ready

The AI Architect marks the request ready after it has enough information. AppWizzy can then start generation automatically.

The creation conversation becomes part of the project record. AppWizzy also uses it to prepare the initial application description.

Do not treat readiness as final acceptance. Review the generated application, data model, permissions, and workflows before production use.

Correct a misunderstanding

Correct the term or rule in the next message. State the wrong interpretation and the required interpretation.

Use this format:

Change the rule for ticket access. Agents must see tickets for their assigned team, not all tickets.

After creation, use Edit via Chat for further changes. Read Generated App Editor.