Project Management · Dunedin

Asana will hold your Dunedin site programme and cannot hold retention money on trust or a payment schedule due in twenty working days

Project Management Software workflow illustration for Dunedin, OTA, New Zealand.
The short answer

Custom project management software for a Dunedin construction, engineering, or professional services firm runs NZ$55,000 to NZ$160,000 over 4 to 8 months. Asana, Monday, Jira, and ClickUp are all competent task trackers, and none of them understand a payment claim, a payment schedule with a statutory response window, a variation that changes the contract sum, or retention money that must be held on trust. Those four things are where construction money is actually won and lost in New Zealand.

The programme is in one tool, the variations are in an email folder, the payment claims are in a spreadsheet, and the retentions are a number your accountant maintains separately. Your project manager knows where everything is, which is fine until two projects run at once and a subcontractor disputes a variation from four months ago. The evidence exists. It is just distributed across three systems and a phone.

The generic tools cannot fix this because their object model is a task. A payment claim is not a task; it is a dated instrument that triggers an obligation to respond within a fixed number of working days, and failing to respond properly has consequences that no amount of project tracking will soften. Retention money held on trust is not a project field either, it is a separate obligation with its own record-keeping requirements. Building around Asana means building the important half yourself anyway.

The problems nobody warns you about

  • Payment claims and the working-day clock to respond are tracked in a spreadsheet outside the project tool
  • Variations live in email, so the contract sum on the system and the contract sum in reality drift apart
  • Retention money is maintained separately by finance, which makes the trust obligation hard to evidence quickly
  • Subcontractor documents such as insurances and certifications expire without anyone noticing until an audit

The case for owning your project management

Build when your project data has legal consequences. A Dunedin build treats the payment claim as a first-class object with its own response deadline and status, keeps variations against the contract so the sum is always current, tracks retention money with the record-keeping the trust obligation requires, holds subcontractor compliance documents with expiry alerts, and links health and safety records to the site rather than to a filing cabinet. The programme and the tasks still matter, they are just no longer the hardest part of the system.

Budgeting a project management build in Dunedin

Project scopeTypical costTimeline
Payment claims, variations, and retention trackingNZ$55,000 to NZ$88,0004 to 5 months
Full platform with subcontractor portal and site recordsNZ$120,000 to NZ$160,0006 to 8 months
Contract and claims layer over existing Asana or JiraNZ$30,000 to NZ$56,0002 to 4 months
Cost by project scopeCost by project scopePayment claims, variations, and retention tracking$55k to $88kFull platform with subcontractor portal and site records$120k to $160kContract and claims layer over existing Asana or Jira$30k to $56k
Typical project cost bands. Source: Digital Heroes 2026 delivery benchmarks.

What your build should include

What to build in
+Payment claim and payment schedule tracking with working-day deadline counting and alerts
+Variation register linked to the contract sum with approval workflow and full history
+Retention money tracking with the record keeping the trust obligation requires
+Subcontractor compliance register covering insurance, certification, and expiry alerts
+Site diary, health and safety records, and inductions linked to the project and the site
+Programme and progress claims reconciled so the value claimed matches the work recorded

Dunedin project management: the full scope

Digital Heroes builds the full project management stack for Dunedin teams. Typical engagements cover time tracking, team collaboration software, workflow management, custom project management software, task management, Gantt charts and resource scheduling.

Exactly what you get

A system that treats contract obligations as seriously as the programme. Concretely: payment claims and schedules with working-day deadline counting, a variation register that keeps the contract sum current, retention tracking with a proper evidence trail, a subcontractor compliance register with expiry alerts, site diary and health and safety records tied to the project, and progress claims reconciled against recorded work. You own the code and the data. It connects to accounting software so claims and retentions reach your ledger cleanly, field service management software when defect and remedial work starts, and business intelligence (BI) dashboards for portfolio margin across concurrent Dunedin projects.

How to choose a developer in Dunedin

