Cayman Software studio · Sydney · Est. 2017

How we work.

A screenshot shows none of this, which is why most quotes look much the same until the work starts. Here is what we do before we would call a job done, and what it is like to work with us.

What “finished” means.

Anyone can show you something that runs on their laptop. This is the part that takes the time, and it is the part you are really paying for.

Exploded assembly drawing of a phone separated into seven stacked layers along dashed alignment axes
Fig. 1 An app is a good deal more than the screen you were shown.
  1. 01

    It goes live properly

    Not a test link that expires in 90 days. Panoramica is on the App Store. Tarmac, ClickLens, ChartReps and Strudo are on the web right now, and you can open them from this page. CrankPilot is with Apple waiting on approval. You will always know exactly where yours is.

  2. 02

    Payments work, including when they do not

    Cards get declined and subscriptions lapse. Refunds come in six weeks after the sale. The app handles each of those on its own, so you are not reconciling payments by hand or losing a customer to a failed charge nobody saw.

  3. 03

    You hear about problems from us, not your customers

    Every app we build reports its own errors. When something breaks after hours we get told that night, and you hear it from us before a customer writes a one-star review about it.

  4. 04

    Nothing gets lost

    Updates are tested against real data before they run, so an upgrade never eats last month's records. Anything personal is encrypted on your phone before it is stored anywhere.

  5. 05

    You own all of it

    The code, the domain, the App Store listing, the Stripe account. All in your name from the first day. If you want to take it to somebody else in two years, there is nothing to untangle and nobody to ask.

  6. 06

    The boring pages are done

    The privacy policy and the terms, and a support page somebody answers. Apple will not approve an app without them, and customers read them before they hand over a card.

CAY-A1

If it is already built.

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

  1. 01 Every reason Apple or Google would send it back, written against the guideline number so you can check us.
  2. 02 What is sitting in the shipped bundle and in the repository history that should never have left your machine.
  3. 03 Which payment paths are handled and which ones quietly lose the money — declines, refunds, chargebacks, a subscription that lapses overnight.
  4. 04 What one signed-in customer can read that belongs to another.
  5. 05 Whether you can ship an update without losing what your customers have already put in.
  6. 06 What falls over at a hundred users, and what falls over at ten thousand.
  7. 07 What it costs to run each month before a single customer pays you.

Ask for the audit A$2,500 fixed, five working days

Working together.

How it starts
You send the idea. A reply comes back inside a business day with what it would take and what we’d build first. Nobody has to book a call to get that far.
What we quote
A first slice at a fixed price with a date on it. When that slice lands, the next one is scoped from what we learned building it. We do not price a whole build up front, because that number is a guess and you would be the one paying for it.
What you own
The repository, the accounts, the domains, the App Store listing. All of it in your name from the first commit, so there is nothing to unpick if you take it elsewhere.
When we say no
If it needs a discipline we do not have in-house, or is regulated in a way we could not carry responsibly. And sometimes the real problem is a process, and software would only decorate it. Either way you hear it in the first reply.

Tell us the idea or email [email protected]