# Create a SaaS Application

> Transforms a SaaS concept into a structured application specification and build plan.

## Best For

- Transforms a SaaS concept into a structured application specification and build plan.
- Work involving website and SaaS
- Producing a copy-ready deliverable with explicit accuracy rules

## Recommended AI

- ChatGPT
- Claude
- Gemini

## Difficulty

Advanced

## Information to Provide

- [INSERT TOPIC OR SOURCE MATERIAL]
- [INSERT GOAL]
- [INSERT AUDIENCE]
- [INSERT REQUIREMENTS]
- [INSERT CONSTRAINTS]
- [INSERT OUTPUT FORMAT]
- [INSERT TONE OR STYLE]
- [INSERT DEADLINE OR LENGTH IF RELEVANT]

## Quick Prompt

```text
Act as a senior product designer, web engineer, and application architect. Your objective is to deliver the result described here: Transforms a SaaS concept into a structured application specification and build plan.

Use this context: [INSERT TOPIC OR SOURCE MATERIAL]. Goal: [INSERT GOAL]. Audience: [INSERT AUDIENCE]. Requirements: [INSERT REQUIREMENTS]. Constraints: [INSERT CONSTRAINTS]. Output format: [INSERT OUTPUT FORMAT].

Cover users, roles, workflows, data model, billing assumptions, security, screens, APIs, and phased delivery. Avoid vague filler, unsupported claims, invented facts, and unnecessary repetition. Do not invent missing facts. If a missing detail is essential, ask up to three focused questions; otherwise state a reasonable assumption. Return an implementation-ready product or design specification with organized sections, requirements, states, edge cases, and acceptance criteria.
```

## Advanced Prompt

```text
Act as a senior product designer, web engineer, and application architect.

OBJECTIVE
Deliver the result described here: Transforms a SaaS concept into a structured application specification and build plan.

CONTEXT
- Topic or source material: [INSERT TOPIC OR SOURCE MATERIAL]
- Goal or decision this must support: [INSERT GOAL]
- Intended audience: [INSERT AUDIENCE]
- Known background and evidence: [INSERT CONTEXT AND VERIFIED FACTS]
- Platform, environment, or channel: [INSERT PLATFORM]

REQUIREMENTS
1. Cover users, roles, workflows, data model, billing assumptions, security, screens, APIs, and phased delivery.
2. Follow these user requirements: [INSERT REQUIREMENTS].
3. Respect these constraints: [INSERT CONSTRAINTS].
4. Match this tone or style: [INSERT TONE OR STYLE].
5. Use this target length or deadline when relevant: [INSERT LENGTH OR DEADLINE].
6. Make the result specific to the product idea, users, platform, technical constraints, visual direction, and success criteria; do not produce a generic answer.
7. Check the final result for internal consistency, missing steps, and unusable ambiguity.

ACCURACY AND BOUNDARIES
- Do not invent facts, quotations, sources, product features, statistics, experience, or results.
- Clearly label assumptions, estimates, and inferences.
- When current or external facts are required and browsing is available, verify them with reliable sources and cite direct links.
- When required evidence is unavailable, write [NEEDS VERIFICATION] or ask a focused question instead of guessing.
- Avoid vague filler, unsupported claims, invented facts, and unnecessary repetition.

OUTPUT
Return an implementation-ready product or design specification with organized sections, requirements, states, edge cases, and acceptance criteria.
Use this exact requested format: [INSERT OUTPUT FORMAT].
Begin with the finished deliverable. Put assumptions, verification needs, or optional alternatives afterward.
```

## Example Input

```text
Topic: homework planner web app; Goal: help students plan assignments; Audience: middle-school students; Requirements: dashboard, calendar, reminders, dark mode; Constraints: responsive vanilla HTML/CSS/JS; Output: page map, features, UI states, and acceptance criteria.
```

## Customization Options

* Tone
* Length
* Audience
* Detail level
* Output format
* Platform or AI model

## Expected Output

Return an implementation-ready product or design specification with organized sections, requirements, states, edge cases, and acceptance criteria. The result should directly address the stated goal, preserve supplied facts, label assumptions, and be usable without another rewrite.

## Related Prompts

* [Create a Landing Page](Create%20a%20Landing%20Page.md)
* [Design a Dashboard](Design%20a%20Dashboard.md)