Free Tool · No Signup · Runs in Browser

AI PRD Generator for Design Teams

Dhairya Purohit

Builds dMaya. Ships AI design workflows in real client work.

Published May 11, 2026

This AI PRD generator is the only free PRD template that adds a Design Direction section and ready-to-paste prompts for dMaya, Lovable, Bolt, v0, Cursor, Claude Code, Figma Make, and Stitch. Two sections no other AI PRD generator includes: visual direction for designers, and tool-specific prompts tailored to each AI tool's quirks.

Free, no signup, no API calls. The full product requirements document is generated in your browser. We are dMaya. We built this because every other PRD generator on page 1 is built for AI coding tools only and skips the design phase entirely.

# FreelanceFlow

> Project management and invoicing SaaS for freelancers.

## Overview

Project management and invoicing SaaS for freelancers. Built for Solo freelancers and small studios (1-5 people) in design, dev, and consulting..

## Problem & Goals

**Problem:** Freelancers stitch together 3-4 tools (Notion for projects, Stripe for invoices, Toggl for time, spreadsheets for cash flow). It is expensive, fragmented, and tax-time is a nightmare.

**Goal:** Build a product that solves the above for Solo freelancers and small studios (1-5 people) in design, dev, and consulting., shipping an MVP that proves the core loop before expanding scope.

## Target Users

Solo freelancers and small studios (1-5 people) in design, dev, and consulting.

## User Stories

- As a user, I want project tracking with milestones and deadlines, so that I can move my work forward without leaving the product.
- As a user, I want time tracking per project with hourly rates, so that I can move my work forward without leaving the product.
- As a user, I want invoicing with Stripe + bank transfer, so that I can move my work forward without leaving the product.
- As a user, I want client portal for project status, so that I can move my work forward without leaving the product.
- As a user, I want tax-ready expense reports, so that I can move my work forward without leaving the product.

## Functional Requirements

- Project tracking with milestones and deadlines
- Time tracking per project with hourly rates
- Invoicing with Stripe + bank transfer
- Client portal for project status
- Tax-ready expense reports

## Design Direction

**Visual direction:** Calm, professional, friendly. Slightly warm. Not corporate.

