Research & direction
Connect market evidence and customer needs to priorities, product decisions and the assumptions still needing validation.
AcesOps · Product in development
Build the product.
Run the business around it.
Research the market. Win the work. Build and deliver. Look after customers. Keep the books in order. AcesOps is being designed to connect those responsibilities in one business operating system, with a shared view of commitments, evidence and what needs your decision. Small hardware teams are the first audience.
In development. The board validator is designed, not built. We are looking for hardware teams to help shape the first workflow.
One business · connected responsibilities · planned
The work around the product is part of the product’s success.
A customer promise should inform delivery. Delivery should inform purchasing and cash flow. Customer feedback should inform what gets built next. The intended system carries that context between roles, while you set priorities, approve commitments and resolve the questions that need you.
Sales & relationships
Keep opportunities, follow-ups, agreed scope and customer commitments connected to the team doing the work.
Delivery & purchasing
Coordinate capacity, dependencies, suppliers and purchases against what has been promised and approved.
Customer success
Carry onboarding, support and feedback back into delivery and product decisions.
Finance & administration
Bring business-wide receipts, expenses, invoices, reconciliation and cash visibility into the same operating picture.
Engineering & product
Connect hardware development and the supporting software factory to requirements, acceptance evidence and business priorities.
Business operations · planned
Handle the routine. Ask for what matters.
The intended experience is simple: receipts arrive and are filed, purchases are matched, and reconciliation proceeds when the required facts and rules are satisfied. This covers the finances of the business, not only the cost of a product.
If business purpose, the payment account or client allocation is unknown, AcesOps should ask a short, specific question and retain the answer. Declared conditions determine whether to proceed, ask or stop. Uncertainty is made explicit; it is never silently turned into a fact.
See the business working together
Explore the intended user experience. These purpose-built illustrations use fictional information; they are concepts, not screenshots of a finished product.
AcesOps WorkspaceCONCEPT PREVIEW · FICTIONAL DEMO DATA
Planned · illustrative business workflow
Know what is moving. Know what needs you.
One operating picture across customers, commitments, delivery and money, connected to the product being built.
Customers & growth
Market research informs priorities; opportunities and follow-ups carry the context behind each customer commitment
Delivery & customer success
Agreed scope informs work, purchasing and onboarding; support feedback returns to product planning
Finances & decisions
Receipts, invoices and cash visibility stay connected; unresolved facts or authority come back to you
Your next decisionSet priorities and resolve the decisions that require your input
This connected business workflow is a product direction, not an implemented end-to-end system. This illustration is not connected to the live application.
From design files to a build you can review
Start with the board you drew
The intended first workflow works with existing design files, locally. EasyEDA is the first format in scope, with KiCad designed as the next format.
Review the design on screen
Inspect the design and confirm what you intend to build. An existing AcesForge board-viewing tool informs this experience; the new validator is designed, not built.
Check against explicit rules
The planned validator evaluates declared checks offline. The design principle is that AI can flag or block a problem, but cannot grant a pass.
Run the whole business
The planned expansion covers business-wide receipts, purchases, reconciliation, client work and finances, alongside fabrication and product costs. Routine work follows explicit rules; missing facts prompt a focused question.
For people building physical products
Small hardware shops and electronics consultancies carry the engineering and the business. Design files, fabrication outputs, parts costs and customer commitments often live in different places.
We are starting with New Zealand product makers, including teams using EasyEDA for small production runs. A useful first conversation is about where design-to-build breaks down in your actual work.
Where development stands
- Built separately by AcesForge: an offline board-viewing tool. It is a foundation to learn from, not the new validator.
- Designed: the offline board validator, its findings view and KiCad support. The validator has not been built.
- Planned: market research, sales, customer success, delivery coordination, purchasing, receipt filing and reconciliation, alongside fabrication packs and BOM costing.
- Partly built: read-side books components and the supporting software factory. Neither makes the complete workflow available.
Design partnership · exploratory
Start with one workflow worth fixing.
Bring the friction
Describe the work, the people involved and where context gets lost. A non-sensitive walkthrough is enough for the first conversation; no system access is needed.
Agree a useful first step
Together, identify a bounded workflow, what a useful result would be and which decisions must stay with you. You leave with a proposed starting point and the open questions.
Choose the commitment
Any further participation, feedback sessions, data access, fees and delivery expectations are agreed before work starts. An introductory conversation is not a subscription or a promise of a finished platform.
Questions about AcesOps
What is AcesOps?
AcesOps is a business operating system in development for small hardware shops and people building physical products. Hardware checks are the first entry point. The wider system is intended to run the business, including market research, sales, delivery, customer success, purchasing and business-wide finances.
When would AcesOps ask me a question?
The intended policy is explicit: proceed when the required facts, rules and authority are satisfied; ask when a required fact is missing or conflicts. A purchase may need its business purpose, payment account or client confirmed. Confidence alone does not supply that answer. These workflows are planned, not yet fully implemented.
Is the board validator available today?
No. The validator is designed, not built. A separate AcesForge board-viewing tool exists, but it is not the AcesOps validator and was not built by the software factory.
Would I need to upload my board design?
The intended validator runs offline on local files. This is a product design commitment, not a claim that the unfinished validator is available today.
Who should get involved?
Small hardware shops, electronics consultancies and product makers, starting in New Zealand. We want to understand where moving from board design to fabrication and running the business causes friction.
Where does the software factory fit?
It remains a partly built supporting capability. It is not a finished autonomous multi-component development system, and it is not the first hardware product offer.
How is this different from hiring AcesForge?
AcesOps is the product being developed. AcesForge provides engineering services now, including hardware R&D, production testing, software and computer vision. You can discuss an engineering engagement without waiting for AcesOps.
Where does running the business slow you down?
Tell us what you build and where research, sales, delivery, customer care or administration lose their connection. Help shape one useful first workflow around your business, with clear boundaries on what happens automatically and what needs your input.