Donnish
Get in touch
§ 01Services / Build / Custom software

From idea to App Store. We've done it all.

You've got an idea, a set of features, a design refresh, or a team that needs ramp-up capacity to take a product to market. We've helped customers from concept through detailed design, technical architecture, build, release, product roadmap, and ongoing support.

Three engagement models, one senior team. Pick the shape that fits how you work.

Get in touchWe'll get back to you within a business day, usually faster.
See how we work↓
§Team augmentation

Senior developers, embedded in your team.

Team augmentation is the fastest way to add senior engineering capacity. We match a developer, or a small team, to what you need. They join your standups, your Slack and your sprint cadence, and own features end to end. No handlers, no middle-management layer.

  • Senior React, React Native, Flutter and .NET developers. Not juniors learning on your budget.
  • Onshore and offshore: Australia's East Coast and Manila, working AEST hours with an 80%+ overlap.
  • Direct Slack access to the people writing the code. The person you talk to is the person shipping.
  • Start in days, not months. Three-month minimum, then month to month. Most clients stay years.
The stacks we embed in
React NativeReactJSFlutter
Talk to us about team augmentation
The proof it works
  • drtalk

    Six years as the engineering team behind a US healthcare platform. A 2024 Good Design Award winner, built to healthcare-grade security standards.

  • STARTTS

    CAMLAP, a Flutter assessment platform for the NSW service for torture and trauma survivors. WCAG AA, 120+ languages.

  • Lite n’ Easy

    Embedded React and .NET developers on Australia's largest meal-delivery platform. Thousands of orders a day.

§ 02Why we work this way

We believe in process, not the puff.

Most clients have a clear vision of what they want to build, and we have the experience to get them there. Our strength is a lean approach, clear roles, and a hybrid team across Australia's East Coast and Manila. Engineers working AEST hours, attending your standups, owning features end to end.

When you want to take the reins, that is fine too. Our team has worked with Australian and US clients and become one of your team. No handlers. No middle-management layer.

We focus on fundamentals: can the scope of the work be measured, can we measure progress, are the delivery team and senior stakeholders aligned on resolving issues as they arise. Nobody wins medals for the best Scrum process. We all win when a project is delivered into the hands of users.

§ 03How we engage

Three ways to engage.

Pick the shape of engagement that fits how you work. The team underneath is the same: senior, ring-fenced, working your hours.

Team augmentation

We add the right person to your team.

Increase capacity by adding individual roles: a BA, a QA, a senior React developer, an offshore React Native developer. We try to understand what you need and match it to the right person on our team. The person works as part of your team. They put your cap and t-shirt on. No middle management from us. They are fully immersed.

Who it's forSoftware delivery managers and CIOs who need additional capacity quickly.

Currently delivering with
Lite n’ Easy
Co-delivery

We bring a partial team to complete yours.

Adding key roles to complete a project team. You may have a product owner and a BA, but need a development team around them. We provide the additional people. Depending on the role, we may manage the project on your behalf. Note: we do not ever provide the product owner role. That should be someone on your team. We can provide a proxy such as a BA.

Who it's forProgramme managers and CIOs running projects that need additional engineering capacity, design, and QA.

Currently delivering with
STARTTS
Project

We deliver the whole thing.

You know what you want to do and need a team to do it. Classic product delivery, end to end. You are the stakeholder and we deliver to you with our team. Often involves an initial Discovery, then a Design Sprint or Sprint 0 so the full sizing of the project can be done and everyone has a clearer understanding of the team shape and size for the remaining design and development.

Who it's forFounders, CTOs and product leaders with a clear vision and budget to take an idea to market.

Currently delivering with
drtalk
§ 04The stack

The stack we use, every engagement.

Battle-hardened on real client products. Picked because it ships, not because it is the latest thing.

Mobile
  • React Native (Expo)
  • Flutter
Web
  • ReactJS (Node)
  • Next.js
Backend
  • .NET on Azure
  • .NET on AWS
  • C# integration services
Cloud + ops
  • Azure
  • AWS
  • Cosmos DB
  • SignalR
Tooling
  • Jira
  • Confluence
  • Slack
  • Figma
  • Claude Code with VS Code

Our offshore engineers stand out because they work an 80%+ AEST timezone overlap, work directly with the customer team (no handlers), and have shipped pixel-perfect designs in production with Australian and US clients across financial services, health, government and more.

§ 05How we run a project

How we run a project.

Dual-track Agile (Scrum or Kanban). Lean. Pragmatic. The hardest problem first, then expand outward.

  1. 01

    Discovery

    We map the problem space with you. Users, business goals, constraints, technical landscape. The output is a shared understanding of what we are building and why.

  2. 02

    Design

    Designers and engineers work alongside each other. We crack the hardest critical designs first so the development team can start. We do not wait for every flow to be designed before writing code.

  3. 03

    Sprint 0

    Foundations. Repository, CI, observability, deployment pipeline. Architecture decisions documented. The team is set up so that Sprint 1 ships working software.

  4. 04

    Sprints

    Working software at the end of every sprint. Daily standups. Sprint reviews with stakeholders. Risks raised early and managed openly. We do not try to remove all risk. We try to identify it early.

§ 06Pre-engagement questions

Things people ask first.

  1. Where is your team located?

    Australia (Brisbane) and the Philippines (Manila). Engineers in Manila work an 80%+ overlap with AEST business hours. They attend your standups, work directly with your team, and have shipped products with Australian and US clients. No handlers between you and them.

  2. Will the offshore engineers work with my team directly?

    Yes. They join your standups, work in your Slack, push to your repo, and own features end to end. No middle management from us.

  3. Can we hire your engineers full-time?

    Talk to us. The default is a service engagement, but we have helped clients transition embedded contributors into permanent roles where it made sense for both sides.

  4. What is the minimum engagement?

    We typically work in 3-month minimums to give engineers time to ramp on your codebase and start delivering value. Shorter engagements are possible for advisory or short discovery work. Talk to us.

  5. Do you provide product owners or business stakeholders?

    No. Product ownership stays with you. We can provide a BA who proxies for the product owner in delivery ceremonies, but the strategic product decisions are yours.

  6. What if you're not the right fit?

    We will tell you. The 30-minute discovery call is for both sides to figure that out. If we are not a good fit we will say so. We are not in the business of selling engagements that should not happen.

Brisbane / Manila · Aussie hours

Got something to ship?

Tell us what you are building and we will tell you whether we are the right team. We will get back to you within a business day, usually faster.

Get in touchSee our case studies→ /case-studiesRun it with our managed service→ /services/mobile-app-maintenance