Here’s the honest version: most apps built by Sydney and Melbourne studios take somewhere between 10 and 24 weeks, from the first day of discovery through to App Store launch. Simple, focused apps sit at the lower end. Anything with multiple integrations, a custom backend, or compliance requirements pushes toward the upper end. Complex enterprise platforms can run well past that, 28 weeks or more.
The “3 to 9 months” you see thrown around in generic guides is technically true and practically useless. The real question isn’t “how long does app development take?”, it’s “how long will my specific project take, and what decisions push it toward the shorter or longer end of that range?”
We’ve built more than 50 apps out of our Sydney studio on Barangaroo Avenue and our Melbourne studio at 727 Collins Street, and this guide comes straight from that project history, not some global average pulled from markets with completely different team structures, rates, and approval cycles to Australia.
We’re also covering three things specific to 2026 that are reshaping Australian timelines right now: AI-assisted development compressing delivery windows, Privacy Act compliance adding governance time to certain builds, and App Store review cycles running to their own rhythm regardless of how efficiently you build. For the broader national framework on app development timelines across Australia, our general app development timeline guide covers the global context this article builds from.
Sydney and Melbourne App Development Timelines at a Glance
TIMELINE BY PROJECT TYPE:
| Project type | Total timeline | Discovery | Design | Development | QA + Launch |
|---|---|---|---|---|---|
| MVP — single platform | 10–14 weeks | 1–2 wks | 2–3 wks | 5–7 wks | 2–3 wks |
| MVP — cross-platform | 12–16 weeks | 1–2 wks | 2–4 wks | 6–8 wks | 2–3 wks |
| Mid-complexity app | 16–22 weeks | 2 wks | 3–5 wks | 8–12 wks | 3–4 wks |
| Full consumer app (dual platform) | 20–28 weeks | 2–3 wks | 4–6 wks | 10–16 wks | 4–5 wks |
| Enterprise platform | 24–36+ weeks | 3–4 wks | 5–8 wks | 14–20 wks | 5–8 wks |
| Healthcare / compliance-heavy | Add 2–4 weeks | Privacy Act scope | — | Compliance integration | Legal review |
| AI-integrated features | Add 2–6 weeks | ML scoping | — | Model integration + testing | Performance validation |
[Source: Software Co project data 2026 (50+ Sydney and Melbourne apps), cross-referenced with Designveloper June 2026 (3–9 months typical range) and SynapseWorldwide May 2026 (16–36 weeks for custom mobile apps]
The 6 Phases of App Development in Sydney and Melbourne, What Happens and How Long It Takes
Phase 1, Discovery (1–4 weeks, $5,000–$15,000)
What happens:It’s here that requirements are documented, user research is conducted, competitors are analysed, tech is selected, integrations are mapped, the fixed price estimate is put together. An accurate timeline is possible because of discovery.
Sydney and Melbourne context: A discovery phase typically lasts 1-2 weeks for MVP projects and 2-4 weeks for enterprise builds in Sydney and Melbourne. They run a “Inception” phase at 2-4 weeks at Rebelled in Sydney and our normal landing time for discovery is 1-2 weeks for budgets below $150,000. In compliance-centric environments, such as fintech and healthcare, it takes 2-3 weeks to sufficiently assess Privacy Act needs.
Timeline risk here: The place the timeline risk resides: NOT skipping or rushing discovery doesn’t shorten your project – it lengthens it. All such requirements that are not discovered here are scope variations that cost 3–5x more once they are discovered later in development.
2026 addition: Where your app employs automated decision making, scoping the Privacy Act APP 1.7 requirements takes 2-3 days off discovery.
Phase 2, UX/UI Design (2–6 weeks)
What happens:These include user journey mapping, wireframing, high fidelity Figma prototypes, design system development, and gaining sign-off from stakeholders – the contractual agreement that precedes the development process.
Sydney and Melbourne context: Melbourne has a more design first culture compared to Sydney, and more design rounds per unit of time as a general rule in studios. For most consumer-facing apps, 2-3 rounds of review with stakeholders will be required for both cities.
Timeline risk here: The greatest cause of delays in the design phase is the lack of feedback from the stakeholders. If a round isn’t answered a week of time passes. Establish SLA for response in your contract – 48 hours for internal review is reasonable.
AI in 2026: AI tools such as Figma AI and Adobe Firefly are reducing the time of experienced designers to do initial wireframing by 20-30%, although the impact on the stakeholder review cycle is secondary and the effect is more internal to the studio.
Phase 3, Development (5-20 weeks depending on scope)
What happens: This is agile sprint delivery, usually a 2 week sprint and a working demo at the end of each sprint. Concurrently, with a sufficient team size, frontend, backend API work and third-party integrations begin concurrently.
Sydney and Melbourne context: New functions are added, such as Face ID, a referral program, push notifications, each of which requires 2–3 sprints (Ptolemay 2025, quoting Sydney fintech founder Josh Howland). This is where features get added on—the sprint doesn’t just gain the additional feature’s development time, but also any planning time that was scheduled around it.
The impact of AI in 2026: Coding tools such as Cursor, GitHub Copilot and Claude Code are cutting down on mundane coding tasks by 20-30% (8ration, April 2026). On a clear scope with an AI team, the 16 weeks of development is feasible to shrink to 12-13 weeks. Any studio should be asked directly if they are leveraging AI coding support and how it contributes to their time estimates.
Integration time: each 3rd party API takes 1-2 weeks for integration and testing. All this is done independently of payment gateways (Stripe, Afterpay), health care data exchanges (FHIR), and CRM integrations (Salesforce, HubSpot).
Phase 4, QA and Testing (2–5 weeks)
What happens: This includes functional testing with various devices and OS versions, performance testing under set-up loads, security penetration testing (in the case of fintech and healthcare), accessible testing (WCAG – enterprise and government) and regression testing after bug fixes.
Sydney and Melbourne context: The typical QA cost of a development project is 20-25% of the overall development effort (Dotsquares Melbourne 2026). The worst blowouts happen in studios where QA is merely the final two weeks of the project, not something that’s active throughout the entire process. Testing at the beginning of the sprint cycle is better than testing later in the sprint cycle.
Testing across 50+ real devices: For consumer apps, which require comprehensive device coverage, physical testing to real iOS and Android devices takes 1-2 weeks, which cannot be replaced by emulator testing. As standard we test on 50+ real devices. Our software testing service covers functional testing, automated test suites, performance and load testing, OWASP security penetration testing, and WCAG accessibility compliance audits — available as a standalone engagement or embedded within the development project.
2026 addition for compliance-heavy apps: For compliance-focused applications, OWASP security penetration testing adds 1–2 weeks and $3,000-$12,000 to the QA phase, for the fintech and healthcare sectors. Compliance verification of the Privacy Act automated decision-making adds an additional 3–5 days.
Phase 5, App Store Submission and Review (1–3 weeks)
What happens: This includes preparing the metadata and screenshots, submitting to the App Store (for iOS) or Google Play Console (for Android), going through the process of the review, and dealing with rejections.
Sydney and Melbourne context: The review process generally takes 1-3 business days for new apps and 24 hours or less for updates (Apple Developer 2026). Most submissions are processed within 3 days of Google Play.
The timeline risk most founders miss: The worst case scenario of launching a site on Apple that you are not prepared for is that it will be submitted and rejected, which adds 5-10 days to the time frame, followed by a few more days to receive detailed feedback on the rejection, and then a few more days to make the necessary changes and re-submit. If you’re familiar with compliance, then there’s a much lower risk of rejection if you submit a studio that’s a compliance expert.
The Australian timezone advantage: Apple’s US review team processes Sydney and Melbourne submissions overnight AEST, meaning most Australian studios receive their review outcome within the next Australian business day after submission.
Phase 6, Launch and Post-Launch Stabilisation (2–4 weeks)
What happens: This includes production monitoring, crash reporting configuration, collecting user feedback, App Store rating management, and the first few bugs that only occur under real user traffic.
Often missed in timeline estimates: It’s the “boring buffer sprint”, as Ptolemay put it, the sprint following QA when most of the second Sydney founder’s life is dedicated to last-minute legal copy tweaks, App Store metadata revision, and problems with the production environment. Give it 2–4 weeks after the launch for it to settle down, then you can truly say that the app will be “done”.
Post-launch stabilisation is one of the most consistently underbudgeted phases in Australian app development. Our true cost of building an app guide covers post-launch costs, annual maintenance budgets, and the full 3-year cost of ownership model that most Australian app quotes exclude.
Real Timelines from Our Sydney and Melbourne Projects
1.CLINIC 1 — Healthcare Practice Management (Sydney)
Platforms: iOS + Android + Web
Coverage: 5000+ practitioners, all in one practice management.
Timeline breakdown:
- Discovery: 3 weeks – Privacy Act + FHIR compliance scoping
- Design: 5 weeks – clinical workflow UX + complex user types
- Development: 18 weeks – backend API + FHIR integration + Medicare claiming
- QA + OWASP security testing: 4 weeks
- App Store Submission: 2 weeks
- Total: 32 weeks
What made it stretch: a full 4 weeks on top of the normal backend development time due to the depth of healthcare compliance work, the integration of FHIR HL7, and the Medicare claiming API.
2.BIZCAP — AI Lending Platform (Sydney)
Platform: Web + Mobile
Product: Lending as a service powered by AI for Australian SMBs.
Timeline breakdown:
- Discovery: 2 weeks
- Design: 4 weeks
- Development: 16 weeks (AI decisioning, APRA-aware architecture)
- QA + security penetration testing: 3 weeks
- Launch: 1 week
- Total: 26 weeks
What extended it: APRA-aware architecture decisions plus testing of an AI decisioning model added 3-4 weeks on top of a typical fintech build.
Both Clinic 1 and BizCap were built from our Sydney studio. For the full picture of what Sydney app development involves beyond timelines — rates, studio selection, and what to expect from discovery — see our Sydney app developer guide.
3.Fieldr, Field Workforce Management (Melbourne)
Platform: iOS + Android (cross-platform)
Scope: Workforce management for 500+ field workers
Timeline breakdown:
- Discovery: 2 weeks
- Design: 3 weeks
- Development: 12 weeks (offline-first architecture, GPS tracking)
- QA + field device testing: 3 weeks
- Launch: 1 week
- Total: 21 weeks
What held it up: It was a cross-platform implementation with Flutter, which saved 4-5 weeks over dual native, and a client who had very clear operational needs.
4.ShopRun, Live Commerce Platform (Melb)
Platform: iOS + Android + Web (simultaneous)
Scope: Real-time livestream shopping
Timeline breakdown:
- Discovery: 2 weeks
- Design: 4 weeks (live commerce UX, novel interaction patterns)
- Development: 16 weeks (real-time video + purchase stack)
- QA + live event simulation testing: 3 weeks
- Launch: 2 weeks (simultaneous iOS + Android + Web store)
- Total: 27 weeks
What was long: The novel interaction patterns required three additional rounds of design iterations, and the syncing of real-time video to purchasing is a complex infrastructure lacking an off-the-shelf buy sync path.
5.Healthmate, Allied Health Platform (Melbourne)
Platform: iOS + Android (cross-platform)
Scope: Telehealth and practitioner matching
Timeline breakdown:
- Discovery: 2 weeks
- Design: 3 weeks
- Development: 10 weeks (cross-platform, API integrations)
- QA + compliance testing: 2 weeks
- Launch: 1 week
- Total: 18 weeks
What kept it tight: A clearly defined scope, going cross-platform, and already having allied health platform experience within the team, which greatly reduced the length of time to discovery integration.
Fieldr, Shoprun, and HealthMate were all built from our Melbourne studio at 727 Collins Street. For Melbourne-specific rates, studio selection criteria, and the R&D Tax Incentive that can reduce effective Melbourne build costs by up to 43.5%, see our Melbourne app developer guide.
The 8 Most Common Timeline Blowouts in Sydney and Melbourne App Development — and How to Prevent Each One
Risk 1. Scope creep — features added mid-build
As with Sydney fintech pioneer Josh Howland’s example from 2025, every addition of a “quick” feature comes at 2-3 sprints.
Prevention: Lock feature list before sprint one! A formal Change Order system, anything outside of the scope of the document must be in writing and have a timeline adjustment before being built.
Software Co’s product discovery and planning service covers all seven steps of our discovery process — from business requirements through to the fixed-price estimate — and what each step produces before development begins.
Risk 2. Slow stakeholder feedback
Slow feedback and unclear requirements during design review are always found to be one of the leading causes of blowouts (Upscalix, Feb 2026).
Prevention: Define written SLAs, 48 hours for design review, 72 hours for sprint demos and incorporate them into the contract.
Risk 3. Third-party API behaviour
Documentation for integration does not necessarily reflect reality. When the behaviour in the sandboxes is different to the actual production system, payment gateways, healthcare APIs, and CRM integrations are frequent sources of 1-2 weeks of unplanned work.
Prevention: when discovery, ask the studio to create a map, specifically, of each of their integrations and verify they have worked with all of them before. If you’ve previously used features from your specific APIs, the time to discover integration will get reduced.
Risk 4. Rejection from Apple’s App Store
If you are rejected, you will have to wait about 5-10 business days before getting it launched. Typical reasons for rejecting common 2026 forms are poor privacy disclosure (which is associated with compliance with Privacy Act), problems with the form’s design, and problems with the accuracy of the metadata.
Prevention: submit to a studio with experience in the field to ensure the suitability of the application; there is an increased likelihood of rejection for fintech apps and healthcare apps, so previous experience with Apple’s guidelines is a real asset.
Risk 5. Underestimated QA scope
A studio that offers two weeks’ worth of QA for a moderately sized app that has three integrations in place likely undercharges. In reality, functional and device, but also performance and integration testing for that kind of build will take 3–4 weeks.
Prevention: request that QA be broken down as a % of development effort in the quote – industry standard 20-25% (Dotsquares Melbourne 2026).
Risk 6. Australian public holidays
They’ve got what they call a four-month sprint plan to get it done, and the Melbourne Cup hit them, half the team was missing and then the QA backlog doubled,” said Sam Gale, co-founder of RentRoller in Brisbane.
Prevention: include Australian public holidays as a part of the delivery plan. Important dates to keep an eye on include Australia Day, Easter, Anzac Day, Christmas/New Year’s and the Queen’s Birthday (June in Victoria, October in NSW), and Melbourne Cup in November for Victoria. These will be included in a professionally organized delivery timeline.
Risk 7. Complying with Privacy Act 2026 identified during construction
When you’re using automated decision making and this is not scoped during discovery, the compliance work tends to come up midway into your app’s development, pushing 2-4 weeks and $3k-$10k in unplanned scope.
Prevention: specifically discuss the obligations to the APP 1.7 in December 2026 during discovery. The existence of this should be well known to any studio that is truly up to date with compliance in 2026.
Risk 8. Underestimate of complexity of AI features
“AI powered” can mean a couple weeks of API integration, or a project that involves training a custom model over a period of ten weeks.
Prevention: Get the studio to be more specific when you’re in the discovery phase about what kind of AI implementation they are talking about: an API integration (OpenAI/Anthropic) or a fine-tuned AI or a fully custom-trained AI. This can be 5x the number of years between them.
How 2026 Has Changed Australian App Development Timelines
FACTOR 1: AI-powered development is speeding up build times
AI-driven development is reducing build times. By 2026, most Sydney and Melbourne studios were using tools such as Cursor, GitHub Copilot, and Claude Code. The real-life impact: The three-day coding tasks now only take about two days. That can be squeezed down to 12-13 weeks with well-scoped builds (8ration, April 2026) for a 16-week development period.
FACTOR 2: AI Compresses Routine Coding — Not Integration or Compliance Work
That’s not exactly what the current AI coding tools achieve when it comes to integration tasks, architecture decisions, and compliance implementation. The compression is genuine but it’s only on probably 40% of a typical development stage, not the entire development timeline.
FACTOR 3: Norman can be delayed by another 2–4 weeks by the new Privacy Act 2026
The December 2026 Privacy Act changes add 2–4 weeks to affected builds. The ecosystem of automated decision making comes into effect from 10 December 2026 and will align with APP 1.7–1.9. This is an addition of 2-3 days for fintech, healthcare, and ecommerce apps. Developing the in-app disclosures takes 1-2 weeks longer. There is also a legal review of your new privacy policy that requires an engagement that typically begins about six weeks before the Dec. 10 deadline. If you are beginning a new build at this time, incorporate this into discovery. If you already have an app live, add that app to your next sprint the instant you’re able.
For the full breakdown of what the December 2026 Privacy Act changes add to your build budget by industry — and the 8-step action checklist before the deadline — see our Privacy Act 2026 app development guide.
FACTOR 4: Review in the App Store is quicker but less reliable
This is because the average review time for Apple in 2026 is 1-3 business days for first submissions compared to 3-7 business days back in 2022. However, privacy-based denials have increased, as Apple enforces data disclosure more strictly per new privacy laws, worldwide. Australian apps that are automated decision-making are more likely to be rejected if there is not a disclosure statement in the app metadata and app description.
5 Decisions That Shorten Your Timeline Without Cutting Corners
DECISION 1: Cross-platform (Flutter or React Native)
Building native on both iOS and Android requires 30-40% more time than building a single codebase for both. If it is 16–18 weeks cross-platform, then it is 24 weeks going dual native. Whereas React Native has a larger pool of Australian talent and a robust JavaScript ecosystem to support it, Flutter appear to be the better choice for fintech (pixel-perfect UI and real-time data). This one choice is more than any other you’ll make to shorten your timeline.
DECISION 2: Invest in discovery appropriately
Believe it or not, the total timeline is reduced by investing two weeks and $10,000 in discovery. All of the requirements that come up at discovery are requirements that are not going to come up as an ad hoc scope change later in the case, and scope changes are 3-5 times as time consuming as the initial discovery.
DECISION 3: Lock Your Feature List Before Sprint One Begins
In several Sydney and Melbourne projects having added features mid construction, they have all seen the timelines extended by 2-3 times what they would have taken if they had been planned within the original plan. Include a feature in week 12 of a 16-week build and you can expect to see 2–4 weeks added on to it, not a couple of days.
DECISION 4: Choose a studio that has experience with the integrations you’re interested in
An already integrated studio will learn the idiosyncrasies in days and not weeks. If there is one ‘time-bomb’ that is underutilised in any Australian buyer’s vocabulary, it’s previous experience with a particular API.
DECISION 5: Register developer accounts in the App Store as early as possible
Apple Developer Program and Google Play Console accounts require review and approval, it will take 1-3 business days for Apple. To start this during discovery, rather than putting it on the critical path at the end, removes it altogether.
How to Build Your Own Timeline: A Planning Framework
Step 1: Identify the type of project from the timeline table and record your baseline range.
Step 2: For each of the complexity factors that are applicable:
- Up to +2 weeks for every major 3rd party integration.
- +2-3 weeks for native builds, rather than cross-platform (or -4-5 weeks if you’re switching from native to cross-platform).
- +2-4 weeks for compliance scope (Privacy Act, APRA, ADHA)
- +2-6 weeks for AI/ML feature integration (depends on the specific feature)
To translate these timeline additions into budget implications, our Sydney app developer rate guide covers agency blended rates and project cost by type from our Barangaroo studio.
Step 3: Buffer with Australian specific:
- Step 1: Public holiday and stakeholder review delays are compensated for by adding +10 to +15%.
- Step 2: +2 weeks to submit to App Store and possible rejection the first time around.
- Step 3: Post launch stabilisation is +2–4 weeks.
- Step 4: Do your studios leverage AI development? If, yes, compress the development phase only (discovery, design, QA, submission are excluded).
- Step 5: Realistic total = baseline range + complexity additions + Australian buffer − AI compression (if applicable).
Example, a Melbourne healthtech MVP (cross-platform, two integrations, Privacy Act compliant, AI-assisted studio):
- Baseline: 12–16 weeks
- + 4 weeks (2 integrations × 2 weeks each)
- + 3 weeks (Privacy Act compliance scope)
- + 2 weeks (public holiday buffer + App Store)
- + 2 weeks (post-launch stabilisation)
- − 2 weeks (AI coding compression on dev phase)
- = 21–25 weeks total — realistic, planned, not a surprise
How Long Will Your App Actually Take? The Honest Summary
The range for most apps developing from a Sydney or Melbourne studio is from 10 to 28 weeks from the discovery phase to being launched on the App Store in 2026.By project type:
- MVP (single platform): 10–14 weeks
- MVP (cross-platform): 12–16 weeks
- Mid-complexity app: 16–22 weeks
- Full consumer app: 20–28 weeks
- Enterprise platform: 24–36+ weeks
- Compliance-heavy addition: +2–4 weeks
- AI feature addition: +2–6 weeks
The three decisions that make the biggest difference:
- Cross-platform vs native (4-6 weeks of saving)
- investing properly in discovery (3-8 weeks worth of mid-build variations are avoided)
- understanding what you are going to build before sprint one (2-4 weeks per feature added late).
And the following specifics for 2026: The build phase is shortened by 15-20% due to AI assistance, compliance to Privacy Act adds 2-4 weeks for affected apps, and if rejected by the App Store, it will cost you 5-10 business days to recover.
For a project-specific timeline estimate from our Sydney or Melbourne studios, contact our app development team directly. We will tell you where your project sits in these ranges and what the specific decisions are that will push it toward the shorter or longer end.
App Development Timeline Sydney and Melbourne, Frequently Asked Questions
Q1: How many days does it take to develop an app in Sydney or Melbourne?
The average time from start of discovery to appearing in the App Store in 2026 is 10-28 weeks for most apps. How long it takes to build an MVP varies depending on the complexity of the app and its integrations, but is generally 10–14 weeks for focused single-platform, 12–16 weeks for cross-platform, 16–22 weeks for mid-complexity apps with multiple integrations, and 20–28 weeks for full consumer app with backend for both iOS and Android. Compliance-based (fintech, healthcare) builds take 24–36+ weeks to complete, while Enterprise platforms and compliance-heavy builds (fintech, healthcare) run 24–36+ weeks. All figures are drawn from Software Co’s own project data from 50+ Sydney and Melbourne apps.
Q2: What is the breakdown of phases?
The Australian app development lifecycle runs through 6 phases: Discovery (1–4 weeks, covering requirements, tech selection, and fixed-price estimation); UX/UI Design (2–6 weeks); Development (5–20 weeks); QA and Testing (2–5 weeks); App Store Submission (1–3 weeks); and Post-Launch Stabilisation (2–4 weeks).
Q3: So, what are the biggest delays in the development of apps in Australia?
The biggest offenders: scope creep (each feature added during the build takes 2-3 sprints), slow stakeholder feedback on the design review (should be done in the design phase, not mid-build), unscoped complexity of third party API on the application (1-2 weeks per integration), Privacy Act compliance being identified mid-build rather than scoped prior to build, underestimated QA (should be 20-25% of the build time, not just 10%), and public holidays in Australia (Melbourne Cup week is well documented and creates a very real 2x QA build time.
Q4: Does cross-platform development make sense in Australia?
Yes, significantly. The time to build native separately for iOS and Android is 30-40% of the time of building a single codebase for both. Generally a project that runs 22 weeks going dual native runs 14-16 weeks going cross platform. Fintech and healthcare apps work best for Flutter (pixel-perfect UI, real-time data) and React Native (bigger Australian developer base). This is likely to be the biggest timeline lever for most Sydney/Melbourne builds.
Q5: What impact does AI-aided development have on timelines?
At most Sydney and Melbourne studios, they’re now using tools such as Cursor, GitHub Copilot, and Claude Code that cut routine coding work by 20–30%. With good scope, a 16 week development phase can be compressed to 12-13 weeks realistically. Current AI tools do not accelerate the majority of the most important tasks, such as routine coding, which accounts for around 40% of a typical development phase, integration work, architecture decisions and implementation of compliance. Any studio worth their salt would reply with a resounding yes and how much does that help contribute to their set price timelines?
Q6: How long does it take for Apple App Store to review Australian Apps?
In 2026, new submissions are processed within 1-3 business days, compared to 3-7 days during previous years, and updates are generally done in 24 hours. However, if rejected, it takes 5-10 business days (3-5 days for detailed feedback, 2-5 days for making the changes and resubmitting). Over the last few years, Apple’s review team in the United States has been processing submissions from Sydney and Melbourne studios over the course of a business day, so that those studios can typically have their submission reviewed overnight and receive a reply the following local business day. In 2026, rejections for privacy reasons have increased.
Q7: Will timelines be impacted by the December 2026 Privacy Act change?
Yes, if there is an automated decision-making capability in the application (e.g., credit scoring, health triage, product recommendations, dynamic pricing). The APP 1.7-1.9 compliance scope will add an extra 2-3 days to discovery and 1-2 weeks for building in-app disclosures, and will necessitate a separate legal review of your privacy policy, beginning around six weeks before the 10 December 2026 deadline. When developing new builds, include discovery in the initial sprint; when developing live applications, incorporate compliance work into the next sprint as soon as possible.
Q8: What was the actual time of Software Co’s real projects?
Sydney and Melbourne: build of our healthcare practice management (iOS + Android + Web) took 32 weeks, including FHIR compliance. It took 26 weeks to develop our AI fintech lending platform, which is APRA-approved. At 21 weeks, that cross-platform app was built using a Flutter field workforce app, and it was put together snugly thanks to the platform choice. A simultaneous release of a live commerce platform on iOS, Android and Web took 27 weeks. An allied health platform was also cross-platform, but was built in just 18 weeks, due to a clear scope and a team that had experience building in that space. These are actual projects that have been completed, not estimates.