Inducting two hundred seasonal workers in three days in Napier, in four languages, before anyone touches a ladder or a forklift

NZ$40,000 to NZ$60,000 for shared-device induction with comprehension checks, up to NZ$110,000 with multilingual delivery, a certification register and audit reporting. Content production sits outside that and typically adds NZ$10,000 to NZ$30,000 depending on how much original video and translation you need.

Yes, using a worker code or a scanned identifier issued at enrolment rather than an account with a password. This is the single most important design decision for RSE and seasonal workforces, and it is where most off-the-shelf products force an awkward workaround involving fake email addresses that nobody can reset later.

Design visually first, then add audio in the languages your workforce speaks. Translating text-heavy modules helps less than you would expect if literacy varies. Short demonstration video with spoken narration and simple visual checks works across languages and comprehension levels, and it is what we would recommend for a Hawke's Bay crew arriving in the same week.

It supports them by producing dated records showing who completed which module and what comprehension they demonstrated, which is stronger evidence than a signed attendance sheet. Your obligations under New Zealand health and safety law remain yours, so have your health and safety adviser confirm the content and the record format before you rely on it.

Yes, and it should take about two seconds on a phone. Scan or search the worker, see their current certifications and any expiry. This is the feature that turns an induction system from a compliance archive into an operational control, because the check happens at the moment the decision is made rather than in an office afterwards.

Eight to eleven weeks for the core system, plus content production time. Work backwards from your arrival week and add a rehearsal: run twenty people through it before the real intake to find the problems. Building an induction system while crews are already arriving does not work, so start in winter for a late summer arrival.

Someone internal has to own it, usually your health and safety lead. Procedures change, equipment changes, and content teaching an outdated process is worse than no content. Budget a few days each winter for a content review and factor small update costs into your support arrangement, because filming a replacement module is not a five-minute task.

Yes, and most Napier operators do once the system exists. Permanent staff training on cellar procedures, food safety or equipment operation runs on the same platform with individual logins instead of shared devices. Building for the harder case first, the seasonal arrival week, means the easier case is largely free.

They should be retained for a defined period consistent with your health and safety and Privacy Act obligations, then deleted. Retention is worth deciding before you start collecting, because seasonal workers return across years and you will want their certification history without holding personal data indefinitely. Make the retention rule explicit in the build.

TalentLMS handles standard corporate training well and is the fastest cheap start; its free tier alone covers 5 users and 10 courses. You outgrow it when you need custom role hierarchies beyond its branches, white-labeled portals for many client brands, or integrations it does not offer, and per-active-user pricing stings once learner counts reach the thousands. Run a three-year projection of your learner count against its published tiers before deciding; that math settles most build-versus-buy debates.

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.

One page with five answers: your learner roles, headcount now and in three years, whether you use SCORM/xAPI content from tools like Articulate or iSpring, the systems it must connect to (HRIS, SSO, payroll), and the one report someone will pull every month. That page gets you comparable quotes instead of guesses, and on Digital Heroes projects it routinely cuts discovery time in half. You do not need wireframes or a technical spec; producing those is the agency's job.

Being in the same city matters far less than timezone overlap and a weekly working demo. Where a Napier agency earns its premium is discovery, when in-person workshops with HR, department heads, and compliance stakeholders surface requirements a call misses. The hybrid most buyers land on: local or on-site discovery, distributed delivery, and every line of code in your own repository either way.

Yes, if scale is a design input rather than a hosting upgrade: enrollment and progress modeled as event-style records, video offloaded to a streaming CDN, and reports served from aggregates instead of live table scans. Most LMS scaling failures trace back to a schema tested at demo size, not to undersized servers. The question to put to an agency: what happens Monday at 9 a.m. when 3,000 people open the same compliance course before a deadline.

You should, and it must be in the contract: full IP assignment on final payment, the repository in your own GitHub organization, and hosting accounts in your company name. Watch for agencies that build on their proprietary platform and license it back to you, which is a subscription dressed up as custom development. The test is simple: if you cannot hand the code to another team tomorrow, you do not own it.

Ask them to open a live LMS they built and walk you through the SCORM tracking, the reporting layer, and what happens at your learner volume, because those are the three places cheap builds fail. Then check the contract for full IP assignment, hosting in your own cloud accounts, and a discovery phase before any fixed quote. An agency that prices a full LMS from a one-paragraph brief without discovery is guessing with your budget.

Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.

You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.

Digital Heroes builds custom LMS software systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Napier. You can chat with the team directly, and every form gets an email reply within 24 hours.