Conditions of satisfaction.
You buy acceptance criteria every day. This is ours: what each engagement delivers, what counts as complete, what you keep, and what we will not sell you. Written to be held to.
1. Who you are contracting with
MFG Analytics is a practice of Up Analytics LLC. The contracting party is Up Analytics LLC. Work is principal-led. Where a subcontractor is used, we say so before the engagement starts, and these conditions still apply.
2. What counts as complete
Each stage has a defined end. The stage is complete when the listed items exist and are in your hands — not when the hours are spent.
| Stage | Complete when you hold |
|---|---|
| Audit | A graded report card by ERP module (healthy, misconfigured, abandoned); a written reconciliation of where key numbers disagree and the cause of each; a recommendation with a price attached. Fixed scope, fixed fee. You keep all three whether or not you engage us again. |
| Build — the model | One semantic model in your Microsoft tenant, built on written definitions you approved; measures documented; every number traceable to the source transaction. |
| Build — operating views | Power BI reports reading from that model, drilling to the same transactions, with documented measures. |
| Transfer | Source, documentation, refresh logic, measure definitions, runbooks, and working sessions with your team. Included in every build, not priced separately. |
If a stage does not meet its criteria, it is not complete, and we finish it. Disagreement about whether criteria are met is resolved against this page and the engagement letter, in writing.
3. What you own
- The model, the reports, and the documentation. They are built in your Microsoft environment and stay there.
- The measure definitions, in writing, in a document you hold.
- The refresh logic and the runbooks, on a path your team controls.
- Your data. We do not copy it into a system of ours, and we do not host it.
There is no proprietary portal, no seat licence, and no hosting dependency on us. End the relationship and the system keeps running. That is the design, not a concession.
4. The recommendation set is closed
The audit ends in one of three recommendations: build the model, convert the ERP, or do nothing yet. There is no fourth, and no fourth will be added. Nothing else the principal sells can appear in your report card.
That restriction is the point of the grade. An assessment that can recommend its author's other product is not an assessment.
5. What we will not do
- Resell, or take a commission on, any ERP or reporting product. We are not a reseller for any vendor, and we take no referral fee in either direction.
- Hold your reporting behind a portal, a licence, or a refresh path we control.
- Retain a copy of your data after the engagement, beyond what your own tenant holds.
- Take ERP implementation work outside Infor CSI/Syteline and Global Shop Solutions. Transformation and analytics, any ERP; implementation, those two only.
- Start an AI engagement on data we have told you is not yet reliable.
- Continue selling into an engagement that the audit graded as not worth doing.
6. Fees, scope, and change
The audit is fixed scope and fixed fee, stated before it starts. Build work is quoted against a written scope. Scope changes are priced and agreed in writing before the work is done — we do not discover them in an invoice.
We do not discount by shortening the work. If the budget is smaller, the scope gets narrower and says so.
7. What depends on you
Our criteria assume access and answers. Specifically: read access to the ERP and the systems around it; a named person who can settle a definition when two departments disagree; and reasonable availability for the scheduled sessions. Where access is blocked or a definition cannot be settled, we say so in writing and the dates move rather than the quality.
8. The models on this site are illustrative
The exit model and the figures in the document library are illustrative. They model a mechanism using coefficients we consider defensible and inputs you supply. They are not a valuation, an appraisal, a quote, or investment, tax, or legal advice, and no engagement or duty arises from using them. Multiples vary by sector, size, buyer, and process. Do not put an output in front of a board as anything other than your own working assumption.
9. What this site records
This site records how the published tools are used, so we can improve them. It is first-party and anonymous. We collect no name, email, phone, company, or free text, and no page here asks for contact details.
| Recorded | Detail |
|---|---|
| A random browser identifier | Generated in your browser's local storage. It identifies a browser, not a person, and is not matched to any contact record. |
| Tool use | Page views; and on the exit model, each recalculation with its inputs and outputs, mode changes, and prints. |
| Request context | Page path, referring URL, campaign parameters in the link you followed, viewport size, browser language, time zone, and user-agent string. |
| Where it goes | A Google Cloud project controlled by Up Analytics LLC. Not sold, not shared with an advertising network, not used to build a profile of an identified person. |
No advertising or cross-site tracking pixels are loaded. Fonts are served by Google Fonts, which necessarily sees the request.
Stops the recording and deletes what this browser already holds. Applies to this browser only; a private window or a cleared cache resets it.
10. Confidentiality
What we see inside your systems stays there. We do not name clients, quote figures, or publish a case study without written permission, and the audit report is yours to circulate or not. Where we write about patterns — as in the document library — the examples are constructed, not lifted from a client.
11. Limits
We build reporting on the data your systems hold. We do not warrant that the underlying ERP data is correct — establishing where it is not is frequently the work. Decisions taken on the reports are yours. Liability is limited to the fees paid for the engagement in question, and neither party is liable for indirect or consequential loss. Nothing here excludes liability that cannot lawfully be excluded.
12. Changes
These conditions carry a revision date. The version in force for your engagement is the one current when the engagement letter is signed, and it does not change underneath you. Where this page and a signed engagement letter differ, the engagement letter governs.
Up Analytics LLC · hello@mfg-analytics.com · Revision 2026-07.
Questions about these conditions get a written answer before you sign anything.