Three Paid Reviews
for Audio Software

// ROUTING

Which review fits your situation?

Pick by the decision in front of you: release readiness when a launch, investment or acquisition hangs on product quality, the rescue diagnostic when a repository exists and needs a credible completion plan, the ML review when the idea itself is unproven. A product with no code yet, a single reproducible defect, or a released product needing support belongs to a different route.

// RELEASE READINESS

Release-Readiness Review

This review suits a launch, an investment, an acquisition, a change of developer, or more spending on a product assembled with AI tools. We agree the boundary first, then work the questions you chose: stability, maintainability, feature behaviour, audio correctness, platform coverage, third-party integration, licensing exposure, security and privacy, performance, release readiness and realistic completion cost. The boundary can be the whole product or a defined set of environments, and we look at third-party components only as your product uses them.

The audit is a standalone engagement, separate from the rescue diagnostic below. It does not disclose our internal audit system or hand you a reusable implementation recipe, and its findings commit neither side to implementation. We confirm the scope after seeing your objectives and the available material, and the proposal states payment stages, timing and acceptance. An NDA comes first.

// RESCUE DIAGNOSTIC

JUCE Rescue Diagnostic

Bring us a product that already has a repository and needs substantial completion, recovery or release work. The diagnostic suits unclear codebase condition, inherited development, stalled builds, broad feature gaps, or a product that needs a realistic route to beta, v1 or release. Most of these repositories are JUCE and C++. After an NDA where required, we take repository access, build and run the product, and check it in an appropriate audio host where relevant. The review is bounded at two working days, and a simple build issue may be corrected inside it.

All of it arrives as one concise findings and proposal document. It does not answer every technical question, and it is not a full audit. Its fee is separate, non-refundable, and not credited against later implementation. If the product needs broader recovery or investigation, we propose it as a defined first milestone. Payment comes before the review starts.

// ML FEASIBILITY

Audio ML Integration Review

Some DSP and machine learning ideas cannot be responsibly promised in advance, so this review tests one inside a bounded scope. Use it when you need evidence before a larger commitment, or when the question is whether an approach is useful, reproducible and suitable for a product. The written scope defines that question, the available material, the constraints, the evidence we expect, and the decision the work should support. Datasets, licences, specialist services and target hardware are agreed before work begins.

Acceptance rests on completing the agreed investigation and delivering its evidence. It does not rest on a scientific breakthrough, a particular subjective sound, model performance that was never agreed in writing, or a commercially successful end product. The first engagement runs hourly, billed in 30-minute increments, or as a bounded milestone. Where effort is uncertain we work to a cap you approve and stop there unless you approve more time in writing. Subjective DSP or workflow outcomes include two consolidated feedback rounds unless the proposal says otherwise.

// DELIVERY

What do you get at the end?

Every review ends in a written document you can act on, plus a call to take you through it. From there you either approve a written scope with deliverables, fees, assumptions and acceptance terms, or you keep the document and stop.

Implementation after a review runs in milestones, 20% before each and 80% after acceptance, with invoices due in 14 calendar days and ten business days to review each delivery. Projects stay confidential by default, and we name one only with your written permission. Once the agreed fees are paid in full, you own the project-specific intellectual property.

// COST

What does a review cost?

We quote each review privately after the first call, so this page carries no prices. The figure moves with the size and condition of the repository, the formats, platforms and hosts inside the boundary, how much of the DSP or model work is original, and whether datasets, licences or target hardware are involved. Volume pricing may be available if you commit multiple products or milestone-based engagements.

The first two calls are free and last about 30 minutes each. They cover fit, priorities, budget and timing rather than unpaid code review or technical solution design. The intake form has an optional budget band: it reaches us by email only, stays out of our analytics, and helps us recommend the smallest sensible first engagement.

// FAQ

Common Questions