How it works

A process designed for companies, not freelancers

From the first call to ongoing delivery — every step is designed to be predictable, low-friction, and accountable.

From first call to first sprint in under 2 weeks

Discovery call — 30 minutes

We start with a structured 30-minute call. We ask about your app, your team, your timeline, and what's not working. We don't pitch — we listen. By the end of the call, we both know whether AppTeky is the right fit. If we're not, we'll tell you that too.

What to bring: a brief description of the app, what platform it runs on, and what you're trying to accomplish in the next 3 months.

Proposal and scope — within 48 hours

We send a clear written proposal: what we'll build or maintain, how we'll work together, what's in and out of scope, and what it costs. No hourly estimates. No vague "starting from" ranges with asterisks. A number, a scope, and a process.

You review it, ask questions, and either proceed or don't. No pressure, no follow-up calls unless you want them.

Onboarding — 2 to 3 days

Once the agreement is signed and the first payment is received, we onboard. We join your Slack workspace, get access to your GitHub repository, connect to your project management tool (Jira, Linear, Notion — whatever you use), and set up our sprint board.

We spend the first 1–2 days reading the codebase before writing a single line. We want to understand what already exists before changing anything.

Sprint 1 begins — within 5 working days of signing

Sprint 1 is a 2-week sprint. We start with a planning call to align on the highest-priority items, create tasks, and assign estimates. Then we ship. Every sprint ends with a review — you see what was built, give feedback, and we plan the next sprint.

We communicate asynchronously in Slack throughout the sprint. Nothing disappears into a black box for two weeks.

Ongoing delivery

After Sprint 1, the rhythm continues. Fortnightly sprints, fortnightly reviews, monthly summary reports. You always know what was done, what's coming next, and what the current state of the app is.

As the relationship matures, sprints get faster because we know the codebase and your product deeply. There is no re-onboarding cost every time you need something done.

We work in your tools

No new software to buy. We join the systems you already use.

Slack GitHub Jira Linear Notion Google Meet WhatsApp Figma / your design tool

Everything belongs to you

Code, accounts, infrastructure — it's all in your name. Always.

GitHub Repository

Code lives in your account. We push to your repo, not ours.

Firebase Project

Your Firebase console, your billing, your data. We work as contributors.

App Store Accounts

Google Play and App Store developer accounts stay in your name.

Source Code

Full source ownership from day one. No lock-in, no hostage code.

Common questions

You can cancel with 30 days written notice after the minimum engagement period. We hand over all code, documentation, and access credentials. Nothing is held hostage.

Yes. We sign an NDA before any codebase or business information is shared. Standard NDA is mutual.

We address concerns immediately. If a sprint didn't meet expectations, we discuss it in the sprint review and adjust. If issues persist after good-faith resolution attempts, you can exit with 30 days notice.

Yes. If you need more sprint capacity — a release crunch, a new feature push — we can discuss increasing the retainer scope for that month. This is agreed in advance, not billed as surprise overtime.

Our primary expertise is Flutter. If you have a React Native, native Android, or native iOS app, we can discuss migration to Flutter or limited maintenance work — but our best output is on Flutter projects.

Retainers are billed monthly in advance. Fixed-scope builds are split: 50% upfront, 25% at mid-milestone, 25% on delivery. All prices are exclusive of GST.

Ready to start?

Book a 30-minute discovery call. No commitment required on either side.