$ what we ship

Six types of app build.

Pick the shape that matches your problem — from a lean MVP for validation to a multi-tenant SaaS with billing, roles and audit trails. Every build is production-hardened before it ships.

01

Custom web applicationsSaaS platforms, marketplaces, internal portals, member sites — auth, billing, roles, audit logs baked in.

02

Internal tools & dashboardsAdmin panels, ops tools, data dashboards. Real-time updates, exports, permission tiers, single-sign-on.

03

Membership & content portalsLogin, content gating, subscription billing (Stripe), tiered access, drip content, self-serve account.

04

iOS & Android mobile appsReact Native or native Swift/Kotlin. Push notifications, deep links, offline mode, App Store & Play Store submission included.

05

Booking & schedulingAvailability engines, calendar sync (Google/Outlook), payments, reminders, cancellations, no-show handling.

06

Mobile-first PWAsProgressive web apps that install like native, work offline, and cost half of a mobile+web pair.

$ our process

From MVP to launch — six phases, every time.

Every engagement runs the same six phases, in the same order. Fixed scope, fixed timeline, fixed price — agreed in writing before we start writing code.

01

Discovery & scoping
Week 1

We start with a paid discovery sprint — the version of your idea we can actually build. Stakeholder interviews, competitor scan, feature-vs-timeline trade-offs, and honest opinions on what to cut.
- 2–4 hour kickoff workshop (in Brisbane or over video)
- Feature inventory + MoSCoW prioritisation
- Tech-stack recommendation + hosting shape
- Fixed-price proposal with week-by-week milestones
02

UX & design
Week 2 – 3

User flows, wireframes, hi-fi Figma mockups, and a clickable prototype you can hand to stakeholders. We design against real content and real user stories — no lorem ipsum.
- User personas & journey maps
- Wireframes for every screen (desktop + mobile)
- Hi-fidelity Figma design system + component library
- Interactive Figma prototype for stakeholder sign-off
03

Foundations & auth
Week 3 – 4

Repo, CI, staging, auth, database schema, base component library — everything shipped before any feature work starts. Fixing foundations later is 10× more expensive.
- GitHub repo with branch protection + CI checks
- Staging URL live from day one
- Auth (Clerk / Auth0 / custom) + role model
- Postgres schema + migrations, seeded test data
04

Feature sprints
Week 4 – 12

Two-week sprints. Every Friday you get a demo on the staging URL — clickable, real data, no PowerPoint. Slack channel for real-time questions.
- Weekly Friday demo call (30 min, recorded)
- Linear board you can see and comment on
- Daily deploys to staging, monitored automatically
- End-of-sprint retro + next-sprint plan
05

Hardening & QA
Week 12 – 14

Performance profiling, security review, accessibility (WCAG 2.2 AA), load testing, cross-device QA, penetration scan, dependency audit. If it's fragile, we find it before your users do.
- Lighthouse ≥ 95 across performance, a11y, best-practices, SEO
- Automated E2E tests (Playwright) for critical flows
- OWASP Top-10 review + dependency vuln scan
- Real-device QA on iOS + Android + top 5 browsers
06

Launch & 90-day support
Week 14 → 26

Production deploy, App Store & Play Store submission (if mobile), monitoring dashboards, on-call for the first 90 days. Bugs, tweaks, questions — all included.
- Zero-downtime production release
- App Store & Play Store submission handled end-to-end
- Uptime + error monitoring (Sentry, UptimeRobot) wired in
- 90 days of bug fixes & tweaks — no ticket queues

$ what you own

What lands in your hands.

On final payment, every artefact below transfers to your name. Source, accounts, credentials, keys — no vendor lock-in, ever.

Full source repo

GitHub repo transferred to your org. Every commit, every branch, every review — yours.

Figma design files

Design system, component library, prototypes — editable, not screenshots.

Hosting & DNS accounts

AWS / Vercel / Cloudflare accounts registered in your name from day one.

App Store listings

Apple Developer + Google Play accounts under your business, screenshots, copy.

Architecture docs

Runbook, database schema, API docs, deployment guide — written like your next dev is reading them.

Monitoring dashboards

Sentry, UptimeRobot, GA4 — configured, alerting to your inbox before the first user pings.

$ tech stack

The stack we reach for.

Boring on purpose. Every tool here is battle-tested, actively maintained, and hire-able for anywhere in Brisbane, Sydney, Melbourne, Auckland or Wellington if you want to bring it in-house later.

Frontend

React
Next.js
TypeScript
Tailwind
React Native

Backend

Node.js
Python
Fastify
tRPC
GraphQL

Data

Postgres
Redis
Prisma
Supabase

Auth & payments

Clerk
Auth0
Stripe
Paddle

Hosting

Vercel
AWS
Cloudflare
Fly.io

Observability

Sentry
PostHog
Datadog
GA4

$ timeline & investment

Rough shape of a web-app engagement.

Real numbers from the last twelve web-app builds. Actual pricing lands after discovery — but this is the sensible band to plan around.

Typical timeline

0–0 weeks

MVP web app: 8–10 weeks. SaaS with billing + roles: 12–16 weeks. Mobile app add-on: +4 weeks.

Investment (AUD)

$0k – $0k

Fixed price. Broken into three milestone payments — no all-in-advance. Care plan from $250/mo after launch.

0

Apps shipped in 2025

0%

On-time launches

0%

Uptime SLA

0 min

Avg first reply

$ questions

The stuff every client asks first.

If your question isn't below, we'll answer it on the discovery call. No sales pitch — just an honest read on whether we're the right shop.

What's the smallest web app you'll build?

A validated MVP with auth, one core flow, one payment integration, and a marketing landing — typically 6–8 weeks and around AUD $18–25k. If your idea's smaller than that, we'll usually tell you to skip us and build it on Webflow or Bubble first.

Do you build native iOS/Android or React Native?

React Native by default — it's 60% cheaper and covers 95% of what most apps need. We reach for native Swift or Kotlin when there's a real reason: heavy on-device ML, ARKit, high-end graphics, or specific SDK constraints.

Who owns the code?

You do. On final milestone payment we transfer the GitHub org, all deployment accounts (AWS/Vercel/etc.), the Apple Developer and Google Play accounts, the Figma files — everything. No vendor lock-in, ever.

Do you take over apps someone else started?

Often, yes. We run a paid 2–4 hour audit — codebase health, tech-debt inventory, security posture — and quote the continuation honestly. If it's not worth rescuing, we say so and quote a rebuild.

How do payments work?

Three milestone payments — 30% at kickoff, 40% at the design + foundations gate, 30% at launch. No all-in-advance. All fixed price, no billable hours, no surprise variations.

What if my requirements change mid-build?

Small changes (a copy tweak, a colour, a field) — included, no drama. Anything that shifts scope by more than half a sprint gets its own change order, priced fixed, before we do the work. You always know what the next invoice looks like.

Do you work outside Brisbane?

Yes — every engagement runs remote-first from our Brisbane studio, with on-site availability across Sydney, Melbourne, Perth, Adelaide, Gold Coast, Auckland and Wellington. About half our clients we've never met in person; the other half we visit for kickoff and launch.

Apps that scale with you.