Working with us
Useful questions begin with the workflow, your responsibilities and the arrangements needed to operate the solution. Commercial terms are agreed for each engagement.
What will our team need to contribute?
Your team’s role in an AI implementation
Your team can help us understand the process, share appropriate examples, and review whether proposed outputs are useful. A process owner is especially helpful; technology, data, and governance colleagues may be involved depending on scope. We agree roles and responsibilities together before implementation begins.
People and information
A process owner can explain how the workflow operates and help assess whether a change is useful. Subject-matter reviewers can assess outputs; technology, data, and governance colleagues may help confirm access, integration, and operating requirements.
Before work begins, agree who supplies permitted examples, reviews results, makes decisions, and prepares for handover. Please do not send confidential client files for an initial fit conversation.
What happens in the first conversation?
Your first conversation with Muuvment
The first conversation is a friendly discussion about your workflow, current challenges, and what a useful next step might look like. You do not need a finished business case. A simple process description is helpful; please do not send confidential client files for an initial conversation.
What is helpful to prepare
A short description of the process, the people involved, the current difficulty, and the result you hope to improve is enough. Approximate workload or time spent can help explain the context.
If there is a potential fit, a later discussion may define a scoped investigation or test. The first conversation does not determine final feasibility, price, or a complete business case.
How is the engagement priced?
Pricing a bespoke AI engagement
Muuvment prices work around the agreed scope rather than a universal package. Data preparation, licences, integration, evaluation, deployment, training, and ongoing support can all affect cost. After understanding your workflow, we will discuss the work involved and the commercial terms for your engagement.
What affects the scope
Discuss the workflow, data preparation, source licences, integrations, evaluation, deployment, training, and ongoing operating needs. These determine the work to be priced.
Separate implementation costs from recurring hosting, provider, data-licence, and support costs. The proposal should clarify what is included, what depends on third parties, and how scope changes are handled.
Who owns the software and operates the workflow?
Ownership and operation
Ownership and ongoing operation are agreed as part of each engagement. Custom code, reusable components, third-party licences, data rights, hosting, and support can have different terms. We discuss these early so your team understands its responsibilities and what handover or ongoing support includes.
Agree rights and responsibilities
Custom code, reusable components, third-party software, source data, and licences may have different terms. Business accountability is distinct from intellectual-property ownership.
Discuss hosting, access, documentation, training, maintenance, and support. Agree how your team will operate the workflow and what access or materials are provided at handover or if the engagement ends. The contract determines the specific rights.
Talk with Muuvment about your requirements.