Ask a candidate to explain, without notes, what happens if a payment schedule is not issued in time. If they cannot, they will build you a task tracker with construction words on it. Ask for a construction or engineering reference and ring the quantity surveyor rather than the director, because the quantity surveyor will tell you whether the claims module actually works. Ask how they will get subcontractors onto the portal, since adoption by small trade businesses is the hardest part of the rollout. And insist on a heavy testing budget for anything that counts days.

Red flags when hiring (and what to ask instead)
  • !They describe a payment claim as a task type; ask them to explain the response obligation in their own words
  • !Retentions are not mentioned; ask how the trust obligation is evidenced in their design
  • !No subcontractor onboarding plan; ask how a two-person Dunedin trade business gets into the portal
  • !They have only built for professional services; ask for a construction reference and ring it
  • !Testing is budgeted lightly; ask how a deadline calculation error would be caught before it costs you
Ready to price this for your Dunedin team?
A 30-minute call gets you a named team, fixed scope and a real quote within 48 hours.
Talk to Digital Heroes

If project management is on the roadmap, field service management, booking & scheduling, mobile app usually follow within the year. Budget them as one conversation. Weighing options across the region? We publish the same project management guide for Queenstown. Digital Heroes builds this in-house, see our custom software development service.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
  2. The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
  3. Per Sensor Tower's State of Mobile 2026, worldwide consumers spent about $85 billion on apps in 2025 (up 21% YoY), and for the first time non-game apps surpassed games in consumer spending; generative-AI in-app purchase revenue more than tripled to top $5 billion. Source: Sensor Tower (via TechCrunch) (2026) →
  4. 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Rohan K. · Director of Web Platform Engineering · Delhi

Rohan directs web platform engineering at Digital Heroes, the group that builds the custom web applications, portals and internal tools behind client operations. He writes about how those systems are structured, where they usually break under load, and what makes one maintainable years later.

View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

What does custom project software cost for a Dunedin construction firm?

Payment claims, variations, and retention tracking runs NZ$55,000 to NZ$88,000 over 4 to 5 months. A full platform with a subcontractor portal and site records is NZ$120,000 to NZ$160,000 over 6 to 8 months. A contract and claims layer over the Asana or Jira you already use costs NZ$30,000 to NZ$56,000.

Can the system track payment claim response deadlines automatically?

Yes, and it should count in working days with public holidays and the Otago anniversary date built into the calendar. Alerts escalate before the deadline rather than reporting after it. Have your legal adviser confirm the exact calculation rules for your contract forms before this is coded, because the details vary.

How does it handle retention money held on trust?

Retentions are tracked as a separate obligation with their own ledger and evidence trail, showing what is held, for whom, and on what project. That makes the trust position something you can produce on request rather than reconstruct. Involve your accountant in the design so the treatment matches how it is recorded in your books.

Will our subcontractors actually use a portal?

Only if it takes them under five minutes and works on a phone in a ute. Keep the portal to submitting claims, uploading insurance certificates, and acknowledging variations, and resist adding anything else. Budget for someone to personally onboard your top twenty subcontractors, because that human effort determines whether the portal succeeds.

Should we replace Asana or keep it for tasks?

Many Dunedin firms keep the task tool their site teams already use and build the contract layer alongside it, integrated so progress and claims stay aligned. Replacing a tool people actually use in order to add contract features is a fight you do not need. Ask your developer to price both approaches.

How does this connect to our accounting system?

Approved claims, variations, and retention movements post into Xero or your ledger as structured transactions rather than being rekeyed. The project system stays the source of truth for contract position while accounting holds the financial position. Agree the posting rules with your accountant during design.

How long does it take to roll out across live projects?

Four to eight months to build, then bring projects on as they start rather than migrating live ones mid-stream. Moving a project that is halfway through its claim cycle creates exactly the ambiguity the system exists to prevent. Run the old process alongside for one full claim cycle on the first project.

What happens when construction legislation changes?

You fund the change, which is the honest cost of owning custom software in a regulated area. Keep a maintenance agreement that explicitly covers legislative updates so it is budgeted rather than negotiated under time pressure. Ask how your developer stays aware of changes, and do not rely solely on them for that.

Can we hire developers in Dunedin to support this long term?

