M-Power Analytics - What can i do? – M-Power Software Help Centre

M-Power Analytics lets you ask Claude questions about your M-Power data in plain English. You get answers, tables and charts back in seconds, with no reports to build. This guide shows you how to start, what data is there, and how to work through the questions people ask most.

Getting started

Connect once. Follow Connect Claude to M-Power Analytics. It takes about 6 minutes. You sign in with the account M-Power set up for you.
Start a new chat in Claude and make sure the M-Power Analytics connector is switched on.
Ask a warm-up question so you can see how it works, for example: "What were our sales last month, and how does that compare with the same month last year?"
Follow up in the same chat: "Split that by account manager", "Show it as a bar chart", "Which customers drove the change?"
Check the working for anything you'll rely on: "How did you work that out?"

Three things to know before you start:

Your company's data only. Claude sees only your company's data, and only while you're signed in.
Read-only. Claude can look at your data but can't change anything in M-Power.
Updated overnight. Data is copied from M-Power each night, so today's changes show up tomorrow morning.

What's in your data

Claude can report on 12 areas of M-Power, from the first lead to the final invoice. Some areas only fill if your team records that work in M-Power. The last column says what that is.

Area	What you can see	Needs in M-Power
Sales (orders)	Every job by order date, with value, lines, products, work type, customer, account manager and profit centre	Nothing extra
Quotes	Every quote and line, whether it became an order and how many days that took, and portal quote requests	Nothing extra
Leads and opportunities	Status, outcome, loss reason, quoted value, and whether each was won	Leads entered in the CRM
Work in progress	Open jobs, WIP status, required-by date, on hold, released to production, and who released them and when	Nothing extra
Production progress	Which step each job line is on, planned against actual minutes per step, and percent complete	Jobs stepped through production, with job timing
Capacity and workload	Outstanding hours by department and week, overdue work, and load against what each department usually gets done	Planned times on BOM steps
Materials	The raw materials each job needs (sheets, square or lineal metres), and whether the step that uses them is done	BOM materials on quotes and jobs
Purchasing	Purchase orders and lines, suppliers, what's still to arrive, late lines, goods received and rejected	Purchase orders raised in M-Power
Delivery and DIFOT	Despatch dockets, carriers and freight cost, partial despatches, and whether each job went in full and on time	Required-by dates and despatch dockets
Invoicing	Invoices and lines ex and inc tax, invoice type and deposits	Nothing extra
Staff time	Attendance, hours recorded on jobs, and utilisation per person per day	Clock-on and job scanning
Customers, contacts and portal	Customer groups and branches, contacts, notes and sales calls, portal users, portal items and portal orders	Notes logged against customers; client portal in use

Not covered yet: stock on hand and stock movements, costs and margins, and payments received. You can ask Claude "What data do you have about purchasing?" at any time to see what's there.

Common scenarios

Each scenario is a short conversation: ask the first question, then follow up with the next ones in the same chat. Swap in your own customers, dates and departments.

1. Monday production meeting

For production managers who need to know what's late, what's due and where the bottleneck is this week.

Which open jobs are past their required-by date? List them by customer with their WIP status and value.
Which of those are on hold, and which haven't had any time recorded in the last 5 days?
Show me the workload by department for this week and the next two, against what each department usually gets done.
Which department is most overloaded? List the jobs driving its demand this week.
Which jobs are due this week but still have more than half their steps to do?

Watch for: workload only counts steps with a planned time. Claude will tell you how many steps are due without one, because those hours are missing from the totals.

2. Weekly sales review

For sales managers and owners checking how the month is tracking.

What are our sales month to date, and how does that compare with the same point last month and last year?
Split that by account manager.
Which of our top 30 customers are down more than 20% on last year, year to date?
Which customers spent over $10,000 last year but haven't ordered in the last 90 days?
For those customers, when was our last sales call or note?

Watch for: "sales" means jobs by order date. Say "invoiced" if you mean invoices.

3. Following up quotes and leads

For account managers working out who to call.

