Frequently Asked Questions

Develune is a full-stack software development company. We take products the whole way — discovery and design, front-end and back-end engineering, mobile, cloud and DevOps, data, AI features, and the automated testing that keeps releases safe. Clients come to us when they want one team accountable for the outcome rather than a build handed between specialists.

Headquartered in Marsden Park, New South Wales, Australia, with additional offices in Brampton, Ontario (Canada) and London (UK). The team works remote-first across time zones, and engagements run for clients worldwide regardless of office location.

Develune was founded in 2022, growing out of contract engineering work that started in 2020. Since then the team has shipped 63+ products across 13+ industries, expanding from testing and quality assurance into full-stack delivery and, more recently, production AI engineering.

Nine services: custom software development, web and frontend engineering, backend and API engineering, QA and test automation, AI and automation engineering, product strategy and UX/UI design, mobile app development, cloud, DevOps and infrastructure, and data engineering and analytics. We also run maintenance and support retainers, including rescue work on codebases we did not originally build.

It depends entirely on your requirements, and we would rather tell you that honestly than publish something that fits nobody. A small integration and a multi-team platform are not the same job. So we start by understanding what you actually need, then agree everything in writing before any work starts. Send us a short brief and we will come back with a recommended way to work together, usually within one business day, with no obligation.

We do not bill by the hour. Discovery is a fixed fee, builds are billed against agreed milestones, and ongoing work is a monthly retainer for a defined capacity. Anything outside the agreed scope is discussed and approved before work starts, so nothing appears on an invoice that you have not already agreed to.

The same three things, in the same order: the problem we were handed, what we designed and built to solve it, and the measured impact once it was live. Where a number is claimed it is one we can stand behind — test coverage, regression time, time to launch — not a rounded-up percentage. Each study also names the stack, our role on the engagement, and what we would tell the next team inheriting it.

Not every engagement is ours to publish in full. Some were one part of a larger programme where the outcome was not ours alone to claim, and some are still in build — which the card says plainly rather than letting an unfinished project borrow the credibility of a shipped one. Where there is no case study, the card states the work we actually did and stops there.

You do, from day one. The code, the data, the infrastructure, the designs, and the documentation are yours — including the right to take them to another team. Every engagement ends with a documented handover so your system can be operated and extended without us.

SaaS and startups, healthcare and life sciences, government and public sector, insurtech and financial services, edtech and compliance training, e-commerce and retail, martech and hospitality, logistics and field operations, and nonprofit and community organizations. We deliver for clients across several regions and time zones, and each sector here is grounded in delivered work rather than a list we would like to serve.

No. Sector experience helps — it means we already know the constraints, the integrations, and the failure modes before we start — but engineering discipline travels. The sectors we list are the ones we can evidence with delivered work, and we would rather show you that than claim coverage we cannot back up. If yours is not listed, tell us what you are building and we will say plainly whether we are the right team.

It changes the constraints, not the craft. A patient-facing tool has accessibility and audit requirements a marketing site does not; a government service has procurement and record-keeping obligations; an insurance claims portal has to be able to explain its own decisions. Those constraints shape the architecture, the test coverage, and what we consider done — which is why every sector page names them rather than listing logos.

TypeScript, React, and Next.js on the front end; Node.js, Ruby on Rails, Python, PostgreSQL, and GraphQL on the back end; React Native and Flutter for mobile; AWS, Google Cloud, Vercel, Docker, and Terraform for infrastructure; Cypress, Playwright, Selenium, and Cucumber for testing; and Claude, Gemini, and the Model Context Protocol for AI work. We choose the stack that fits the product rather than defending a favourite.

Yes, and it is a regular part of our work. We start with a codebase audit covering architecture, dependency risk, security exposure, and test coverage, then give you an honest assessment of what is salvageable and what is not. We modernize incrementally wherever possible and only recommend a rewrite when we can show the reasoning.

The careers page lists a role only when one is genuinely open, and says so plainly when none is. When we need someone, the role goes up there with what the work involves and how to apply. Until one is listed there is nothing to apply for, so the page itself is the thing to check.

Three stages once a role is open: an application with your CV or profile, a thirty-minute intro call, and a technical conversation about work you have actually done. Then a decision. No whiteboard puzzles and no panel round.

Yes — remote-first, across time zones, with clients in several regions. That is why we hire for precise written communication and for people who own outcomes rather than wait to be assigned tickets.

Two things. We build AI features into client products — LLM applications, retrieval systems, document processing, and agents — with evaluation suites, guardrails, cost ceilings, and human review on anything consequential. We also use AI tooling internally to move faster, with an engineer reviewing every change before it ships. Our team holds Anthropic certifications in Claude Code, the Model Context Protocol, and Agent Skills.

A Discovery Sprint can usually begin within one to two weeks of an agreed scope. Larger builds and dedicated-team engagements depend on current capacity, which we will tell you honestly on the first call rather than promising a date we cannot hold.

Send a short note through the contact page describing what you are building and what is in your way. We will reply with suggested next steps and a recommended way to work together — usually within one business day. The first conversation is 30 minutes and there is no pitch attached to it.

Two ways, both reaching the same team: the contact form on this site, or email at hello@develune.com. Either suits a first brief best, because you can attach a specification, a repository link or a design file. We reply to every enquiry, usually within one business day.