About
We speak human, not code.
You run the place. We build the app, so you don't have to. The package is written down. The revision rounds are counted. Care is its own bill. Campaigns are a third bill. No mystery estimate.
Tell us how it works. Then we build it.
Five steps. The scope is written before the design starts. The build starts with a 50% deposit.
01Tell us how it works
Who it is for, what it has to do, what you use today, and when you need it. Plain language is perfect.
02We check the thing
We confirm the app can actually do the job, including whether it can send push and in-app messages.
03It goes in writing
The build, the monthly plan, any campaigns, and the revision rounds. Work starts with a 50% deposit.
04We build it
Designs use the rounds we counted. We test the main paths. The rest of the build fee is due when you accept it.
05You get back to the floor
We help you publish and hand it over. Monthly care starts, messages included. Ads are their own job.
Who runs it
One person per job.
Each part of the work has one owner, from the first conversation to the ads, so you always know who has your app.
- 01
Elly Yan
Head of Connect
Takes the first conversation, learns how the place works, and matches you to the right package.
See Connect → - 02
Ryan Graham
Head of Builds
Scopes the app, counts the screens, and gets it into the App Store and Google Play.
See Builds → - 03
Joy Ausler
Head of Care
Keeps the app up after launch: the hosting, the monthly hours, and the messages that go out.
See Care → - 04
Josh Lovejoy
Head of Reach
Runs the ads that put the app in front of the people who should have it.
See Reach →
In writing
Your name stays on it.
Account, source code, content, customer data, and the messaging list are named in the agreement. The app stores still decide on a native app. If a feature cannot run, we say so before we quote it.
See the builds