Back to field notesGovernment Procurement

How to Sell Technology to the New Zealand Government: GETS and Supplier Readiness

A step-by-step guide for foreign technology vendors on using New Zealand's GETS platform, qualifying supplier access, and building the evidence agencies expect before you respond.

Paglago/September 25, 2026/12 min read

New Zealand's government procurement system is more accessible than most foreign vendors expect, but access and readiness are two different things. The Government Electronic Tender Service (GETS) is free, open to international suppliers, and the starting point for most large public contracts. That does not mean every listing is worth your time or that your existing sales collateral will carry a bid.

GETS finds the opportunity. The buying agency controls the decision. Your job is to confirm supplier access, map your evidence to the published evaluation criteria, and resolve security, privacy, cloud, support, and local-delivery questions before you commit response resources. This article walks through that process in the order a technology vendor actually faces it.

GETS finds the opportunity; the buying agency controls the decision

The most common mistake foreign vendors make with New Zealand government procurement is treating GETS as a qualification system. It is not. GETS is a discovery and tender-management service run by New Zealand Government Procurement (part of the Ministry of Business, Innovation and Employment). It advertises opportunities, distributes tender documents, handles questions and clarifications, and collects submissions. It does not evaluate bids, set technical requirements, or decide who wins.

New Zealand Government Procurement states that GETS is used for most large government contracts and that the service supports open competition. The rules framework makes clear that domestic and international suppliers can access listed opportunities. Whether you are a viable bidder for a specific tender depends entirely on the buying agency's requirements, evaluation criteria, and the conditions stated in the controlling notice.

This separation matters because it shapes your entire approach. Register on GETS, set up your notifications, and treat it as a monitoring tool. But every qualification decision happens at the tender level: read the notice, retrieve the complete pack, and test your fit against what the agency actually wants.

How GETS, open tenders, selected tenders, and agency procurement fit together

New Zealand's procurement framework sits on the Government Procurement Rules, now in their 4th edition with updates through 2024. The rules set expectations for how agencies plan, approach the market, award contracts, and manage transparency. Rule 10 establishes the requirement to openly advertise, and it specifies how that advertising happens, including requirements for the GETS listing.

Agencies use GETS to publish contract opportunities. Some agencies are mandated to use it for large tenders. Others choose to use it because it is the standard channel. The practical result: if a New Zealand government agency is buying technology, there is a strong chance the opportunity appears on GETS, at least for contracts above certain thresholds.

GETS supports two main tender types:

Open tenders are available to any registered GETS supplier. You see the listing, download the pack, and submit your response. This is the most common route for foreign vendors and the one you should expect to encounter first.

Selected tenders (sometimes called closed or invited tenders) restrict participation to suppliers the agency has pre-identified or pre-qualified. You may see a notice on GETS, but you cannot respond unless you are on the shortlist. Some selected tenders follow a registration-of-interest (ROI) stage where the agency evaluates expressions of interest before inviting a smaller group to bid.

For below-threshold procurement, agencies have more discretion. They may use GETS, approach suppliers directly, or run a simplified process. The rules encourage agencies to consider capable New Zealand businesses, including Maori and Pasifika enterprises, for smaller contracts. This does not exclude foreign suppliers, but it means the competition dynamics shift at lower values.

The procurement thresholds relevant to foreign vendors under New Zealand's trade agreements are approximately NZD 260,000 for goods and services supplied to central government entities and approximately NZD 800,000 for Crown agents. Construction thresholds sit around NZD 10 million. These thresholds can change with currency fluctuations. Below these values, trade-agreement obligations on non-discrimination do not formally apply, though agencies still follow the procurement rules in practice.

Register, monitor, and retrieve the complete opportunity pack

