Software & the engagement
Tailored software at a cost that makes sense.
We build applications within our proprietary platform as part of a process improvement engagement. Reusable components help us implement the software quickly and keep the cost proportionate to the benefit.
Build on components we can reuse.
We configure and extend our software around your company’s needs, including connections to existing systems. The application supports the process changes we work on with your team.
We compare implementation and ongoing costs with the expected benefit before recommending the investment.
How we assess the business caseKeep using it.
Choose your support.
Our offering for business applications deployed in your environment separates lasting usage rights from ongoing maintenance.
- Use it indefinitely
- Your perpetual license lets you keep using the implemented application without an active McIntosh maintenance agreement.
- Access your data
- Your business data remains accessible. We can provide APIs and MCP connections so your other systems and AI tools can work with it.
- Choose ongoing maintenance
- Maintenance and support are optional services. Their scope is separate from your right to continue using the application.
- Built on McIntosh software
- The proprietary platform and its software extensions remain McIntosh intellectual property. Implementation and customization do not include delivery of source code, the editable code behind the application, or transfer of its ownership.
Source-code delivery and IP transfers require a separate written agreement. Your signed agreement defines the license, deployment, interfaces, and support. Mercury and third-party products have their own terms.
Questions about software usage and ownership
Why use the McIntosh platform?
Our proprietary platform provides reusable components for rapidly tailoring applications within an improvement engagement. It helps keep the cost of the supporting tool proportionate to the business benefit.
Does paying for custom development include source code?
Our standard customer-deployed application offering covers the implemented software and perpetual usage rights. Configuration and development adapt and extend McIntosh software. Source-code delivery and intellectual-property transfers are separate items that must be expressly negotiated in writing.
Can our team maintain or change the underlying code?
A perpetual usage license and access to data or integration interfaces do not include source-level modification or maintenance rights. If those are a requirement, discuss them before the engagement so the agreement can address them explicitly.
Does this apply to Mercury and third-party products?
Mercury is part of our toolset and shares the McIntosh software foundation, but it has its own deployment and commercial terms. Third-party products also have their own terms.
What would the improvement be worth?
Start with the process, its current cost, and the benefit you want it to create.
Discuss a process