Process
Clear steps. No surprises.
You always know what’s happening, what’s next, and what it costs. Here’s how a project runs, from the first message to the updates after launch.
-
Tell us about it
Send a project request. A few honest lines about the idea and the people it is for is plenty.
Every request is read by a person, not a form robot, and you get a reply by email with first thoughts and the questions we’d need answered.
-
A conversation
We talk through goals, users and must-haves, and agree what belongs in version one and what can wait.
A video call, usually under an hour. You leave with a clearer picture of the product even if we don’t work together.
-
A clear proposal
Scope, timeline and quote in writing, so you know exactly what you are getting before any work starts.
Milestones you can check against, and what’s deliberately left for later, so there are no surprises.
-
Design, then build
Designs first, then working builds on your own phone as we go, so you watch the app take shape.
Regular test builds and short updates. You can try every feature as it lands and change course early, when it’s cheap.
-
Launch, and after
Store submission and review, launch day, then fixes, updates and new features as your users ask for them.
We handle the store paperwork and stay on for support, so launch is the start of the product rather than the end of the project.
Questions
Good to know.
What kinds of projects do you take on?
Three kinds: building new apps, games and websites; improving software you already have with new features, redesigns, performance work and store fixes; and helping teams ship better through CI/CD, testing, release automation, audits and advice.
Can you work on an app someone else built?
Yes. We start by reading the code and getting it building, then agree a plan with you. Most work happens in your existing codebase and conventions; rewrites are a last resort, not a default.
Do you only build for Apple platforms?
No. Native Apple apps are a specialty, but we also build for Android and the web, and pick the approach that fits your product and budget rather than the one we happen to prefer.
Who owns the code?
You do. When the project is paid for, the source code, designs and store listings are yours, with a handover so another developer could pick them up.
How is a project priced?
From the agreed scope in the written proposal, split into milestones. Smaller jobs, audits and ongoing support can be quoted separately, or as a set number of days.
Can you set up CI/CD for our team?
Yes. We’ll look at how you build, test and release today, then set up a pipeline that suits your team, whether that’s Xcode Cloud, GitHub Actions or something you already use, and document it so your team owns it.
Can you work with my designer or team?
Yes. We can build from existing designs, work alongside your developers, or own the whole thing end to end.
Ready for step one?
Tell us about your project. It takes a few minutes, and we’ll take it from there.
Start a project