A fixed-fee audit of the software your business built for itself: the quoting tool, the scheduler, the app one smart employee stood up. Moonello inspects it across five domains and hands you a ranked roadmap of what needs attention, in what order, and why.
For most growing companies, the honest answer is "it works". An internal tool that started as a shortcut now runs quoting, scheduling, or operations, and nobody outside the person who built it has ever looked underneath.
This isn't a your-company problem; it's the new normal. Recent industry surveys found a majority of teams shipping software built outside IT oversight, and half of them shipping production code written with AI. At Moonello we think that's mostly good news as the builds we audit usually solve real problems. The unexamined part is the risk, not the building.
We see the same arc in nearly every audit: a spreadsheet became an app, the app got a login, customers' data got involved, and now the business quietly depends on it. Nobody decided to run operations on an unaudited system. That's precisely the moment to look underneath: after it matters, before it breaks.
Ask yourself who could fix your internal tool if its builder left, got promoted, or just went on vacation during a bad week. For most of our clients the honest answer is one name. The code may be fine; the dependency is the finding.
An audit doesn't ask whether the build was a good idea. It asks a better question: now that it exists, what does it need?
Every audit at Moonello runs the same five domains, a framework we built from years of inheriting, rescuing, and hardening internal systems. The domains exist so nothing depends on what an individual reviewer happens to notice.
DOMAIN 01
Authentication, access control, secrets handling, data protection, and vulnerability exposure. The questions your customers would want asked: who can get in, what can they reach, and what happens to the data the tool touches. This is where we most often find the shared password taped to the whole system.
DOMAIN 02
Can the system be safely extended, supported, and scaled as the business grows? Or is every new feature a game of Jenga? We read the structure the way the next developer will have to, because someday one will.
DOMAIN 03
Deployment practices, monitoring, error handling, backups, and recovery. The domain with the scariest simple question we ask every client: if this went down at 9 a.m. tomorrow, how would you find out, and how would you get it back?
DOMAIN 04
Key person dependency, documentation, access governance, and whether the organization can sustain the system independent of any single individual. The code can be excellent and this domain can still be the highest risk on the report.
DOMAIN 05
The domain most audits don't have, for the builds most companies now have. If your tool calls AI, and increasingly they all do, we assess prompt injection exposure, data leakage to third party model providers, cost controls, and whether automated outputs are reliable enough for what the business does with them. At Moonello we build production AI systems ourselves, which is exactly why we know where they leak.
Every finding in every domain is scored two ways, with technical severity and business impact, because a critical-sounding bug in a tool nobody depends on matters less than a modest one in the system that produces your quotes.
An audit is only as useful as the document it leaves behind, so we'll show you exactly what that is. Four deliverables, all yours to keep, all written to be acted on.
Every finding across the five domains, each with supporting evidence, a severity rating, and a plain language statement of business impact (what this means for the company, not just the codebase). Our clients tell us the impact lines are the part they actually read aloud in meetings.
Overall system health and the handful of risks that matter most, written for leadership rather than technical staff. If you forward one document to your partner or your board, it's this one.
A ranked action plan: what to address, in what order, and why, with relative effort indicated for each item so you can plan resourcing. Not a wall of problems, but a sequence of decisions. Whether your team executes it, another vendor does, or we do, the roadmap is written to work.
A working session of up to 90 minutes where we walk your stakeholders through everything, answer the hard questions, and align on next steps. We present findings to the people who built the system with the same respect we'd want in their chair. The readout is a briefing, not a trial.
And then we stay reachable: for 30 days after the readout, your team can send us written questions about anything in the report, and we'll answer at no charge. An audit shouldn't be a PDF that goes quiet the moment it's delivered.
Every audit at Moonello follows the same four steps on a published schedule. It's fast because the process is standardized. The framework does the remembering, so the calendar doesn't depend on heroics.
You provision read-only access to the code, the hosting environment, and whatever documentation exists; through named accounts, never shared credentials. We look; we don't touch. Nothing in an audit modifies, commits to, or deploys your system, which means there is no way for the audit itself to break anything.
We work through the five domains against the live picture: code, configuration, infrastructure, and one or two hour-long conversations with the people who built and maintain the system. Those interviews aren't interrogations. The builder usually knows exactly where the bodies are buried, and our job is to make it safe to say so.
You receive the findings report, the executive summary, and the prioritized roadmap. Every finding is scored for severity and business impact; every recommendation is sequenced. We write it assuming it will be forwarded to someone who wasn't in the room.
Up to 90 minutes with your stakeholders to walk the findings, take the hard questions, and align on what happens next. Then a 30 day written question period at no charge, because the report should start conversations, not end them.
The schedule has one dependency: access. Clients who provision it in the first two days get findings in two weeks; the audit can't start until we can see the system.
Audits at Moonello start at $3,500 for a single module and $15,000 for a full platform (fixed-fee).
One system, one core module: the quoting tool, the scheduler, the customer portal. All five domains, the full deliverable set: findings report, executive summary, ranked roadmap, readout, and the 30-day question period. The right size for a focused worry and the one tool you'd least like to be surprised by.
The whole internal system: every module, the integrations between them, and the infrastructure they share. Same five domains and deliverables, with scope and timeline confirmed after a short scoping call. The right size when the business has quietly accumulated a platform and wants one honest map of all of it.
Start where the worry is. A single module audit often becomes the first chapter of a platform audit and what you've paid applies toward the larger scope if you expand within six months.
One thing an audit deliberately is not: the fix. We identify and rank; remediation is its own engagement most often our Production Hardening retainer, where the roadmap you're holding becomes the work plan. Your audit fee credits toward the first hardening sprint.