--- title: Executable decision models | SpinForge url: https://spin-forge.com/solutions/decision-modeling description: Turn business rules, objectives and approved data into a reusable decision model your team can inspect and run. --- [All solution workflows](https://spin-forge.com/workflows) 10 / Model & explain Executable decision models # Make the requirements runnable. Turn business rules, objectives and approved data into a reusable decision model your team can inspect and run. [Discuss the scope](https://spin-forge.com/contact?product=workflow-decision-modeling&interface=all&brief=SpinForge+request%3A+Executable+decision+models%0A%0APlease+scope+this+customer-specific+engagement.%0A%0ABoundary%3A+A+proof+applies+to+the+encoded+model%2C+not+automatically+to+the+original+business+intent.+Requirement+interpretation+and+customer+approval+are+part+of+this+engineering+engagement.+Natural-language+understanding+and+arbitrary+format+translation+are+not+implied.) [See what you get](https://spin-forge.com/solutions/decision-modeling?section=workflow-delivery) Customer-specific engineering Selected product access: CLI · MCP · Headless BUILT FOR Operations owners, planning-software teams and engineering groups with a valuable decision but no agreed executable model. THE CHALLENGE / THE RESPONSE ## Start with what needs to change. Agree the business requirement, model and outcome before choosing the implementation. 01 ### The business request is not yet a precise model. Capacity, deadlines and priorities can mean different things to different people. HOW SPINFORGE HELPS We define the units, data mappings, decision variables and objective with the customer, then connect that approved specification to a supported model. 02 ### Mandatory rules are mixed with preferences. An attractive score can hide a requirement that was never represented correctly. HOW SPINFORGE HELPS Separate non-negotiable requirements from authorized trade-offs. Record customer-approved positive, negative and boundary examples before acceptance. 03 ### Every revision starts another translation exercise. One-off spreadsheets and undocumented assumptions make the decision difficult to repeat. HOW SPINFORGE HELPS Deliver a versioned model, input contract and repeatable invocation path, with ownership of future model changes made explicit. WHAT YOU GET ## A usable deliverable. Not just a score. The written scope names the inputs, implementation, evidence and handover your team receives. 01 ### An approved requirement map Definitions, units, objectives, mandatory constraints and permitted preferences, reviewed by the customer. 02 ### An executable model The supported representation and data adapter selected for the workflow, with its original-source relationship retained. 03 ### Acceptance examples Approved valid, invalid and boundary cases that test the interpretation as well as the returned result. 04 ### An operating handover Invocation, revision, evidence and review instructions for the agreed environment. AN ILLUSTRATIVE WORKFLOW ## See the work in context. A production planner wants to allocate work subject to machines, qualified operators and due dates. The engagement defines what each limit means before an optimizer is asked to choose. Illustrative, not a customer case study. ### A planning rule becomes a repeatable decision. Illustration of the engagement, not a live solver or a customer case study. 01 / 03 ### Agree the meaning Identify the decision, units, rules, objectives, source data and who can approve changes. QUALIFY THE FIT ## Your requirements. An explicit scope. The following inputs and measures guide the proposal and acceptance plan. ### What you bring - Business objective and current process - Data dictionary, units and sample inputs - Mandatory rules and permitted preferences - Named model owner and acceptance examples ### What we measure - Coverage of approved requirements - Rejection of contradictory or invalid inputs - Agreement on positive and boundary cases - Time and effort to repeat a supported decision THE BOUNDARY A proof applies to the encoded model, not automatically to the original business intent. Requirement interpretation and customer approval are part of this engineering engagement. Natural-language understanding and arbitrary format translation are not implied. PRODUCTS TO CONSIDER Select only what the task needs. These links do not assert a completed combined integration. [UNISOLVE](https://spin-forge.com/unisolve) [GARMO UCS](https://spin-forge.com/ucs) [SpinForge + Atlas](https://spin-forge.com/spinforge) [GarmoForge](https://spin-forge.com/garmoforge) HOW TO BUY ## Define one useful deployment. Commission a bounded scope using the existing engineering and licensing options. A $15,000 workload assessment or $30,000 focused sprint may fit a limited first step; neither includes the entire workflow by default. Larger implementation, operated delivery, compute and continuing rights are agreed separately. [Single-workload assessment — $15,000](https://spin-forge.com/engineering/workload-assessment) [Focused sprint — $30,000](https://spin-forge.com/engineering/focused-sprint) [All prices & rights](https://spin-forge.com/pricing) PREPARE YOUR SCOPE Delivery preference Preferred access What should this accomplish? What would make the result acceptable? Prepared locally. Review and send through your email application. No model upload, job execution, payment or account activation occurs here. BEFORE YOU BUY ## A few useful distinctions. **Is this another product or an already integrated application?**This is a customer-specific engagement using selected existing products. The model, adapters, user experience and acceptance work are scoped before delivery. It does not add another underlying product or establish a completed integration. **Can we use our existing software?**Yes, where its input, output and operating interfaces fit the agreed scope. A custom adapter may be required. The existing tools do not have to be replaced to qualify one useful component. **How are price and acceptance set?**Agree the baseline, required result, explicit limits, delivery capacity and acceptance tests before work begins. Existing software rates remain unchanged; engineering already included in a larger scope is not charged twice. RELATED WORK ## A complete process. Selected capabilities. These workflows can be scoped together or independently. [11 / Customer-specific engineering ### Conflict diagnosis & authorized repair Explain a supported infeasible plan and compare explicitly authorized changes without silently weakening mandatory requirements.](https://spin-forge.com/solutions/conflict-repair) [12 / Customer-specific engineering ### Decision history & reoptimization Retain the model, assumptions and result history so changed requirements can be checked and re-evaluated without losing their meaning.](https://spin-forge.com/solutions/decision-history) [Explore all 17 solution workflows](https://spin-forge.com/workflows)