Ninja Forms · Fixes & Renewal Decisions

Ninja Forms Support — and an Honest Look at the Add-On Bill

Ninja Forms sells its capability as separate add-ons, which is fine when you need two and expensive when you need six. Most sites we are handed are running an ageing install, several add-ons, and at least one licence nobody has renewed. We fix what is broken, then help you decide what is actually worth paying for.

Ask about your Ninja Forms setup

Australian team

Based here, working your hours — not a timezone away

144+ projects delivered

Over 10+ years building and maintaining sites for Australian businesses

One developer, start to finish

The same person every time — no re-explaining your site

Straight answers, on your terms

We only take work we can finish. Ask us anything first — no obligation

This is not a page arguing you should leave Ninja Forms — plenty of sites should stay, and we will say so. If your problem is spam volume rather than the forms themselves, start with the Cloudflare page. If you are comparing where to go should you move, the Gravity Forms and WPForms pages are written for that reader rather than for us.

Add up what the add-ons cost you in a year

This is the number that decides everything else, and very few sites have it written down anywhere. Ninja Forms is inexpensive to start and scales by capability: each integration, each payment method, each piece of extra functionality is its own purchase with its own renewal. A site that grew gradually can be paying several hundred a year across half a dozen line items for what a single licence elsewhere would cover. Once that figure exists, the stay-or-move question mostly answers itself.

Lapsed add-ons keep working until they suddenly matter

An expired add-on licence does not switch the feature off. It stops the updates, silently, and the form carries on until a PHP version change or a WordPress release finds the incompatibility. That is why this surfaces as a form that broke for no apparent reason, months or years after the actual cause. Establishing which add-ons are on the site, which are current and which lapsed is the first thing worth doing, and it is frequently the whole diagnosis.

Keep it updated — this one has had a serious vulnerability

Ninja Forms has been the subject of a vulnerability severe enough that WordPress pushed a forced security release to sites running it, which is a step reserved for genuinely dangerous cases. This is not a reason to distrust the plugin today; it is a reason to make sure the site is actually receiving updates rather than sitting on whatever version it had when the last developer left. A plugin that touches every enquiry you receive is not one to leave out of date.

Actions are where a Ninja Forms site is really configured

What happens after a submission is built from actions — send an email, store the submission, post somewhere, run an integration — and they can be conditional. On most sites we look at, the actions have accumulated: notifications to people who have left, duplicates added when something appeared not to work, integrations pointing at systems no longer in use. Reading them properly is unglamorous and routinely explains both the missing enquiries and the duplicate ones.

The three-column builder has opinions about layout

Ninja Forms lays fields out in a fixed column structure, and finer control over layout is one of the things sold separately. A great deal of what people want from that is achievable with a small amount of CSS in your theme, which does not renew and does not break when the add-on is updated. We will tell you which of the two your requirement needs rather than assuming the paid route.

Your submissions and how to get them out

Submissions are stored in the site, which is the strong point of being on this plugin rather than one that only emails. Two things are worth doing with that: exporting them somewhere durable so the record does not depend on the plugin, and deciding a retention period, because on most installations they accumulate indefinitely and they are personal information you are responsible for. Both also make any future migration far simpler than it would otherwise be.

The renewal decision, done with numbers

When a renewal comes up the choice is renew, drop the add-ons you can live without, or move. We price all three honestly, including the one that earns us nothing. Moving is a real project — forms rebuilt, integrations rewired, historic submissions brought across — and it only pays back when the annual add-on total is large or you are about to need two more of them. Sites with two current add-ons and forms that work should renew and spend the money elsewhere.

What this costs

A diagnostic — what is installed, what has lapsed, what the actions actually do and what the yearly total is — is $249 and is written down for you to keep. Fixes and rebuilds start at $300, fixed-quoted. Ongoing work is $165 an hour, or $750 for five hours and $1,400 for ten.

Care plans

Plans, and what each one actually includes.

Month to month, no lock-in — change or cancel any time. Prices in AUD.

Essential

$159 /mo AUD

Keeping a site secure, updated and online. No development time included.

What is covered

  • WordPress core, theme & plugin check
  • Weekly off-site backupsA full copy of your site and database taken every week and stored on separate infrastructure, not on your own server — so a failure, a hack or a bad update cannot take the backups with it., restorable on request
  • Uptime & SSL monitoringYour site is checked from outside every few minutes. If it goes down, or the security certificate is about to expire, the alert reaches us — you are not the monitoring system. — alerts come to us, not you
  • Malware checkFiles and database are scanned for injected code, so anything that has been planted is found rather than waiting to be noticed. maintained
  • Broken-link and 404 checks
  • Monthly report of site status
  • Email support included
