The bowl sold on Instagram at 9pm and on the website at 9.04pm, and only one of them exists
Custom software for a Whanganui business runs NZ$45,000 to NZ$180,000 depending on scope, with a working first release in 10 to 20 weeks. The build almost always starts in the same place: you make things that exist exactly once, you sell them through three channels that do not talk, and generic SaaS has no concept of a stock level of one.
You make a piece. It goes on the website, gets photographed for Instagram, and travels to the Saturday stall by the river. Three channels, one physical object. Somebody buys it in a comment thread while somebody else checks out online, and now you are writing the apology email and processing a refund on work that took two days to make. It has happened enough times that you have started deliberately under-listing, which means you are hiding your best work from buyers to protect yourself from your own systems.
Generic SaaS cannot fix this because it was built for products with quantities. Shopify assumes restocking. A market stall assumes cash. Instagram assumes nothing at all. Each tool is competent alone and useless together, and the gap between them is exactly where your margin and your reputation leak out.
Where the off-the-shelf tools fall short
- A one-off piece sells simultaneously on the website and in an Instagram DM, and the refund conversation costs you a collector
- You under-list work on purpose to avoid double selling, so your strongest pieces never reach the wider market
- Nobody can say what stock is at the studio versus a gallery versus in a courier van without three phone calls
- Commission work, editions and one-offs all get forced into the same product record, so pricing history is meaningless
Custom custom software: what Whanganui teams actually get
The fix is a single source of truth for physical objects that every channel has to ask before it sells. That is a small system, not a big one: a piece register, a reservation mechanism with a timeout, and channel adapters. Once it exists, an Instagram DM can hold a piece for twenty minutes while payment is arranged, and the website will refuse the sale for those twenty minutes. No off-the-shelf product does this because no off-the-shelf product assumes quantity one is the normal case.
Feature priorities for Whanganui teams
What we build under custom software in Whanganui
Digital Heroes builds the full custom software stack for Whanganui teams. Typical engagements cover API development, cloud software, MVP development, legacy modernization, systems integration and microservices.
- You have refunded a customer because two channels sold the same physical item
- Manual reconciliation between channels takes more than half a day a week
- You are turning away wholesale or gallery relationships because you cannot promise availability
- Growth is currently limited by admin rather than by demand or production capacity
- You sell repeatable products with real stock quantities
- Your volume is low enough that one person can hold availability in their head
- A single channel accounts for almost all revenue
- You would rather spend the budget on marketing and a better photographer, which is often the right call
The honest cost picture for Whanganui
| Project scope | Typical cost | Timeline |
|---|---|---|
| Piece register with reservations and two channels | NZ$45,000 to NZ$75,000 | 10 to 14 weeks |
| Full multi-channel platform with Xero and courier integration | NZ$85,000 to NZ$140,000 | 16 to 24 weeks |
| Platform plus wholesale, consignment and reporting | NZ$140,000 to NZ$220,000 | 26 to 36 weeks |
Timeline: what happens, and when
Exactly what you get
A system that knows how many of a thing exists and refuses to let two people buy it. Concretely: a register of physical pieces with photos and provenance, a reservation engine with configurable holds so a phone sale and a web sale cannot collide, adapters for each channel you sell through, a refund flow that returns a piece to availability in one action, and reporting on sell-through by channel and price band. You also get the source code, deployment configuration and documentation, plus a migration of your existing product data with the duplicates from three years of parallel spreadsheets resolved.
How to choose a developer in Whanganui
The right partner will tell you to build less than you asked for. Ask each candidate which single problem the first release solves and how they would keep you trading through the transition, because a Whanganui maker cannot pause selling for four months. Ask for a capped phase one with a defined deliverable rather than open hourly billing. Check they can integrate with Xero and a New Zealand courier without inventing a bespoke API layer. And get code ownership, hosting credentials and a written handover into the contract before the first payment, not after the relationship sours.
- A reservation model that lets you sell confidently across a website, a stall and social messages without overselling
- Every physical piece tracked with photos, provenance, dimensions and location from hot shop to buyer
- Pricing history per piece and per maker rather than per SKU, which is what actually informs your next release
- Channel margin visibility, so you can see whether the stall, the gallery or direct sales genuinely pay after fees and freight
- Foundations that later carry /shopify-development/whanganui-mwt/ and /pos-system-development/whanganui-mwt/ instead of another integration
- Discovery is real work and will take two or three weeks before a line of code is written
- You inherit responsibility for uptime, backups and security that a SaaS vendor previously carried
- A partial build can be worse than none, because staff will trust it and it will not yet cover every channel
- For a maker turning over under about NZ$250,000, disciplined process on existing tools beats a NZ$50,000 build
- !They quote before understanding that quantity one is the core constraint. Ask them to explain how a reservation expires.
- !A proposal that starts with a rebuild of your website. Ask which single problem the first release solves.
- !No plan for what happens during the build. Ask how you keep trading while the system is made.
- !Hourly billing with no fixed scope for phase one. Ask for a capped first phase with a defined deliverable.
- !They cannot name a similar build. Ask for one reference where physical unique items were the subject.
Most Whanganui teams pricing custom software end up comparing notes on website, inventory management, warehouse management too; the systems share one data spine. Weighing options across the region? We publish the same custom software guide for Palmerston North. Prefer to talk to the team that builds these? Digital Heroes handles custom software development end to end.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- 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) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
Zayn sets the direction of UK engagements before any code is written, working out which problems are worth solving first and what a sensible first release looks like. Readers get a view of how buying decisions are actually made, including the ones that get deferred.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does custom software cost for a Whanganui studio selling one-off work?
A piece register with reservations across two channels runs NZ$45,000 to NZ$75,000 over 10 to 14 weeks. Adding Xero, courier integration and a third channel takes it to NZ$85,000 to NZ$140,000. If your annual sales are under about NZ$250,000, tighten your process on existing tools first and revisit in a year.
How does a custom system stop us double selling across Instagram and the website?
Every channel checks one register before completing a sale, and a social sale places a timed reservation that blocks the web listing while payment is arranged. Twenty minutes is the hold window that works best in practice. The website simply refuses to sell a reserved piece, which is the behaviour no off-the-shelf tool gives you when quantity is one.
Can we keep Shopify and still fix the overselling?
Yes, and often you should. The custom system becomes the source of truth and pushes availability to Shopify through its API, so you keep the storefront, checkout and payment handling you already pay for. That approach usually saves NZ$20,000 to NZ$40,000 compared with building a storefront from scratch.
How do we keep trading during the build?
Phased release. The first deployment usually covers the piece register and one channel, running in parallel with your current process for two to three weeks before anything is switched off. Nobody in Whanganui can afford to stop selling through a build, so any plan involving a hard cutover is a plan to lose a season.
What happens to GST and invoicing?
The system generates the sale record and pushes GST coded invoices into Xero, which stays your filing system of record for 15% GST returns. Sales through a gallery on consignment need different treatment because the commission is the gallery's revenue, and that logic has to be explicit rather than assumed.
Do we own the software outright?
You should own the source code, the database, the hosting accounts and the documentation. Put it in the contract before work starts, with the repository under your organisation from week one. Ownership without documentation is only half the asset, so make the handover document a named deliverable.
How long does the whole thing take?
Ten to twenty weeks depending on how many channels are in scope. Discovery takes two to three weeks and is where the money is saved or wasted, because the reservation rules and channel behaviours have to be decided by you rather than guessed by a developer.
Can a Whanganui developer maintain this after launch?
Yes, provided it is built on a mainstream stack rather than something exotic. The local community around design and technology has capable people, and Palmerston North is close enough for on-site work. Ask your builder to write the maintenance guide as a deliverable so a second developer can start without a discovery phase of their own.
What ongoing cost should we plan for?
Budget NZ$1,200 to NZ$4,000 a month for hosting, monitoring, security updates and a small change allowance. Multi-channel systems need more attention than internal tools because third party APIs change without asking you. Software with no maintenance budget quietly rots and then fails during your busiest week.
Does it matter which tech stack the agency wants to use?
What happens if I stop paying for maintenance after launch?
Who owns the code when an agency builds my software?
How do I calculate whether custom software will pay for itself?
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
What is a discovery phase, and is it worth paying for separately?
How long does it take to build a custom web or mobile app from scratch?
How many people should be working on my software project?
What happens to my software if the agency shuts down or we stop working together?
What does it cost to keep custom software running after launch?
Who can build custom software for a business in Whanganui?
Digital Heroes builds custom 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 Whanganui 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 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.
