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. AliceHQ, our voice AI product, runs on infrastructure built and maintained by this same team.

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.

Frequently asked questions