The agreed user journeys
Walk through the selected actions, including relevant failure paths, and record where behaviour differs from the intended result.
Technical review of an app you already have
Built the app? Know what needs attention before the next step
Your app works in the preview, but you need someone to examine the user journeys, access boundaries and launch arrangements. Josh C reviews the agreed scope and gives you written findings with a walkthrough. Suitable for Lovable apps and existing web applications, subject to access and scope.
Start with what the app does and what you need to decide. The call is free. The technical review is paid work, quoted before you commit.
Sample review findingIllustrative only
An access check with a next step
See how an observation becomes a finding. This example does not connect to or test your app.
Example app · Customer portal
- Expected
- Each customer can open only their own documents.
- Review step
- Use two authorised test accounts to check the boundary.
A written review records what was tested, the evidence and what remains untested.
A sample format, not a customer result, security scan or certification.
Your paid technical review
Quoted first
A fixed price for your agreed review scope, with GST stated in writing
- For
- An existing app, including one built with Lovable
- Output
- Written findings, priorities and a walkthrough
- Timing
- Confirmed after checking the app and required access
- Repairs
- Quoted separately, with no obligation to use us
We agree the app version, test boundaries and deliverables first. A review records what was examined and what remains untested. It does not certify the app or guarantee a launch outcome.
Josh CVibeZero founder, your technical review contact
Josh's background covers software development and IT infrastructure, with experience across government, enterprise and not for profit organisations.
What you get
A review you can use to decide what happens next
Your written scope selects the journeys and systems that matter. We distinguish confirmed findings, unanswered questions and areas outside the review.
Access and data boundaries
Examine the agreed authentication and authorisation paths using permitted test accounts. Record the access checks and limitations.
Launch and ownership arrangements
Review the agreed hosting, service ownership, deployment and recovery arrangements. Identify missing information before operational responsibility changes.
Written findings and a walkthrough
Get evidence, priorities and suggested next steps. Review the findings with Josh and decide whether to fix, investigate, defer or seek specialist testing.
Illustrative example
What a useful finding contains
An illustrative review entry. This is not a result from your app or a customer project.
| Part of the finding | Example contents |
|---|---|
| Expected behaviour | One customer can access only their own documents. |
| Evidence | Describe the authorised two account test, app version and observed result. |
| Next step | Correct the access boundary, then repeat the same test. |
| Limitation | Only the agreed document journey was tested. Other routes remain outside scope. |
The example demonstrates the format. Actual findings depend on the agreed scope, access and observed behaviour.
Scope
What the price covers, and what it does not
Included
- An agreed review scope and fixed quote before paid work
- Review of the selected journeys, technical settings and evidence available
- Written findings with priorities and explicit testing limitations
- A walkthrough of the report and recommended next steps
Not included
- Repairs, new features, a rebuild or production changes
- A full penetration test or certification unless separately scoped
- Legal advice, regulatory approval or a guarantee of security
- Hosting, platform subscriptions and ongoing support
Access is agreed before review activity. Use test accounts and sanitised data where possible. A public app link alone does not permit testing private routes or other people's systems.
How it works
Start with the decision you need to make
An existing app and a specific next step give the review its scope. You approve the paid work before granting review access.
Describe the app
Tell us what exists, how it was built and what you need to decide.
Agree scope and access
We confirm the review boundaries, price, delivery date and authorised test activity in writing.
Review and record
We examine the agreed version and record findings, evidence and anything we could not assess.
Choose the next step
We walk through the report. Repairs or specialist testing need their own approval.
Nothing is charged until you approve the scope in writing.
Scope my app reviewBefore you commit
Agree the review before granting access
The free call scopes the engagement. It does not include a private code review. The paid review, testing permissions and any later remediation are separate decisions.
- Price
- Fixed in your written quote
The quote states GST, app scope, output and exclusions.
- Timing
- Agreed after access is checked
An enquiry does not reserve a delivery date.
- Changes
- Review only
Repairs and production changes require separate approval.
- Ownership
- You keep the report
You can discuss it with your developer or another provider.
Practical questions
What you might want to know
Can you review an app I built in Lovable?
Yes. Tell us what the app does, who will use it and which backend it uses. We confirm the code, settings and test access available before quoting. You do not need to commission a new build to request a review.
What if Lovable's security scan is clear?
Lovable provides Quick and Deep security scans, including application code checks in its Deep scan. Those are useful inputs. Our agreed review adds technical judgement and testing of the selected user journeys and access boundaries in your app. A clear scanner or review cannot guarantee complete security.
How much does an app readiness review cost?
We quote a fixed price after checking the app, its intended use, integrations and the access needed. The written quote states GST, review boundaries, deliverables and timing. The initial scope call is free. Repairs, a rebuild, ongoing support and a penetration test are separate unless explicitly included.
Does this certify that my app is safe to launch?
No. This is a point in time technical review of the agreed scope. Findings distinguish observed problems, questions and areas we could not test. It is not a certification, legal opinion, compliance assessment or guarantee that no defects exist. You remain responsible for the launch decision.
Will you change the app during the review?
The review does not include repairs or production changes. We agree access and authorised test activity first, use test accounts where possible and document findings. Remediation requires a separate approved scope.
Can my own developer use the report?
Yes. The report explains findings and recommended next steps so you can discuss them with your developer. You can ask VibeZero to quote repairs separately, but there is no requirement to do so.
Is this the same as a security audit or app rescue?
A readiness review considers the agreed user journeys and operational arrangements as well as technical risks. A security audit has its own security testing scope. App rescue includes repair work. We confirm the right engagement after hearing what you need.
Do you work outside Perth?
Yes. VibeZero is based in Perth and works remotely with app owners across Australia. We agree review access, scope and a walkthrough time before starting.
Next step
Get a review scope for the app you already have
Scope my app review
Perth based, working remotely across Australia. You approve the review and price before paid work starts.