You’ve built 90%.
Let’s finish this.
An agent got you a working app in a few weekends. Then Apple sent it back twice, the payments only half work, and nobody can tell you whether last month’s customer records are still there. Each of those is its own piece of work, and none of them was ever part of getting the thing to run.
We are Cayman, in Sydney. We finish software — seven of our own products taken through App Review, billing, migrations and monitoring. For A$2,500 we go through what you have built and give you the list of what stands between it and a live release, with a price against every line.
- Price
- A$2,500 fixed
- Time
- 5 working days
- Credit
- Off the build in full
- Based
- Sydney, Australia
Where these builds stop.
Six that come up again and again on software written fast. Every one of them is invisible from the screen you were shown, and every one of them is cheaper to find now than after a release.
- 01
Review keeps sending it back
Apple does not tell you that you are close. A first submission usually comes back on 2.1 for a build that crashes or still has placeholder content, on 5.1.1 for asking for data you do not need or having no privacy policy that loads, on 3.1.1 for taking money for digital goods outside in-app purchase, or on 5.1.1(v) for having no way to delete an account from inside the app. Each round trip costs a day or two, and the reasons stack rather than arrive together.
- 02
Your keys went out with the app
An API key compiled into the app can be read by anyone who downloads it. It gets put there because that is what makes the simulator work, and nothing about the app behaves differently afterwards. The first sign is your usage bill.
- 03
Payments only work on the good day
The card that goes through is the easy case. Declines, refunds, chargebacks and a subscription lapsing overnight all need somewhere to land. If the Stripe webhook is unverified, or cannot cope with the same event arriving twice, you get customers charged twice and paid-up customers locked out.
- 04
One customer can read another customer
A Supabase table with row-level security left off returns every row to any signed-in user, not just their own. It passes every test you ran, because while you were testing there was one account.
- 05
The next update eats the data
Changing the shape of the database without a migration drops whatever was in the old column. On your laptop that is a nuisance you fix by starting again. After launch it is last month’s customer records, and without backups there is nowhere to get them back from.
- 06
You find out from a one-star review
An app with no error reporting says nothing at all when it breaks on somebody else’s phone. The first you hear of it is a customer, in public, at the top of your store listing.
The audit.
We go through what you have built and come back with the list of everything standing between it and a live release. Every item costed, every item timed. You decide what to do with it, including nothing.
- Price
- A$2,500, fixed. Nothing is billed hourly and nothing moves after you agree it.
- Credit
- Credited in full against the build if you have us do the work. Take the report elsewhere and you have still paid once for it.
- Time
- 5 working days from the day we get access.
- We need
- The repository, and read access to wherever it runs. No call to book first.
- You get
- A written report, item by item, each one costed and timed. It is yours and you can hand it to anyone.
- If it is fine
- Then the report says so, and you have spent the money finding out. That happens, and we will not pad the list to justify the fee.
What the report covers
- 01 Every reason Apple or Google would send it back, written against the guideline number so you can check us.
- 02 What is sitting in the shipped bundle and in the repository history that should never have left your machine.
- 03 Which payment paths are handled and which ones quietly lose the money — declines, refunds, chargebacks, a subscription that lapses overnight.
- 04 What one signed-in customer can read that belongs to another.
- 05 Whether you can ship an update without losing what your customers have already put in.
- 06 What falls over at a hundred users, and what falls over at ten thousand.
- 07 What it costs to run each month before a single customer pays you.
When not to buy it.
- It is still an idea. Nothing to audit yet — send it as a brief instead and you get the same reply inside a business day.
- You want an argument that the code should have been written another way. We report on what is standing between this build and a release, with a price against each line, and leave how it got here alone.
- You need it finished by Friday. The audit takes a working week, and whatever it finds takes longer than that.
Tell us what you have got.
Where it is up to, what it was built with, and what it is doing that it should not. A reply comes back inside a business day saying whether the audit is the right thing to buy. Sometimes the answer is that you have a smaller problem than you think and it does not need one.
- 01 We do not share your build or your idea with anyone.
- 02 We do not use it, and we do not go and build it ourselves.
- 03 Want it in writing before you hand over a repository? Send your NDA to [email protected] and we will sign it first. What the form stores.