Question 1

What does AcesForge actually do?

Accepted Answer

AcesForge is a small NZ-based team that builds custom software systems and produces hardware evidence packs for inventors and early-stage companies. We also run hosting and maintenance retainers for clients who want their systems kept current after delivery. The founder has a background in production-grade embedded systems from Tait Communications and holds the Steven Bly Award for best product or solution development, 2025.

Question 2

How does the AI-augmented dev factory work, and how do you keep things reliable?

Accepted Answer

We use AI tools to generate code faster than a traditional solo operator. Every output goes through the same review, testing, and deployment checks that any production system requires. AI helps with speed; engineering discipline keeps things from breaking. We do not ship without tests running and reviewers passing.

Question 3

What does an engagement look like from first email to launch?

Accepted Answer

Step one is a free discovery conversation where we figure out what you need and whether we are a good fit. Step two is a scoped proposal, either fixed price or time-and-materials, depending on how well-defined the problem is. Step three is the build, with async updates and weekly check-ins. Step four is deploy and handover: you receive the code, documentation, and full ownership. Step five, if you want it, is a hosting retainer to keep things running.

Question 4

How do you price work?

Accepted Answer

Custom software runs at NZD 220 to 280 per hour. Hardware evidence packs are scoped project-by-project depending on the complexity of the brief and the number of test cycles. Hosting retainers are a flat monthly rate. Contact us for a quote specific to your project.

Question 5

Do you take ownership of the code, or do we?

Accepted Answer

You own it. All code, documentation, and assets produced under an engagement are yours from the day they are delivered. We do not retain licences or create lock-in. If you take it to another team later, they can pick it up.

Question 6

What stack do you work in?

Accepted Answer

Primarily TypeScript on Node.js or Next.js for web and API work, Python for data pipelines and embedded scripting, and C/C++ for firmware when the project calls for it. On the infrastructure side we use Google Cloud and Firebase. We will work with your existing stack if it is reasonable; we will tell you honestly if it is not.

Question 7

Can you take over an existing project, or only greenfield work?

Accepted Answer

Both. Greenfield work is simpler to scope, but we regularly take over projects that are stuck or unmaintained. The first step for a takeover is a paid code audit so we understand what we are dealing with before committing to a timeline.

Question 8

What does the hosting and maintenance retainer actually cover?

Accepted Answer

Dependency updates, security patches, uptime monitoring, incident response, and minor change requests each month. It is not a blanket feature-development agreement. Larger feature work is scoped separately. The retainer keeps your system current and gives you a direct line when something goes wrong.

Question 9

Who can test my hardware prototype in Christchurch?

Accepted Answer

AcesForge provides independent bench testing and characterisation for electronics and hardware prototypes in Christchurch. We are not an accredited certification lab — our work is design-stage bench evidence and pre-compliance testing. If you need IANZ-accredited EMC certification, we can help you prepare for that process, but the accredited test itself happens at a certified facility.

Question 10

Do I need test data to support a patent application?

Accepted Answer

For hardware patent applications, a patent attorney will typically ask you to demonstrate that the invention works as claimed. Reproducible, characterised test results — produced by an independent party using documented methodology — strengthen the evidential basis of a patent claim. We produce test reports in the format patent attorneys ask for.

Question 11

How do I prove my hardware prototype works for investors?

Accepted Answer

Investors in hardware companies increasingly expect a data room with engineering evidence, not just a demo. A formal test report from an independent engineer — covering operating range, key parameters, and methodology — gives investors a document they can share with their own technical reviewers. We produce investor-ready evidence packs: signed report, raw data, and a summary suitable for non-technical stakeholders.

Question 12

What evidence does a patent attorney need for a hardware claim?

Accepted Answer

Patent attorneys generally need evidence that the claimed device or process performs as specified, produced under controlled and reproducible conditions. This typically means: a description of test methodology, the conditions under which measurements were taken, the actual measured results, and a statement of conclusions. We produce all of these as part of a standard evidence engagement.

Question 13

What is a hardware characterisation evidence pack?

Accepted Answer

A hardware characterisation evidence pack is a set of documents that prove how a device behaves across its operating range. It typically includes a signed test report (methodology, conditions, results, conclusions), a raw data package (oscilloscope captures, measurement logs, exports), and a characterisation summary mapping device performance across parameters such as voltage, temperature, load, or frequency. The pack is designed to be readable by patent attorneys, investors, and certifiers without further explanation.

Question 14

Can I get bench testing without using an accredited lab?

Accepted Answer

