Your first project with AussyPrompt ONE, step by step

Welcome to AussyPrompt ONE. This guide walks through your first project from start to finish. It takes about an hour to plan, and the build itself depends on your tool and the size of the project. Keep it open next to your ONE workspace at aussyprompt.com/one.

Before you start: pick a small first project

Your first project should be real but small: one process that wastes time every week. Good first projects:

• A quote or enquiry follow-up that sends itself
• A booking form with reminders
• A job card app for one team
• A simple website for one service
• A dashboard for the three numbers you check most

You can build the bigger system once you have seen how ONE works.

Step 1: describe it once

On the Projects page, the composer asks "What do you want to build?"

1. Pick the kind of project: App, Automation, Dashboard, Internal System or Website. This tells ONE what to put the detail into.
2. Name your project in the box above the prompt (optional; ONE names it from your description if you leave it blank).
3. Describe it in your own words, as you would explain it to a new colleague. Say who uses it, what happens step by step, what you record, and the tools you already use. You can also press the microphone and say it.
4. Choose Build with: the tools you build with, such as Lovable, Cursor, Supabase or n8n. You can change these later; the build pack updates straight away.
5. Press send (or Enter).

Not sure what to write? Press + to start from a Command Playground result, or pick one of the ideas under the box. Templates are written for South African businesses; edit the details to match yours.

Tip: specifics beat length. "Technicians see only their own jobs and can't delete anything" is worth more than a paragraph of background.

Step 2: wait while ONE plans and checks

ONE drafts the blueprint, then checks its own work against your description before you see it. This usually takes one to two minutes. You can stay on the page.

Step 3: read the blueprint

This is the most important step. Everything your tools build comes from here, so ten minutes now saves hours of fixing later.

• ONE checked its work. The green or amber note at the top says what ONE fixed before you saw it, and anything worth a look. Open the details and read them.
• Assumptions to check. Where your description didn't say, ONE made a reasonable guess and listed it. Correct any that are wrong.
• Open questions. Things ONE couldn't assume. Answer them.
• Roles, tables, screens, automations and KPIs. Check the roles are named the way your business talks, the statuses are the ones you actually use, and nothing important is missing.

Step 4: tell ONE what to change

In Tell ONE what to change, type changes in plain words, one or two at a time:

• "Add a Suppliers table linked to stock items."
• "Technicians can't see invoice amounts."
• "Send the weekly report on Mondays at 8am, not daily."
• "Answers to the open questions: we use Microsoft 365, and the office manager gets the alerts."

ONE updates the blueprint and checks the change too. Every version is kept: open History to go back. If the blueprint is far off, Start again from the brief rebuilds it from your description.

Step 5: take the build pack

Open the Build pack tab. You'll find files for each tool you chose, each with a step-by-step guide:

• App builders (Lovable, Bolt, v0): build prompts, numbered in order. Paste them one at a time, and check each step before the next.
• Cursor or Claude Code: a project spec with acceptance criteria and a task list.
• Supabase or MySQL: a database file to run once, with your tables, links and security rules.
• n8n: workflow files you import in one click. Make, Zapier and Power Automate: build guides, step by step.
• Dashboards: guides for Google Sheets, Looker Studio or Power BI, with a definition for every number.

Copy a file, download it, or use Download pack to get everything as a .zip. Add a tool with More tools and the pack updates instantly.

Tip: start with the guide file for your tool (for Lovable, 00-GUIDE). It tells you what to run first.

Step 6: build it, in order

Follow the guide for your tool. The order matters:

1. The database first, if you chose one.
2. Then the app or website, prompt by prompt.
3. Then the automations, connected to the app.
4. Then the dashboard.

Use your exact table and field names; the pack already does. If your tool asks something the blueprint answers, paste the relevant part of the blueprint. Never paste passwords or API keys into a prompt; keep them in each tool's own settings.

If you want to save credits while you build, read how to stop burning credits.

Step 7: launch together

Open the Launch tab. The checklist is written for the tools you chose, and it is shared with everyone in your business, so the team can tick steps off together.

• Set the project status as you go: Blueprint, Pack ready, Building, Live.
• Work through the test plan with real examples from last week, not made-up ones.
• When it's working, add the live link and press Mark as live.

When something goes wrong

• The tool built something different from the blueprint: paste the relevant part of the blueprint back in and ask it to match exactly.
• You need a change: change the blueprint in ONE first, then ask your tool to apply that change. Keeping the blueprint up to date keeps every tool in step.
• You're stuck: email support@aussyprompt.com with your project name and what you tried.