Questas built three custom applications where off-the-shelf software did not fit
Questas operates in a manufacturing environment where production, planning, quotation, maintenance and operational coordination depend on processes that are too specific for generic SaaS but too important to leave in spreadsheets and email. The business needed software that matched the way the operation actually worked, not workflows reshaped to fit someone else's product.
Inlight IT supported Questas with three custom applications built on an open-source foundation: a manufacturing process and equipment-maintenance tool, a customer quotation application, and a production and planning tool. Each was designed around a specific operational process, integrated where appropriate, and delivered with long-term ownership in mind rather than as disposable bespoke code.
- Client
- Questas
- Industry
- Manufacturing
- Location
- Australia
- Starting point
- Production, planning, quotation and maintenance processes too specific for generic SaaS but too important to leave in spreadsheets and email
- Engagement type
- Three custom applications on a production-grade open-source foundation
- Delivery scope
- 3 process domains: equipment maintenance, customer quotation and production planning
- Outcome
- Three owned applications shaped around real manufacturing processes, delivered with documentation and lifecycle planning
Questas — three custom applications for manufacturing operations
How processes too specific for SaaS and too important for spreadsheets became owned software.
Three applications, one owned open-source foundation
Custom applications across maintenance, quotation and production planning.
Production-grade frameworks selected for long-term durability.
Built on a foundation the business owns, with cost disconnected from user count.
Software shaped to the operation, not the operation reshaped to software.
Manufacturing software needs to fit the operation, not the other way around
Australian manufacturing organisations face a genuine choice point on operational software.
Off-the-shelf SaaS works for some processes, but production-specific workflows, quotation logic, planning constraints and maintenance routines often do not fit a generic product without compromise. Per-user SaaS licensing also creates cost trajectories disconnected from the value the software delivers.
For Questas, the processes were too specific to force into someone else's product and too important to leave in spreadsheets.
Questas needed software that matched the operation, not workflows reshaped to fit someone else's product
Custom application development is rarely the cheapest first move. It is often the right move when off-the-shelf software cannot accommodate operational reality, and when long-term cost and supportability matter more than speed of initial deployment.
Years of process refinement off-the-shelf cannot accommodate
Manufacturing operations carry years of process refinement. Generic products require that refinement to be compromised to fit the tool, which erodes the operational advantage it represents.
The cost trajectory of per-user SaaS
Per-user SaaS licensing ties cost to headcount rather than value. For core operational software used across the operation, that trajectory can outweigh the cost of building once and owning.
Owning the foundation, not renting it
The decision was not only about fit today. It was about owning a foundation the business could maintain and extend, rather than depending on a vendor's roadmap and pricing.
Too specific for generic SaaS, too important for spreadsheets
Production, planning, quotation, maintenance and operational coordination depended on processes too specific for a generic product but too important to leave in spreadsheets and email.
The right move, not the cheapest first move
For Questas, long-term cost and supportability mattered more than speed of initial deployment — the case where custom development is the right move rather than the default.
Three custom open-source applications covering manufacturing automation, quotation and production planning
Inlight IT supported Questas with three custom applications, each designed around a specific operational process. The applications were built on an open-source foundation, integrated where appropriate, and delivered with long-term ownership in mind. The engineering was sequenced deliberately: process before code, architecture before frameworks, integration before features, ownership before handover.
01An application for production-floor process and equipment maintenance workflows
A tool to automate production-floor process and equipment-maintenance workflows, built around how maintenance actually runs on the floor.
02A structured tool for customer quotation handling
A quotation application that gave customer quotation handling a structured, repeatable path rather than spreadsheet and email assembly.
03An application to support production scheduling and operational planning
A production and planning tool that supported scheduling and operational planning against the constraints the operation actually works within.
04Production-grade open-source frameworks selected for long-term durability
Frameworks chosen for durability and maintainability, so the applications would last as production software rather than as a short-lived build.
05Custom development delivered as production engineering, not bespoke code
Delivery treated as production engineering, with architecture, integration and documentation, so the result was an asset the business could own and operate.
Process before code, architecture before frameworks, ownership before handover
Select a stage to trace how each application moved from process to owned software.
Custom does not have to mean disposable
The reputation of custom software as expensive and fragile comes from builds done without engineering discipline. With architecture, framework selection, integration and lifecycle planning, custom development produces an asset rather than a liability. For operational processes too specific for SaaS and too important for spreadsheets, that discipline is what makes building the right call rather than the risky one.
Three custom applications, each designed around a specific operational process.
One production-grade open-source foundation the business owns and can extend.
Three process domains — quotation, production planning and maintenance — moved out of spreadsheets and email.
Cost disconnected from user count, with no dependence on a vendor's roadmap and pricing.
Questas owns custom software that supports core operational workflows
The engagement gave Questas three custom applications shaped around its real manufacturing processes, built on a foundation the business owns long-term. Quotation, production planning and maintenance moved out of spreadsheets and email into purpose-built applications, with cost disconnected from per-user licensing and the code delivered with documentation and lifecycle planning.
Processes out of spreadsheets and email
Quotation, production planning and maintenance moved into purpose-built applications.
Software shaped to the operation
Each application reflected real manufacturing processes rather than forcing the operation to adapt.
A foundation the business owns
Built on production-grade open-source frameworks the business owns, with cost disconnected from user count.
Delivered for the long term
Documentation and lifecycle planning included, so the software remains an asset that can be supported and extended.
Maintenance runs on structured workflows
Production-floor process and equipment-maintenance workflows were automated around how maintenance actually runs on the floor.
Quotations follow a repeatable path
Customer quotation handling gained a structured, repeatable path rather than spreadsheet and email assembly.
The decision was not only about fit today. It was about owning a foundation the business could maintain and extend, rather than depending on a vendor's roadmap and pricing.
Custom development as production engineering, not bespoke code
Three custom applications
Maintenance, quotation, and production planning.
Built to fit the operation
Software shaped to real manufacturing processes, not the reverse.
Production-grade open source
Frameworks chosen for long-term durability.
Owned, not rented
A foundation the business owns, with cost disconnected from user count.
Production engineering
Delivered with architecture, integration and documentation.
Lifecycle planning
Documentation and a path for ongoing ownership.
The work connected custom development, open-source engineering and long-term ownership
Custom application build
6- Custom application development
- Open-source frameworks
- Production-grade selection
- Architecture-led delivery
- System integration
- Documentation
Manufacturing workflows
6- Manufacturing automation
- Production-floor processes
- Equipment maintenance
- Maintenance workflow automation
- Operational coordination
- Process fit
Quotation and planning
6- Quotation workflow
- Customer quotation handling
- Production planning
- Production scheduling
- Planning constraints
- Repeatable process paths
Ownership and lifecycle
6- Long-term ownership
- Lifecycle planning
- Cost disconnected from user count
- No vendor lock-in
- Maintainable asset
- Supportable extension
Have an operational process that off-the-shelf software cannot accommodate?
We confirm whether a custom application is the right answer, then scope and build it.
Discuss automation