Yes. Accredited lab certification is required for market access (RCM, FCC, CE), but not for patent evidence, investor data rooms, or design-stage validation. Independent bench testing — carried out by a qualified engineer using calibrated equipment and documented methodology — is appropriate and widely used for these purposes. AcesForge is not an accredited lab, but our test reports are produced to an engineering standard suitable for patent attorneys, investors, and pre-certification evidence.

Question 15

What is hardware evidence engineering?

Accepted Answer

Hardware evidence engineering is the practice of producing documented, reproducible technical evidence about how a hardware device performs. The discipline sits between pure R&D (proving something works to yourself) and accredited certification (proving it to a regulator). It covers bench testing, parameter characterisation, pre-compliance assessment, and the production of formal test reports and data packages for patent attorneys, investors, and certifiers. AcesForge focuses on this discipline for NZ electronics and hardware firms.

Question 16

How much does it cost to test an electronics prototype in New Zealand?

Accepted Answer

AcesForge bench testing engagements start from NZD $750 for a single discovery-and-scope phase. Full characterisation and evidence pack engagements typically run $750 to $9k per phase depending on device complexity, number of test parameters, and deliverable requirements. Accredited EMC certification (which we do not perform) costs significantly more and varies by lab and test category.

Question 17

Is hiring a contract test engineer cheaper than hiring a test engineer in-house?

Accepted Answer

For most early-stage hardware companies, yes. A salaried test engineer in NZ runs to $80k-$100k per year before equipment, bench space, and software licensing. A contract test engagement costs a fraction of that for the specific evidence you need, with no ongoing overhead. If your test needs are episodic (patent filing, investor round, pre-cert), contracting is usually the right call. We can start an engagement before you have filled a test role and hand over a clean evidence pack when you do.

Question 18

How do I get my hardware evidence ready for an investor data room?

Accepted Answer

An investor data room typically needs: a description of what the device is and what problem it solves, evidence that it works as claimed (test report with methodology and results), any IP filings or prior art searches, and a statement of manufacturing readiness or bill of materials. We produce the engineering evidence component — the test report and data package. For IP filings and prior art, consult a patent attorney. For BOM and manufacturing readiness, your contract manufacturer can provide those.

Question 19

What test artefacts will a certifier or attorney ask me for?

Accepted Answer

Patent attorneys typically ask for: test methodology, test conditions, measured results, and a statement of conclusions. Pre-certification auditors ask for: evidence of design intent, initial bench measurements, and identification of known risks. Accredited certifiers ask for: the device itself, a description of its intended use, and access to design documentation. Our test reports cover the first two categories. We can help you prepare the documentation package for accredited lab submission.

Question 20

What is pre-compliance testing and do I need it before EMC certification?

Accepted Answer

Pre-compliance testing is bench-level emissions and susceptibility testing carried out at design stage, before submitting to an accredited EMC certification lab. It is not a substitute for accredited certification but it is a proven way to reduce the cost and risk of that certification. Most hardware companies that skip pre-compliance testing fail their first accredited lab attempt. Pre-compliance testing is not a regulatory requirement, but it is recognised industry practice for electronics development. AcesForge provides pre-compliance bench testing as part of our evidence engineering service.

Question 21

What is the difference between pre-compliance bench testing and accredited EMC testing?

Accepted Answer

Accredited EMC testing is carried out by a lab certified to a specific standard (e.g. IANZ in NZ) using traceable calibration and accredited processes. It produces a test report that regulators accept for market access (e.g. RCM, FCC, CE marks). Pre-compliance bench testing is non-accredited design-stage testing, done at an electronics workbench with calibrated but not IANZ-accredited equipment, to find and fix problems before the accredited test. AcesForge does pre-compliance and design-stage bench testing. We do not perform accredited EMC certification and will tell you so clearly.

Question 22

How do I reduce the cost of EMC certification?

Accepted Answer

The best way to reduce EMC certification cost is to test early at design stage and fix issues before the accredited lab visit. A single accredited lab retest typically costs more than a full pre-compliance bench engagement. AcesForge can help you identify emissions and susceptibility issues at the bench before you submit, which reduces the probability of a costly retest. We also help you prepare the documentation package that labs ask for on submission.

Question 23

Do I need an RCM mark for my electronic product in New Zealand, and how do I prepare for it?

Accepted Answer

The RCM (Regulatory Compliance Mark) is required for most electrical and electronic products sold in Australia and New Zealand. It covers electrical safety and electromagnetic compatibility. To obtain it, you need accredited test results from an approved test lab. AcesForge does not issue RCM certification — that requires an accredited lab. What we can do is help you prepare: pre-compliance bench testing to identify likely failure points before your lab submission, and documentation of design intent and test history that labs ask for. Think of us as the design-stage preparation step before accredited certification.

Frequently asked questions