No false “live” labels
Discovery, prototype, private beta and generally available are separate product states.
Product pipeline
A disciplined sequence—not six unfinished products at once.
AESS will reuse proven engineering foundations while keeping product teams focused. TradiePro web and its customer rollout come first; iOS follows; the broader pipeline advances through documented discovery and pilot gates.
Development principle
Shared core, industry-specific workflow.
Customers, people, roles, work orders, assets, stock, purchasing, documents, evidence and reporting can be reused. The operational language, approvals, screens and compliance model must still be designed for each industry.
Gate for every product
- Problem and customer discovery
- Written scope and permission model
- Prototype and internal use
- Controlled pilot
- Security, backup and recovery acceptance
- Documented commercial release
Recommended sequence
Operating foundation
AESS Workshop Manager
Continue daily operational use, reliability work and reusable module extraction.
Current priority
TradiePro web platform and first paying customers
Complete role controls, demo quality, onboarding, backup, support documentation, project validation and a repeatable customer-instance deployment process.
Next build phase
TradiePro iOS field application
Harden the mobile API, authentication, assigned-job scope, camera workflows and online operation first; then implement and test offline queueing, conflict handling and synchronisation.
Parallel discovery only
Marine & Plant CMMS
Capture vessel/site hierarchies, maintenance regimes, class and audit obligations, running-hour sources, spares, defects, permits and connectivity constraints.
Pipeline
Facilities Management
Hotels, resorts, hospitals, campuses and commercial facilities—asset maintenance, rooms and areas, inspections, contractors, guest-impact priority and compliance.
Pipeline
Rental Property Operations
Property registers, tenants and contacts, maintenance requests, inspections, approvals, contractor dispatch, evidence, expenses and property history.
Pipeline
Victualing & Provisioning
Vessel or remote-site headcount, dietary requirements, menus, stores, requisitions, purchasing, receiving, waste and per-person cost reporting.
What we will not do
No uncontrolled custom fork
Customer-specific development must fit a documented product architecture and maintainable release path.
No growth without operations
Backup, rollback, security, manuals, onboarding and support are release requirements—not cleanup work after sales.
Have operational expertise in one of these industries?
AESS is interested in structured requirements, sample workflows and serious pilot partners—not feature wish lists without operating context.