Registering on GETS is straightforward. You need a RealMe account (New Zealand's government identity service), which you can create as part of the registration process. Once registered, you provide your business name, address, country, and capability description. The system pulls company information from the New Zealand Companies Office register if your entity is listed there, but you can also enter details manually for overseas businesses.

The registration form accepts any country in its address fields, confirming that international suppliers are expected participants. You do not need a New Zealand Business Number (NZBN) to register, though the form offers it as an optional lookup.

Once registered, set up your notification categories. GETS lets you subscribe to opportunity types by sector, region, and category. For technology vendors, relevant categories include information technology, telecommunications, professional services, and security services. The system emails you when new opportunities match your subscriptions.

When you find a relevant listing, download the complete tender pack immediately. Do not rely on the summary description. The pack typically includes the request for tender (RFT) or request for proposal (RFP), evaluation criteria, terms and conditions, any issued amendments, and a questions-and-answers log from the clarification period. Read every document. The summary on GETS gives you the title and closing date. The pack tells you whether you can actually bid.

Check the questions-and-answers section regularly during the open period. Agencies publish responses to supplier questions, and those responses sometimes change eligibility conditions, add requirements, or clarify ambiguities that affect your bid strategy. If you have a question that is not already answered, submit it through GETS. Agencies are required to respond, and the response becomes part of the official record available to all participants.

Qualify foreign-supplier access and tender-specific conditions

New Zealand is a party to the World Trade Organization Agreement on Government Procurement (GPA) and the Comprehensive and Progressive Agreement for Trans-Pacific Partnership (CPTPP). These agreements commit New Zealand to non-discrimination in covered procurement: agencies must not discriminate against suppliers based on the country of origin of goods or services, or the degree of foreign ownership.

The MFAT guidance on CPTPP government procurement states that these rules ensure open, fair, and transparent conditions of competition. In practice, this means that for covered procurement above the relevant thresholds, a foreign technology vendor from a GPA or CPTPP member country has formal legal access rights.

However, trade-agreement access does not mean every tender is open to every supplier. Several conditions sit on top of the formal access right:

Tender-specific eligibility. The controlling notice may require specific certifications, registrations, or qualifications. A cybersecurity tender might require a supplier to hold a specific security clearance. A government cloud procurement might require data to be hosted in New Zealand or in a country with an adequate data-protection framework. These are tender-level conditions, not blanket rules.

Language and documentation. Tender documents are in English. Responses must be in English. If your standard collateral is in another language, budget time for translation and ensure technical terminology is precise.

Insurance and liability. Many tenders require professional indemnity insurance, public liability insurance, or specific bonding arrangements. Check whether your existing coverage meets the stated minimums and whether your insurer can provide certificates valid in New Zealand.

Tax and entity questions. You do not need a New Zealand entity to bid on most tenders, but if you win, the contracting agency may require you to register for New Zealand goods and services tax (GST) and provide a New Zealand bank account for payment. Some tenders require a local entity for contract execution. Read the terms and conditions in the pack to determine what applies.

Trade-agreement thresholds. If the procurement value is below the relevant threshold (roughly NZD 260,000 for central government goods and services), the formal non-discrimination obligations do not apply. Agencies may still accept foreign bids, but they have more discretion to preference domestic suppliers or consider broader economic outcomes.

The key principle: do not assume access based on your country's trade-agreement status. Always confirm the specific tender's conditions.

Prepare value, security, privacy, cloud, support, and reference evidence

New Zealand government agencies evaluate technology bids against published criteria. Your job is to build evidence that maps directly to those criteria, not to present your product's general capabilities and hope the evaluator connects the dots.

The evidence categories that matter most in New Zealand government technology procurement:

Technical fit and functionality. Map your product's features to the agency's stated requirements. Use the language of the tender documents. If the agency asks for "integration with existing identity management systems," do not say "we support SSO." Explain which protocols you support, how the integration works, and provide documentation or a reference architecture.

Security posture. New Zealand government ICT systems must comply with the New Zealand Information Security Manual (NZISM), maintained by the Government Communications Security Bureau (GCSC). The NZISM contains approximately 1,700 controls organised across 23 chapters covering information security, physical security, and system accreditation. You do not need to be NZISM-certified to bid, but you need to demonstrate how your product meets or can be configured to meet the relevant controls. ISO 27001 certification is a strong baseline, but agencies may require specific NZISM alignment depending on the data classification level.

Cloud and hosting. The New Zealand government operates a Cloud First policy: agencies must consider public cloud services as a primary option, assessed on a case-by-case basis following risk assessments. The government's cloud jurisdictional risk guidance requires agencies to evaluate where data is stored, processed, and accessed. If your product is cloud-hosted, you need to state the hosting region, the data residency options, and the jurisdictional risk profile. Hosting in New Zealand or Australia is generally lower risk. Hosting in other jurisdictions requires the agency to assess specific legal and regulatory exposure.

Privacy and data protection. New Zealand's Privacy Act 2020 governs how personal information is collected, used, stored, and disclosed. If your technology processes personal information, the agency will assess your compliance posture. For SaaS products, this includes data encryption, access controls, breach notification processes, and cross-border data transfer arrangements.

Support and service levels. Agencies evaluate whether you can provide support during New Zealand business hours. If your support team is offshore, state your response-time commitments, escalation paths, and whether you offer local or regional support presence. Service-level agreements (SLAs) should be specific: include uptime commitments, incident response times, and planned-maintenance windows.

References and case studies. Government buyers in New Zealand look for evidence that you have delivered similar solutions in comparable environments. If you have New Zealand public-sector references, use them. If you do not, references from similar government contexts (Australian state or federal, UK central government, or Singapore government) carry weight. Generic private-sector references are less persuasive in a public-procurement context.

Choose direct delivery, prime/subcontract, or in-market representation

Foreign technology vendors entering New Zealand government procurement have three main delivery models. The right choice depends on the tender requirements, the complexity of the deployment, and whether local presence is operationally necessary.

Direct delivery. You bid, win, and deliver from your existing base. This works for cloud-based SaaS products where deployment does not require on-site presence, for products with strong remote support capabilities, and for tenders that do not require a New Zealand entity. Many GETS opportunities are open to direct foreign bids, especially for software and digital services.

Prime/subcontract. You partner with a New Zealand company that holds the prime contract and you deliver as a subcontractor or technology partner. This model works when the tender requires local delivery capability, when the agency prefers a single local point of accountability, or when the scope includes integration, training, or on-site implementation that you cannot credibly deliver from offshore.

Local representative or agent. You engage a New Zealand-based representative to manage the relationship, coordinate local activities, and provide market intelligence. The representative does not take the contract but acts as your in-market presence. This model suits vendors who want to build a pipeline of opportunities rather than respond to individual tenders, and who need local knowledge to navigate agency procurement cycles.

Some tenders specify the delivery model they expect. Others leave it to the supplier's proposal. If the tender is silent, choose the model that best matches your ability to deliver the stated outcomes. Do not propose a local partner you have not engaged or a capability you cannot staff. New Zealand government procurement values credibility over ambition.

New Zealand bid/no-bid checklist

Before committing response resources to a New Zealand government tender, work through these questions. If you cannot answer "yes" or "confirmed" to the first five, the bid is not ready.

1. Is the opportunity confirmed on GETS with a current closing date? Verify the listing is active, not closed or cancelled. Check for amendments that may have changed the scope, timeline, or conditions.

2. Does the tender permit your supplier structure? Confirm whether the notice requires a New Zealand entity, permits direct foreign bids, or specifies a delivery model. If the tender is a selected tender and you are not on the shortlist, you cannot respond.

3. Can you meet the stated evaluation criteria with documented evidence? Review every evaluation criterion in the tender pack. For each one, confirm you have specific, verifiable evidence. If you are missing evidence for a criterion that carries significant evaluation weight, the bid is weak.

4. Have you resolved security, privacy, cloud, and data-residency requirements? If the tender involves classified data, personal information, or cloud-hosted services, confirm your compliance posture against the stated requirements before committing.

5. Can you deliver support, training, and any required local presence? Confirm your support model works for New Zealand time zones and that any on-site requirements can be staffed.

6. What is the response cost relative to the opportunity value? Estimate the effort required to prepare a quality submission: technical writing, evidence gathering, pricing, legal review, and any partner coordination. Compare that cost to the realistic value of the opportunity and your probability of winning.

7. Is there a credible path to contract execution? If you need a New Zealand entity, a local partner, or specific insurance arrangements, confirm these are achievable within the tender timeline. Do not assume you can sort these out after winning.

8. Have you reviewed the terms and conditions? Government contracts in New Zealand include specific liability, indemnity, intellectual property, and dispute-resolution clauses. Review these with your legal team before committing. Do not assume your standard commercial terms will be accepted.

If you answer "no" or "unresolved" to questions 1 through 5, hold the bid. Research the gap, engage a local partner, or let the opportunity pass. Bidding on a tender you cannot credibly deliver wastes your time and damages your reputation with the buying agency.

What Paglago can do for your New Zealand market entry

Paglago acts as your in-market representative across the ANZ region. We do not just advise on market entry. We identify the right government opportunities, qualify them against your product and delivery capability, and coordinate the local relationships that make your bid credible.

If you are evaluating New Zealand as a government sales market, the first step is a conversation about your product fit, your current evidence base, and which delivery model makes sense. Talk to us about your New Zealand government sales strategy.

For a broader view of how we support technology vendors across the region, see our market entry services and how we work.

Frequently asked questions

Do I need a New Zealand entity to bid on government tenders?

Not always. Many tenders, especially for cloud-based software and digital services, permit direct bids from foreign suppliers. However, some tenders require a New Zealand entity for contract execution, and you will likely need to register for GST and provide a local bank account if you win. Read the tender's terms and conditions to confirm what applies.

Is GETS only for large contracts?

GETS advertises most large government contracts, and some agencies are mandated to use it for significant tenders. Smaller procurements may not appear on GETS at all, or may appear as selected tenders. For below-threshold opportunities, agencies have more discretion in how they approach the market.

Can I bid if my product is hosted outside New Zealand?

Yes, but you need to disclose the hosting location and the jurisdictional risk profile. The New Zealand government's Cloud First policy does not prohibit offshore hosting, but it requires agencies to assess data sovereignty, legal jurisdiction, and security risks. Hosting in Australia is generally lower friction than hosting in other regions.

What security certifications do I need?

There is no single mandatory certification for all technology tenders. However, ISO 27001 is a strong baseline, and agencies may require alignment with the New Zealand Information Security Manual (NZISM) for systems handling classified or sensitive data. Some tenders specify SOC 2 Type II or other frameworks. Always check the specific tender's security requirements.

How long does the typical procurement cycle take?

It varies by agency and complexity. Simple procurements may run from publication to award in 6 to 8 weeks. Larger, more complex technology procurements can take 4 to 6 months from the initial GETS listing to contract execution, with additional time for implementation planning. Monitor GETS early and often rather than waiting for a specific opportunity to appear.

Do free trade agreements guarantee I can bid?

Trade agreements like the GPA and CPTPP provide formal access rights for suppliers from member countries in covered procurement above specified thresholds. They do not guarantee you can bid on every tender. Tender-specific conditions, below-threshold procurements, and excluded sectors all apply. The agreements mean agencies cannot discriminate based on your country of origin for covered procurement, but they can set legitimate technical, security, and delivery requirements.

Sources

  • New Zealand Government Procurement, GETS supplier overview: https://www.procurement.govt.nz/suppliers/gets/
  • GETS supplier registration: https://www.gets.govt.nz/RegisterUser.htm
  • Government Procurement Rules (4th edition, updated through 2024): https://www.procurement.govt.nz/government-procurement-framework/government-procurement-rules/
  • Government Procurement Rules 4th edition PDF: https://www.procurement.govt.nz/assets/procurement-property/documents/government-procurement-rules-4th-edition.pdf
  • Requirement to openly advertise (Rule 10): https://www.procurement.govt.nz/government-procurement-framework/government-procurement-rules/approaching-the-market/requirement-to-openly-advertise/
  • Exemption from open advertising: https://www.procurement.govt.nz/government-procurement-framework/government-procurement-rules/approaching-the-market/exemption-from-open-advertising/
  • MFAT, CPTPP Government Procurement: https://www.mfat.govt.nz/en/trade/free-trade-agreements/free-trade-agreements-in-force/cptpp/understanding-cptpp/government-procurement
  • NZ Digital Government, Cloud services policy: https://www.digital.govt.nz/standards-and-guidance/technology-and-architecture/cloud-services
  • NZ Digital Government, Cloud jurisdictional risk guidance: https://www.digital.govt.nz/standards-and-guidance/technology-and-architecture/cloud-services/assess-the-risks/cloud-jurisdictional-risk-guidance
  • New Zealand Information Security Manual (NZISM): https://nzism.gcsb.govt.nz/ism-document
  • Protective Security Requirements, Information security: https://www.protectivesecurity.govt.nz/policy/information-security
  • WTO, Government Procurement Agreement thresholds 2026-2027: https://www.wto.org/english/news_e/news26_e/gpro_30jan26_276_e.htm
  • NZ Government Procurement definitions (GETS, open advertising): https://www.procurement.govt.nz/government-procurement-framework/government-procurement-rules/definitions/