GoAudits pricing and alternative
Paying GoAudits per user, and still chasing corrections by hand? Own the system that chases for you.
Book 30 minutes with Sam. Bring your last GoAudits invoice and the number of people who run visits. We look at what you pay now, what it becomes as you add stores and auditors, and which corrections keep slipping. Then we show you your own version with your GoAudits history brought across. One setup fee, then a monthly retainer, and the system is yours.
GoAudits lists Starter at $10 and Enterprise at $30 per user per month on annual billing ($12 and $35 billed monthly). Its pricing page does not name the dollar currency, so check your invoice. One person on Enterprise is $360 a year, and every auditor adds the same again.
- check_circle30 minutes with Sam, no obligation
- check_circleYour GoAudits history brought across
- check_circleNo per-user licence, ever
The recurring bill
The GoAudits bill grows with every auditor
Starter is listed at $10 per user per month and Enterprise at $30 with annual billing, or $12 and $35 billed monthly. Enterprise adds scheduling, permissions and advanced reporting. The dollar currency is not identified on the pricing page.
A licence for each user
GoAudits prices its plans per user. Count the paid people on your invoice before comparing the cost of your own system.
Checklists and responses
The platform holds your inspection questions and the answers recorded during each visit.
Scheduled inspections
Scheduling is included in Enterprise. Your own version holds visit dates, auditors and missed appointments.
Reporting and trends
Enterprise includes advanced reports and trends. Decide which regional comparisons your managers need each week.
Roles and permissions
Enterprise includes roles and permissions. Access for your own installation is scoped to the people doing the work.
Reports and action plans
Both plans include reports and action plans. The free base prepares visit reports and correction records from your history.
Your own version
Run the store review around the work that remains
Visits
Know which stores need attention
Prepare the regional visit list from dates and recorded coverage.
- check List planned visits with the auditor responsible
- check Find appointments that have passed without a visit
- check Show stores with no recorded visit
- check Keep each visit tied to its checklist snapshot
Standards
Keep a score from hiding a failure
Read the score beside missing answers and critical failures.
- check Weight each local standard explicitly
- check Exclude not-applicable answers with a recorded reason
- check Show critical failures beside the percentage
- check Find the same question failing on separate visits
Corrections
Finish with evidence and a reviewer
Separate work assigned, work completed and work verified.
- check Assign an owner and a due date
- check Record the correction and its evidence reference
- check Require a different reviewer to verify the result
- check Reopen a correction with a recorded reason
History
Keep the source behind the answer
Review the evidence and the original export before relying on a result.
- check Preserve original imported answers and score fields
- check Flag answers whose meaning still needs mapping
- check Find evidence references past their review date
- check See who changed a record and the reason supplied
Make it yours
Design your own GoAudits replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from GoAudits. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your GoAudits data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Store Audits for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Store Audits for Claude Code
Connected to your own database
Which visits have a critical failure or unanswered checks?
AKL-NEXT
- Site
- Harbour Homewares Auckland
- Status
- planned
- Total_checks
- 3
- Unanswered
- 3
- Failures
- 0
- Critical_failures
- 0
- Verdict
- Incomplete
WGN-LATEST
- Site
- Harbour Homewares Wellington
- Status
- submitted
- Total_checks
- 3
- Unanswered
- 0
- Failures
- 1
- Critical_failures
- 1
- Score_pct
- 50.0
- Verdict
- Critical failure
WGN-OLD
- Site
- Harbour Homewares Wellington
- Status
- submitted
- Total_checks
- 3
- Unanswered
- 0
- Failures
- 1
- Critical_failures
- 1
- Score_pct
- 50.0
- Verdict
- Critical failure
| Code | Site | Status | Total_checks | Unanswered | Failures | Critical_failures | Score_pct | Verdict |
|---|---|---|---|---|---|---|---|---|
| AKL-NEXT | Harbour Homewares Auckland | planned | 3 | 3 | 0 | 0 | Incomplete | |
| WGN-LATEST | Harbour Homewares Wellington | submitted | 3 | 0 | 1 | 1 | 50.0 | Critical failure |
| WGN-OLD | Harbour Homewares Wellington | submitted | 3 | 0 | 1 | 1 | 50.0 | Critical failure |
Ask it anything
Ten questions your store review can answer
These questions run against the included fictional records. GoAudits also offers reports and trends. Your own version adds the questions and rules your stores need.
Switching
How to switch from GoAudits
The move involves exporting your audit history, checking how its questions and answers map, and running both systems side by side briefly before you switch.
- 1
Get an export
Ask GoAudits what your account allows you to export, usually CSV or Excel, and check with them if you are unsure. Export question-level audit details, including the questions, answers, dates and original scores you want to keep. If you receive a workbook, the import uses its question-level sheet saved as CSV UTF-8. Keep the original exports so you can compare them with the imported records.
- 2
Map and test the import
Check that each column and answer label means what you expect before loading records. The import can read question-level details from a saved export, including the documented audit-details JSON structure. Start with a test run rather than loading records straight into the database. Review its results, adjust the mapping if needed, then run the import when the test looks right.
- 3
Review flagged records
Check the import results for answer labels that could not be mapped, and confirm the dates and row counts against your export. The import preserves original score fields and extra source fields. It rejects records when source keys have changed, so resolve those discrepancies rather than assuming they loaded. Keep the source export and review a representative store's records before relying on the imported history.
- 4
Run both systems briefly
Keep GoAudits available while your team uses the new database for a short period. Compare a representative store visit, its answers and scores, and any corrections your team needs to follow up. Confirm that the visit process and imported history fit your work before you stop using GoAudits. For needs such as photos, conditional forms, old action plans or notifications, agree on the separate handling before switching.
- 5
Switch off GoAudits
Once you have checked the imported records and your team is ready to use the new system, stop entering new work in GoAudits. Retain the original exports and any evidence you still need to reference. The database import does not fetch photos or copy notification rules and old action-plan history, so keep access to those records if they remain part of your review process.
Where the real effort goes
Most of the work is mapping your own fields and answer rules, then deciding how much history to bring. Question-level audit details and original scores can be imported, but photos, conditional forms, old action plans and notification rules need separate mapping. If you have Enterprise DNA build and run your version, they scope the mapping and reconcile those records with you.
Not ready for a call?
Get your GoAudits switch plan by email
We will send you the step-by-step plan for moving your business off GoAudits, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your GoAudits switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Start with the free version or have your own built and run
Open source
Do it yourself
Free, open source
- 1 Clone the repo and run npm install, then npm run demo
- 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the store review
- 3 Export GoAudits audit details, check the mapping and preview the import
- 4 Set your business name and generate the visit reports
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your store standards, scoring and evidence rules
- check Your GoAudits records mapped and reconciled
- check A collection screen for your team if required
- check Your choice of technology and connections
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed with access controls and backups
- check Your regional reviews and correction reports prepared
- check Kept working as stores and standards change
- check Run through Omni by Enterprise DNA beside the rest of your business
Questions
Instead of GoAudits, answered
What does GoAudits cost a business in New Zealand or Australia? expand_more
GoAudits lists Starter at $10 and Enterprise at $30 per user per month with annual billing, or $12 and $35 billed monthly. Its pricing page shows dollar and pound prices but does not name the dollar currency. Enterprise is $360 per user for a year. Bring your invoice to the call and we will work out the real annual figure for your team.
Will our GoAudits history carry across? expand_more
The free version reads question-level audit details from a saved export, with the column and answer meanings checked first. It preserves original score fields. Photos, conditional forms, old action plans and notification rules need separate mapping. We scope and reconcile those records when building your version.
Can store managers still use a phone? expand_more
Tell us how visits are collected today. We can build a mobile collection screen and the connections your team needs as part of your version. We agree that scope and test the visit process before you switch.
How do we know a correction was completed properly? expand_more
A correction needs a resolution and an evidence reference for the same check. A different reviewer then verifies it. The free version records the names supplied by the operator. We set up authenticated access for the people using your managed installation.
Does a passing score prove the store is compliant? expand_more
No. The score reflects recorded answers. Critical failures, unanswered checks and evidence reviews remain visible. The checks support your review of pricing practices and information handling. Your manager still checks the store, the evidence and the rules that apply.
Bring your GoAudits invoice to a 30-minute review
Spend 30 minutes with Sam. Bring your GoAudits invoice and a recent store report. We will work out what you pay in a year, the visits your team runs and the corrections it chases, and whether owning your own store audit system makes sense. If staying on GoAudits is the better call, we will say so.
Store Audits for Claude Code is free and open source, published by Enterprise DNA.
Done paying for GoAudits?
Book a 30-minute bill review