Getting started

Build your first WordPress plugin

From a plain-English description to a downloadable, installable plugin ZIP — here's exactly what happens and what you need to do at each step.

1

Describe your idea

Go to Dashboard New Plugin (or the big input on the builder screen). Write what your plugin should do in plain English — no code required.

What makes a good description? Be specific about the outcome, not the implementation. Instead of "add an email feature", try "Send me an email notification when a new WooCommerce order is placed with a total over $500". Mention named third-party services (Stripe, Mailchimp, etc.) if the plugin needs to talk to them.

Toggle WooCommerce plugin on if your idea involves carts, orders, products, or checkout. This routes your build through an extra WooCommerce-specialist agent that knows WC hooks and templates.

2

Answer a few clarifying questions

The AI analyses your idea and asks 0–5 targeted questions to pin down anything that would meaningfully change what gets built. Common questions cover:

  • Which pages or post types the feature should appear on
  • Whether generated content should auto-publish or need admin approval
  • Which specific third-party providers to support (e.g. OpenAI vs multiple LLMs)
  • Whether the plugin is for logged-in users, public visitors, or both

Most questions are click-to-choose — pick from pre-filled options or leave any blank and the AI makes a sensible default. If the idea is already clear, this step is skipped automatically.

3

Review and select features

Based on your answers, the requirements agent produces a feature list. Each feature gets a complexity label (Low / Medium / High) that feeds into the credit estimate.

Deselect any features you don't need before moving on — removing a High-complexity feature can meaningfully lower the credit cost and simplify the generated code.

4

Review scope, cost, and risks

Before committing to a build you'll see:

  • Plugin name & slug — AI-proposed, you can change them before approving
  • Credit cost estimate — typically 15–35 credits depending on complexity
  • Risk flags — anything that might cause WordPress.org reviewers to ask questions (e.g. external HTTP calls, data storage, admin-only pages)
  • WooCommerce warnings — hooks or actions that could affect live store behaviour

Click Approve & Build only when you're happy. Credits are deducted at this point.

5

Wait for the build to complete

The builder runs up to 12 AI agents sequentially (idea → requirements → UX → scope → architecture → WordPress specialist → security → QA → packaging → readme). A typical build takes 2–5 minutes.

You'll see a live progress bar. You can safely leave the page — the build runs in the background and you'll receive a notification when it's done.

If the build is stuck on the same stage for more than 8 minutes, something has gone wrong. The system will automatically detect this, cancel the build, and refund your credits. See the troubleshooting guide for next steps.
6

Download and install

Once the build is complete you'll land on the download screen. Click Download ZIP — the file is a standard WordPress plugin package ready to upload via Plugins → Add New → Upload in your WP admin.

The download page also shows a feedback form (star rating + optional comment). Feedback helps improve future builds — it only takes five seconds.

Credits & billing

What are credits? Credits are the build currency on BuildPlugins.ai. Every new account starts with 30 free credits — enough for 1–2 simple builds to try the product before paying.

Credit cost by complexity

Build typeCredits used
Simple plugin (1–2 features)15
Medium plugin (3–5 features, settings page)20–25
Complex plugin (WooCommerce, REST API, multiple integrations)30–35

Refunds — if a build fails through no fault of yours (model timeout, system error), credits are automatically refunded within a few minutes.

Credits never expire. Unused credits on a subscription plan carry over to the next month.