Start with Essential

Billed monthly in AUD. Cancel any time — no lock-in.

Dev

$700 /mo AUD

Your site stays up, stays secure and stays current — and when something breaks, a developer fixes it rather than logging it.

What is covered

  • Critical security & performance checksThe checks that catch the things that actually take a site down: outdated core and plugins with known vulnerabilities, injected code, error rates, and pages that have become slow enough to lose visitors. every week
  • Uptime & SSL monitoringYour site is checked from outside every few minutes. If it goes down, or the security certificate is about to expire, the alert reaches us — you are not the monitoring system. — alerts come to us, not you
  • Weekly off-site backupsA full copy of your site and database taken every week and stored on separate infrastructure, not on your own server — so a failure, a hack or a bad update cannot take the backups with it., restorable on request
  • Your developer emails you every month with what changed and what needs attention
  • Staging site for development changesA private copy of your site where changes are built and checked before anyone else sees them. Updates, new sections and design work go there first, get looked at on phone, tablet and desktop widths, and only reach the live site once you have said so. It matters most on page-builder sites, where a bad update does not error — it re-renders, and the page looks subtly wrong on a screen size nobody checked. — nothing reaches the live site unapproved
  • 5 hours of developer time a month
  • Fixes and small changes — not a build. Content, layout and design edits, plugin and integration setup (included in dev hours)
  • 1 basic page built to match your existing design (included in dev hours)
  • Weekly WordPress core, theme & plugin updates (included in dev hours)
  • Weekly malware and virus check, and fix (included in dev hours)
  • Speed & Core Web VitalsCore Web Vitals are the three loading and stability measures Google uses as a ranking signal — how fast the main content appears, how quickly the page responds to a tap, and whether it jumps around while loading. We measure and fix all three. check and fix (included in dev hours)
  • Priority queue — a developer is assigned and contacts you within 48 hours
  • Urgent issues covered for 1 hour of immediate debugging — you are told what we found, while we work and once it is fixed
Choose Dev

Billed monthly in AUD. Cancel any time — no lock-in.

Most popular

Master

$1,300 /mo AUD

Where Dev fixes and maintains, Master builds — pages, integrations, and the email and domain problems nobody else will own.

Everything in Dev Plan included +

  • Staging site for development changesA private copy of your site where changes are built and checked before anyone else sees them. Updates, new sections and design work go there first, get looked at on phone, tablet and desktop widths, and only reach the live site once you have said so. It matters most on page-builder sites, where a bad update does not error — it re-renders, and the page looks subtly wrong on a screen size nobody checked. — nothing reaches the live site unapproved
  • 10 hours of developer time a month
  • Everything in Dev — the same checks, monitoring, backups and monthly email
  • Up to 3 pages designed and built (included in dev hours)
  • CRM, accounting and API integrationsConnecting your site to the systems you already run — a CRM like HubSpot, accounting like Xero, or any service with an API — so data moves between them without anyone retyping it. (included in dev hours)
  • Email deliverability problemsWhen forms stop arriving, or your mail lands in spam. We work through the sending records — SPF, DKIM and DMARC — and the mail service itself, rather than telling you to check your junk folder. diagnosed and fixed (included in dev hours)
  • Domain and DNS issuesExpiring domains, records pointing at the wrong place, certificates that will not renew, a migration that left half the traffic behind. The infrastructure layer most agencies hand back to you. handled (included in dev hours)
  • Custom features and functionality (included in dev hours)
  • WooCommerce & payment gateway work (included in dev hours)
  • Same-day response on anything urgent — a developer will work outside business hours if needed
  • Quarterly performance and security checksEvery three months we re-run the full audit: load times and Core Web Vitals, plugin and PHP versions, user accounts and permissions, backup restores, and anything flagged since the last review. You get the findings in writing. (included in dev hours)
Choose Master

Billed monthly in AUD. Cancel any time — no lock-in.

Ultimate

Quoted scoped to the work

When the roadmap needs more than Master, or the work is better run as a project.

Get a quote

Everything in Master Plan included +

  • 20+ hours a month, or a fixed-price project
  • A standing slot in our schedule
  • Multi-site and white-label arrangementsWe look after several sites under one agreement, and — if you are an agency or consultancy — we can work under your brand, so your client only ever deals with you.
  • Architecture, infrastructure and hosting work
  • Direct access, no ticket queue
  • We will tell you honestly whether a retainer or a fixed quote costs you less
Why CloudyWP

Why a Ninja Forms Review Starts With the Invoice