Which quotes over $5,000 from the last 30 days haven't turned into an order yet? Show the customer, account manager and value.
What's our quote conversion rate by account manager for the last 6 months, by count and by value?
How many days does a quote usually take to become an order? Is it different for big quotes?
How many leads did we win and lose last quarter, and what were the main reasons for losing?

4. Chasing suppliers

For purchasing staff and production planners waiting on materials.

Which purchase order lines are late, by supplier? Only include lines expected in the last 60 days.
Which of those lines are for open jobs, and when are those jobs required by?
What materials do this week's jobs need that we haven't received yet?
How many goods receipts had rejected quantities last quarter, by supplier?
Who were our biggest suppliers last financial year by purchase order value?

Watch for: purchase order lines that were never received or closed in M-Power stay "late" forever, sometimes by years. Give a recent date range, as in question 1, or ask Claude to leave out lines more than 90 days late.

5. Delivery performance (DIFOT)

For operations managers reporting on delivery in full, on time.

What was our DIFOT each month this financial year? Split it into on time and in full.
Which customers had the lowest on-time rate last quarter? Only include customers with at least 10 jobs.
Which jobs were late last month, by how many days, and what work type were they?
Which jobs were only partly despatched last month?
What did we spend on freight each month, and what was the average cost per docket by carrier?

Watch for: "on time" means despatched on or before the required-by date, because dockets rarely record when goods arrive. Freight, courier and installation lines are left out of "in full".

6. Getting ready for a customer meeting

For account managers before a visit or review call.

Give me a summary of [customer] for the last 12 months: sales by month, top products, and how that compares with the year before.
What open jobs and open quotes do they have right now?
What was their DIFOT this year, and which of their jobs were late?
Summarise our notes and sales calls with them over the last 6 months.
Who uses their client portal, and which portal items have they stopped ordering?

Watch for: if the customer has branches, say whether you mean the whole group or one branch.

7. Month-end

For finance and owners closing off the month.

What did we invoice last month, excluding deposits, compared with what we took in orders?
Which jobs despatched last month haven't been invoiced yet?
What's the value of work in progress at the end of the month, by WIP status?
Show invoiced sales by profit centre for the financial year to date as a chart.

8. Staff time and utilisation

For production managers whose staff clock on and scan jobs.

What was each employee's utilisation last week (hours on jobs as a share of hours attended)?
Who missed a clock-off in the last two weeks?
How many hours did we record on each process last month, compared with planned?
Which jobs went most over their planned time last month?

Getting good answers

The more specific the question, the better the answer. A good question names a time period, a grouping and a filter.

Instead of	Try
How are sales going?	What were sales by month this financial year, compared with last year?
Who are our best customers?	Who were our top 20 customers by sales last quarter?
Are we late on stuff?	Which open jobs are past their required-by date, by department?
Show me purchasing	Which purchase order lines expected in the last 60 days are late, by supplier?

Use your own names. Customer, product, department and WIP status names work as they appear in M-Power.
Ask for a chart or a table. For example: "Show that as a line chart" or "Make a table I can paste into Excel."
Keep going in the same chat. Claude remembers the conversation, so "now just Queensland" or "only the jobs over $2,000" works.
Start a new chat for a new topic. Long chats on many topics get slower and less accurate.
Check figures you'll rely on. Claude can make mistakes. Ask "How did you work that out?" and compare important numbers with M-Power.
Ask for a summary to share. "Write this up as three bullet points for the management meeting" turns an answer into something you can send.

Definitions and limits

Updated overnight. Today's changes show up tomorrow morning.
Sales means orders. "Sales" is jobs by order date. "Invoiced" is invoices by invoice date.
Values are ex tax unless you ask for inc tax.
Financial years start in July. FY2026 is July 2025 to June 2026. Say "calendar year" if that's what you want.
Customer details are current. Account manager, industry and client class are today's values, not the values at the time of the sale.
Work in progress means jobs not yet despatched, closed or cancelled.
Results depend on how you use M-Power. If your team doesn't record something (clock-ons, job steps, planned times, purchase orders), Claude can't report on it. For example, a company that doesn't clock on will have no utilisation figures.
Not covered yet: stock on hand, costs and margins, and payments received.

If an answer looks wrong or something is missing, contact M-Power support.