**Primary brand color:** Nature green (#2F7D55)

**Typography:** Use a system or modern sans-serif as the primary. Reserve a secondary face for headlines only if it adds character without sacrificing readability.

**Spacing & rhythm:** Generous whitespace. Consistent vertical rhythm. Avoid dense data tables; prefer cards or grouped lists with breathing room.

**Component patterns:** Use cards, lists, and contextual sidebars over modals where possible. Modals only for destructive confirmations or rare creation flows.

**Accessibility:** WCAG AA minimum. 4.5:1 text contrast. Keyboard navigable. Screen reader friendly labels on all interactive elements.

**What to avoid:** generic shadcn defaults without commitment to the brand color, dense corporate aesthetics, gradient overuse, and AI-default stock imagery.

## Screens to Build

- Dashboard
- Projects list
- Project detail with time tracking
- Invoices list
- Invoice editor
- Client portal
- Settings

## Non-Functional Requirements

- **Performance:** First Contentful Paint < 1.5s on 4G; Time to Interactive < 3s.
- **Responsive:** Mobile breakpoint at 640px, tablet at 768px, desktop at 1024px+.
- **Accessibility:** WCAG 2.2 AA compliance.
- **Browser support:** Last 2 versions of Chrome, Safari, Firefox, Edge.
- **Platform:** Web (responsive, mobile-friendly)

## Success Metrics

- 10 paying users within 90 days of launch
- Average user logs 4+ projects in first month
- >60% of invoices paid within 14 days

## Timeline & Rollout

MVP in 6 weeks. Phase 1 = Dashboard + Projects + Time tracking. Phase 2 = Invoicing + Client portal. Phase 3 = Tax reports.

## Open Questions

- Which authentication method (email/password, magic link, OAuth) fits Solo freelancers and small studios (1-5 people) in design, dev, and consulting. best?
- Pricing model and tier structure to be validated post-MVP.
- Internationalization scope: launch in English only or include other locales?
- Analytics stack and event taxonomy to be defined before build.

---

## Ready-to-paste prompts per AI tool

### For dMaya

```
I want to design FreelanceFlow: Project management and invoicing SaaS for freelancers.

Target user: Solo freelancers and small studios (1-5 people) in design, dev, and consulting.

Brand: Nature green (#2F7D55) as the primary color. Vibe: Calm, professional, friendly. Slightly warm. Not corporate..

Generate a multi-screen design covering: Dashboard, Projects list, Project detail with time tracking, Invoices list, Invoice editor, Client portal, Settings.

Pick Opus for the hero direction, Sonnet for follow-up screens. Keep components consistent across screens. Match the design direction in the PRD above (generous whitespace, cards over modals, no generic shadcn defaults).

Start with the Dashboard.
```

### For Lovable

```
Build FreelanceFlow: Project management and invoicing SaaS for freelancers.

Target user: Solo freelancers and small studios (1-5 people) in design, dev, and consulting.. Problem: Freelancers stitch together 3-4 tools (Notion for projects, Stripe for invoices, Toggl for time, spreadsheets for cash flow). It is expensive, fragmented, and tax-time is a nightmare.

Main features: Project tracking with milestones and deadlines, Time tracking per project with hourly rates, Invoicing with Stripe + bank transfer, Client portal for project status, Tax-ready expense reports.

Brand: Nature green (#2F7D55) primary. Vibe: Calm, professional, friendly. Slightly warm. Not corporate..

Start with the Dashboard. Use Supabase for auth and DB. Keep the UI clean, generous whitespace, cards over modals.
```

### For Bolt.new

```
Build a running web app: FreelanceFlow. Project management and invoicing SaaS for freelancers.

Target user: Solo freelancers and small studios (1-5 people) in design, dev, and consulting..

Primary color: Nature green (#2F7D55). Aesthetic: Calm, professional, friendly. Slightly warm. Not corporate..

Start with the Dashboard, then we will add Projects list and Project detail with time tracking in follow-up prompts. Commit to the brand color across the whole UI (do not default to indigo or slate).
```

### For Cursor (chat / agent)

```
I am building FreelanceFlow: Project management and invoicing SaaS for freelancers.

Build the Dashboard component first. Tech: Next.js 15 App Router + Tailwind + shadcn (or match the existing stack in this repo).

Brand primary color: Nature green (#2F7D55). Visual direction: Calm, professional, friendly. Slightly warm. Not corporate..

Match the design direction in the PRD: generous whitespace, cards over modals, no generic shadcn defaults. Keep the file structure clean and place new components under components/.
```

---

_PRD generated with dMaya AI PRD Generator (dmaya.ai/tools/ai-prd-generator). Free, runs in browser, no signup._

What makes this AI PRD generator and PRD template different

Every AI PRD generator on page 1 of Google today (ChatPRD, TinyPRD, RapidNative, makemyprd, writemyprd) ships the same PRD template: take an idea, generate a PRD, hand it to a coding agent (Cursor, Lovable, Bolt, v0) to build the app. The PRD template they produce has Overview, Goals, User Stories, Functional Requirements, and Timeline. None of them include a Design Direction section. None of them generate prompts for AI design tools.

If your workflow goes idea → design phase → code phase (which is what most product UI work actually looks like), the PRD template from those tools is missing half the work. This free PRD generator adds two sections nobody else has: a Design Direction block covering visual direction, brand cues, screens, and accessibility, plus tool-specific prompts for the full set of AI tools (dMaya, Stitch, Figma Make, Claude Design, Lovable, Bolt, v0, Cursor, Claude Code).

The Design Direction section: the missing piece

A traditional PRD treats design as a downstream concern. The developer reads the PRD, builds the feature, then a designer (if there is one) reviews it. This works when the design phase is a step in a long process. It does not work when you are using AI tools that have to make visual decisions in 30 seconds based on whatever context you give them.

AI design tools (dMaya, Stitch, Figma Make, Claude Design) need explicit visual direction in the prompt, not after generation. If you tell Bolt "build a freelancer SaaS dashboard," you will get the Bolt default aesthetic. If you tell it "build a freelancer SaaS dashboard with nature green primary, generous whitespace, cards over modals, no shadcn defaults," you get something that respects your design direction. The difference is what you put in the prompt, which is what the Design Direction section of the PRD captures.

The four things our Design Direction section captures and other PRD generators do not: primary brand color (named explicitly, not just "use my brand"), visual vibe (calm/playful/corporate/minimal, again explicit), what to avoid (shadcn defaults, gradient overuse, dense corporate aesthetics), and accessibility requirements (WCAG AA, contrast ratios, keyboard navigation). Each one is a sentence in the PRD that translates directly into the AI tool prompt downstream.

How to use this PRD with each AI tool

With dMaya (vibe design)

Paste the dMaya prompt block (auto-generated at the bottom of your PRD) into a new dMaya project. The prompt is structured to use the model picker (Opus for the hero, Sonnet for follow-ups) and explicitly references your Design Direction section so the output commits to the brand color and visual vibe instead of defaulting to a generic aesthetic. Generate the first screen, review on canvas, iterate on the rest. Once the multi-screen design is settled, use dMaya's HTML export to hand the design to Cursor or Claude Code for the build phase.

With Lovable, Bolt, or v0 (vibe coding)

Paste the tool-specific prompt block into the new project flow. Each prompt is formatted for the tool's quirks: Lovable's prompt is conversational (best for chat-driven iteration), Bolt's emphasizes the running-app brief and explicit color commitment (Bolt's default is to pick indigo unless told otherwise), v0's uses Next.js + shadcn conventions and CSS-variable theme syntax. Build the first screen, verify the visual direction held up, then use follow-up prompts for additional screens from your Screens to Build list. Plan to be on the Pro tier ($25/mo Lovable + Bolt, $20/mo v0 Premium) for multi-screen evaluation.

