Six workbooks run your New Plymouth operation, one person understands all of them, and she is taking leave in September
Internal tools for a New Plymouth business typically cost NZ$25,000 to NZ$90,000 and ship in four to twelve weeks, based on Digital Heroes delivery across 2,000+ projects. This is the cheapest high-return software you will buy: replacing the crew allocation board, the permit tracker, the plant hire register and the calibration diary with something multiple people can use at once, with an audit trail, without the version-in-the-filename ritual.
Nobody set out to run a NZ$40 million business on spreadsheets. It happened because a workbook is the fastest way to solve Tuesday's problem, and Tuesday's problems accumulated. Now the crew allocation sheet has merged cells, conditional formatting nobody dares touch, and a tab called FINAL_v3_USE_THIS. When two supervisors open it at once, one set of changes disappears silently, and you find out during a shutdown when a crew turns up at Kapuni instead of Bell Block.
Airtable and Retool are the obvious next step and they solve part of it. Airtable is genuinely good until you hit its published per-base record ceilings or need a permission rule more subtle than table-level access. Retool gets you an interface fast but it prices per user, which stings when you want 60 supervisors to have read access. Neither will model the thing that actually matters: a crew member cannot be allocated to a confined space job if their ticket expires next Thursday.
What internal tools costs in New Plymouth
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single tool: crew board or plant register with rules and audit trail | NZ$25,000 to NZ$45,000 | 4 to 7 weeks |
| Two or three connected tools sharing staff, plant and site data | NZ$45,000 to NZ$70,000 | 8 to 12 weeks |
| Add offline mobile capture for permits and field records | NZ$20,000 to NZ$40,000 | 4 to 6 weeks |
The fix: internal tools built for New Plymouth, not rented
Internal tools earn their money by encoding the rules that currently live in someone's head. A custom tool refuses to allocate an unticketed worker to a confined space task, refuses to release lifting gear past its inspection date, and shows the crew board to everyone at once without anyone overwriting anyone. That is not a spreadsheet feature, it is a validation layer, and it is the difference between a register that records what went wrong and a system that stops it. The build is small enough that you can start with one tool, prove it in six weeks, and then decide.
- Two or more people need the same workbook at the same time and you have already lost data because of it
- A rule you care about, like ticket currency before allocation, cannot be enforced in a spreadsheet
- The workbook is now load-bearing enough that its owner's leave is an operations conversation
- The process is still changing every month and you are learning what it should be
- Fewer than about six people touch it and never at the same time
- Airtable or a Google Sheet with locked ranges genuinely covers it and you have tested that honestly
The capability list that earns its budget
New Plymouth internal tools: the full scope
Everything an internal tools build here can cover: approval workflows, internal portal, business process automation, data-entry tools, admin panel development, internal dashboards and Retool alternative.
How long it takes, phase by phase
Exactly what you get
One or more small web applications, each replacing a named workbook, with real user accounts, role-based permissions, validation rules and a change log. They share a single source of staff, plant and site data so a person or a crane exists once rather than in four sheets. You get the code and the hosting account. In practice the crew board is the first build, then the plant and calibration register, then permits. Where the tools touch bigger systems they read staff and ticket currency from HR software development, write labour to ERP (Enterprise Resource Planning) software development, pull stock levels from inventory management software, and feed business intelligence (BI) dashboards instead of each tool growing its own reporting screen.
How to choose a developer in New Plymouth
Give the shortlist your ugliest workbook and ask what they would cut. The right answer identifies the two columns that carry all the value and proposes shipping those in six weeks. The wrong answer is a proposal to model every tab. Ask for fixed-price first delivery, because internal tools are small enough to price properly and any supplier who will not is telling you they have not scoped it. Then ask what happens when you want a change in month four: a named rate, a response time, and whether small changes need a formal quote or come out of a retained block of hours.
- Concurrent access with no lost edits, so the crew board is one truth instead of five reconciled copies
- Rules enforced at entry: expired tickets, overdue calibrations and unavailable plant get blocked rather than reported afterwards
- An audit trail of who changed what and when, which matters the first time a client or WorkSafe asks
- Cheap enough per tool that you can build the highest-pain workbook first and judge the rest on results
- Removes the single-person dependency that currently makes September genuinely stressful
- Spreadsheets are infinitely flexible and custom tools are not, so a workflow you change monthly may belong in a workbook
- Small tools multiply, and without ownership you end up with a dozen mini-apps and the same knowledge problem in a new form
- You need someone internally who can specify the rules, and that person is usually the busiest operator you have
- Very simple needs are genuinely cheaper in Airtable, and a good developer will tell you that instead of quoting
- !They quote a platform rebuild when you asked for one tool. Ask for the smallest useful version and a price for that alone.
- !No question about who else needs read access. Ask how the licensing or seat model behaves at 60 viewers.
- !They ignore offline. Ask what happens when a supervisor logs a permit inside a plant with no signal.
- !They will not commit to a six week first delivery. Internal tools that take five months usually mean the scope was never controlled.
- !No plan for the spreadsheet's history. Ask what happens to three years of records and who verifies the import.
Most New Plymouth teams pricing internal tools end up comparing notes on custom software, wordpress, accounting too; the systems share one data spine. 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.
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
Aditya builds and maintains Shopify stores at Digital Heroes: theme development, Liquid work, app integrations and the custom features merchants ask for once a template stops fitting. His posts are hands on, aimed at store owners who want to know what a request really involves.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does an internal tool cost to build in New Plymouth?
A single well-scoped tool, such as a crew allocation board with ticket-currency rules and an audit trail, runs NZ$25,000 to NZ$45,000 and ships in four to seven weeks. Two or three connected tools sharing staff and plant data sit between NZ$45,000 and NZ$70,000. Adding offline mobile capture for permits and field records adds roughly NZ$20,000 to NZ$40,000.
Should a Taranaki engineering firm use Airtable instead?
Airtable is the right answer when the process is still changing and fewer than about six people use it. It stops being the right answer when you need enforcement rules, when you hit its published per-base record limits, or when you want 60 read-only viewers without paying per seat. Test it honestly for a month before committing either way.
Can an internal tool stop us allocating someone whose ticket has expired?
Yes, and that single rule is often the reason firms build. The tool holds each worker's confined space, working at heights, EWP and site induction currency, and blocks allocation to a task requiring a lapsed qualification. It can also warn at 30 and 14 days so the training gets booked instead of the job getting stopped.
How do we handle permit records when there is no signal inside a plant?
The mobile capture stores permits, isolations and photos on the device and syncs when it reaches coverage. Each record carries the device timestamp rather than the sync time, which matters if the register is ever used in an investigation. This is standard in Taranaki builds because assuming coverage at Motunui or offshore is how field tools fail.
What happens to the three years of history in our current spreadsheet?
You import what is genuinely useful and archive the rest as a read-only file. Most firms find only the last 12 to 18 months gets referenced, and forcing a full import usually imports the data quality problems too. Budget a few days for someone internal to decide what carries over and to verify the result against the original.
Do we own the tools if a New Plymouth agency builds them?
Yes, if the contract says so before you pay. The repository, the deployment configuration and the hosting account should be in your company's name. Digital Heroes assigns ownership on delivery, and any supplier reluctant to do the same is protecting a future lock-in you will pay for.
Can internal tools connect to our existing ERP or Xero?
Yes, and they should rather than duplicating master data. The common pattern is reading staff, cost centres and job numbers from the system of record and writing back labour hours or plant usage. That keeps one truth for jobs and stops a supervisor picking a job number that no longer exists.
How much maintenance do small internal tools need?
Budget 15% to 20% of build cost per year, which on a NZ$40,000 tool is around NZ$6,000 to NZ$8,000. That covers hosting, security updates, browser and OS changes on the tablets, and a small allowance for tweaks. Tools with no maintenance agreement quietly break at the two-year mark, usually on a device update.
Is it better to build one big system or several small tools?
Start with small tools that share one data layer. It gets value into the business in weeks rather than months, and it lets you learn what your process really is before you commit to a NZ$150,000 platform. Most New Plymouth firms build two or three, then decide whether the pattern justifies a full ERP rather than guessing up front.
Will a custom internal tool scale as our company grows?
Should I hire a freelancer or an agency for my software project?
What tech stack should an internal tool be built with?
Is a freelancer or an agency better for building an internal tool?
How much should a small business budget for its first custom app or website?
How many SaaS seats do we need before building custom becomes cheaper?
Are local developer rates in New Plymouth worth it compared to hiring an offshore team?
Who can build custom internal tools for a business in New Plymouth?
Digital Heroes builds custom internal tools 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 New Plymouth 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 internal tools 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.