The features are sold separately. On most sites the real question is the renewal, not the form.

The Yearly Total, Written Down

Each integration and payment method is its own purchase with its own renewal date. Very few sites have the combined figure anywhere. Once it exists, the stay-or-move question largely answers itself.

Lapsed Licences Found

An expired add-on does not switch the feature off — it stops the updates, silently. That is why the break arrives a year after the cause, looking like a form that failed for no reason.

Actually Receiving Updates

This plugin has had a vulnerability serious enough for WordPress to force a release to every site running it. Fine today if current — the risk is a site that quietly stopped updating when somebody left.

Actions Read Properly

Notifications to people who left, duplicates added while troubleshooting, integrations pointing at retired systems. Reading the actions explains both the missing enquiries and the duplicate ones.

Your Entries Made Portable

Submissions live in the site, which is the strong point of being here. Exported somewhere durable and given a retention period, they stop depending on the plugin — and any future move gets far simpler.

Told When To Renew

Two current add-ons and forms that work means renew and spend the money elsewhere. We price the move as well, and say plainly when it does not pay back.

What Ninja Forms users ask

Our form stopped working and nothing changed.

Something changed, and on a Ninja Forms site the usual candidate is an add-on that has not been updated in a long time meeting a new PHP or WordPress version. The licence lapsing is invisible at the time it happens, so the cause and the symptom can be a year apart. We check the add-on inventory and licence status first because it resolves this more often than anything else.

Should we move to a different form plugin?

Only if the arithmetic says so. Add up the annual add-on renewals and compare it against a single licence elsewhere plus the one-off cost of rebuilding what you have. If you run two add-ons and everything works, staying is the right answer and we will tell you that. If you are renewing six, the maths usually points the other way inside two years.

Can we keep our old submissions if we move?

Generally yes, because Ninja Forms stores them in the site rather than only emailing. They can be exported and, depending on where you are going, imported. The part to decide is how much history you actually need live in the new system versus archived somewhere as a file — bringing ten years of entries across is often cost without benefit.

Is Ninja Forms safe to keep using?

Yes, provided it is kept current. It is actively maintained, and the serious vulnerability in its past was patched and force-pushed to sites precisely so that it would not linger. The real risk on any older form plugin is not the vendor, it is a site that stopped receiving updates because a licence lapsed or nobody was responsible for applying them.

We are getting duplicate notification emails.

Almost always duplicated actions. Somebody added a second email action while troubleshooting a delivery problem that was actually caused by the site sending unauthenticated mail, the original started working later, and now both fire. Reading the actions resolves it in minutes — and it is worth fixing the underlying sending at the same time so it does not recur.

Can you add a payment to our form?

Yes, and the first question is whether it should be a form at all. For a donation or a one-off amount, a form with a payment add-on is reasonable. For anything with products, tax, or repeat purchasing, a form is the expensive way to build a checkout and it will keep needing extensions. We will say which one your requirement actually is before quoting.

Nobody here knows which add-ons we are paying for.

That is the normal situation and it is exactly what the diagnostic is for. Between what is installed on the site, what is active, and what is still being billed, there are usually discrepancies in both directions — something paid for and not used, or used and quietly lapsed. You get the list written down and it is yours regardless of what you decide afterwards.

Is it slowing our site down?

It can contribute, particularly when its assets load on pages with no form on them and when several add-ons each add their own. It is rarely the main cause of a slow site, though, and we would rather measure than assume — replacing a form plugin to chase a performance problem that was actually images or hosting is an expensive way to learn what the real cause was.

Can you take over from a developer we no longer work with?

Yes, and you do not need their cooperation — admin and hosting access is enough. The first job is working out how the forms are actually assembled: which add-ons are involved, what the actions do, where submissions go and which licences exist. On a Ninja Forms site none of that can be assumed, and all of it changes what anything else costs.

Ask about your Ninja Forms setup

A short call, a fixed quote, and no obligation either way.

Get a fixed quote

Why CloudyWP

Broken forms, lapsed add-on licences and a renewal bill nobody has added up. Melbourne Ninja Forms support, with the stay-or-move maths done properly.

Get a fixed quote

02 — How we work

From first call to live — four steps, no surprises.

Every CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.

01

We map what you actually need.

A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.

Typically 48 hours

02

We design and build it properly.

Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.

2–6 weeks typical

03

We automate the busywork.

Your site talks to the tools you already run — CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.

Average 15 hrs saved weekly

Scope A fixed quote, in writing

Deliverables, price and dates agreed before a line of code is written.

  • Free scoping call
  • Written scope document
  • Fixed price, no hourly creep

48 hrs to your quote

Get a quote