With Cursor or Claude Code (build phase)

These tools are for the build phase, not the design phase. The natural workflow: use dMaya or Stitch for the design phase, export clean HTML, then paste the Cursor or Claude Code prompt (which references your Design Direction section) and tell the agent to convert the HTML into your stack. Cursor's Visual Editor is then the right surface for visual iteration on the running code. Cursor Pro is $20/mo. Claude Code is included with Claude Pro ($20/mo) and Claude Max ($100-200/mo).

With Figma Make or Stitch

Figma Make works best when you already have a Figma file with components and styles set up; the generated prompt references your existing system. Stitch (Google Labs) works best with a tighter, more direct prompt because the tool has less context window for elaborate briefs. Both produce static design output, not running code, so they belong in the design phase alongside dMaya.

When NOT to use a PRD

Some product work does not need a PRD. Spike work where the entire goal is to test a single hypothesis in a few hours. Pure visual exploration where you are trying to find a direction, not commit to one. Bug fixes and minor copy changes. Internal tools used by 3 people who can just talk to each other. A PRD for any of these is overhead, not leverage.

Use a PRD when (a) more than one person is touching the work, (b) the work will take more than a week, (c) you are handing it to an AI tool that has no other context, or (d) you want to be able to revisit your own decisions in three months and remember why. For everything else, a one-paragraph brief is fine.

What makes a great PRD for AI-driven workflows

AI tools optimize for what is in the prompt and ignore what is not. A great PRD for AI workflows is one where every consequential decision is explicit. "Use my brand colors" is not explicit. "Primary color: #2F7D55, secondary: #1A4332" is explicit. "Modern and clean" is not explicit. "Generous whitespace, cards over modals, no shadcn defaults" is explicit.

The other thing that matters for AI workflows: ordering the PRD so the AI gets the most important context first. Tool-specific prompts at the end of the PRD are intentional: they let you copy just the prompt for the tool you are using without scrolling. The Design Direction section sits in the middle because the AI design tools need it more than the coding tools do, but the coding tools still benefit when they get to the build phase.

The PRD template this generator produces is intentionally short. Most traditional PRDs are 10-20 pages because they include extensive market research, competitive analysis, and scenario walkthroughs. AI tools do not benefit from any of that and often do worse when buried in context. Keep the PRD tight, lead with the decisions that constrain output, and let the AI tool fill in the rest. A good free PRD generator is one that produces less, not more.