Yes for general maintenance, and the city's low turnover helps with a system that carries this much institutional knowledge. What matters more is documentation of the deadline and retention logic, since that is where a new developer could do real damage. Insist the rules are documented in plain language alongside the code.

How much does it cost to build a custom project management tool for my company?
A focused build that replaces one painful workflow runs $60,000 to $90,000, and a full platform with portfolio views, client access, and integrations runs $120,000 to $200,000 or more. Those are Digital Heroes delivery bands across 2,000+ projects, not list prices. Add 15 to 20 percent of the build cost per year for hosting, maintenance, and integration upkeep.
What should the first version of a custom project management tool include, and what should wait?
Version one is the painful workflow plus the basics: tasks, projects, permissions, and one integration, shippable in 12 to 16 weeks. Everything that feels essential but is not should wait: Gantt views, custom report builders, native mobile apps, and public API access all belong in version two, once real usage shows what matters. Teams that run the MVP for a quarter before expanding consistently spend less and drop features that looked critical on paper.
How involved does my team need to be during a custom software build?
Plan on one product owner from your side spending 3 to 5 hours a week reviewing sprint demos, answering workflow questions, and testing before releases. Digital Heroes builds run discovery for 2 to 3 weeks, then two-week sprints with a clickable demo at the end of each. If your team is in Dunedin, a one or two day on-site discovery workshop at the start is worth doing; everything after that works identically over calls.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How long does it take to build custom project management software?
Plan on 12 to 16 weeks for a working first version and 6 to 9 months for a mature platform; those are typical Digital Heroes delivery timelines. The schedule killers are undecided permission rules and mid-build scope additions, not the code itself. Locking the workflow map during discovery is what keeps a build inside 16 weeks.
What happens if the agency that built our project management tool shuts down?
Nothing fatal, if you set things up correctly from day one: code in your own GitHub organization, infrastructure in your own cloud account, and written deployment documentation as a contract deliverable. With those in place, any competent team can take over a standard-stack codebase in one to two weeks. Takeover disasters happen when the vendor hosted everything in accounts they owned, so verify account ownership before the first sprint, not after the relationship sours.
How do I vet a software agency before hiring them to build a PM tool?
Ask to click through a workflow tool they shipped, live rather than in screenshots, and get a reference from a client whose system has been in production for over a year. Then ask two questions that expose weak vendors: how they migrate data out of your current tool, and what their maintenance retainer covered for that reference client last quarter. An agency that has genuinely shipped project management software answers both in specifics.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How do I work out whether a custom project management tool will pay for itself?
Add three lines: the per-seat fees you stop paying, the consultant and plugin spend you eliminate, and the hours your team stops losing to manual status reporting and duplicate data entry. On seat savings alone, payback typically lands between years two and four, which is why Digital Heroes tells teams under about 50 seats not to build. It gets much faster when the tool replaces both a SaaS bill and a consultant-maintained Jira setup, or when a client portal becomes part of what you charge for.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Which integrations should a custom project management tool have?
Start with the three that move money and attention: Slack or Teams for notifications, calendar sync for deadlines, and your accounting tool such as QuickBooks or Xero so tracked time flows into invoices without retyping. Development teams usually add GitHub or GitLab so tasks close when code merges. Each solid two-way integration adds roughly 1 to 2 weeks of build time, so rank them by hours saved per week rather than wishlist order.
Who can build custom project management software for a business in Dunedin?

Digital Heroes builds custom project management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, so an operator in Dunedin gets an assigned senior team rather than a local account manager.

Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.

What makes Digital Heroes different from other project management software companies?

Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.

Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.

How can I check Digital Heroes is legitimate before getting in touch?

Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.

Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.

Keep reading
let's build

Build something worth launching.

A plan, a team, a timeline, within 24 hours. No decks, no discovery calls. Tell us what you're building and we'll come back with a real scope and a real number.

message us directly · we reply within one business day

mission briefing

Monthly dispatch

Playbooks, real build costs, and what we're shipping. One email a month. No fluff.

visit us

New York HQ

1140 Broadway, Suite 704 · New York, NY 10001

Get directions
Online now

Hey there 👋 How can we help you today?