Financial truth
Prepared exclusively for Hume Woodwork
Your business. One conversation away.
Proposed AI assistant · not active in this demo. The interactive dashboard shows sample business information. AI services will be activated only after client acceptance.
A proposed operations system that will combine Xero financials with production, labour, stock and job data—so every management number has a traceable source.
The outcome
Ask a question. Get the business context.
Andrew can ask what is holding up a cabinet job, who needs to follow it up and which invoice is affected. Hume OS will connect the relevant information into a clear answer, with source records available when he wants the detail.
How the dashboard becomes true
One view, built from four accountable sources.
A dashboard is only as reliable as the transactions behind it. Each tile will show its source and latest synchronisation.
Job truth
Operations platform
Quotes, job stages, materials, production, deliveries, callbacks and ownershipLabour truth
QR / NFC time capture
Clock-on, clock-off, hours by job, approvals and actual labour costMaterial truth
Stock & purchasing
Opening stock, receipts, allocations, consumption, shortages and reorder statusYour custom system
One connected system for every part of the job.
Tap each workstream to review the connected capability.
Controlled delivery
Five steps from a clear plan to daily use.
Start with the two-week Blueprint. The implementation is estimated at 16–22 weeks, with the final schedule and any overlap between stages confirmed in the Blueprint.
Blueprint — agree the plan
We sit down with you and follow a job from the first quote to the final payment. Together, we identify what takes too much time, what information is missing and what should connect.
- Your part
- Show us a typical job, your current spreadsheets and systems, and the questions you need answered each day. Introduce the team members and accountant who know the process.
- What you receive
- A written plan covering what we will build, what connects to what, the priorities, budget, delivery schedule and how you will check that it works.
You review the plan and approve a separate implementation agreement before the full build starts.
Prototype — try one job first
We create a small working example around one agreed job. We check that the proposed screens make sense and that the required Xero information can be connected with your permission.
- Your part
- Try the example with us and tell us what is clear, what is missing and what should change. Your accountant helps check the financial information.
- What you receive
- A reviewed example and an early check of the key connection, so we can resolve problems before building the rest.
We agree any changes to the workflow and confirm the approach before expanding it.
Build — create your system in steps
We build the agreed parts of Hume OS in manageable stages: jobs, production, costs, stock, time capture and the dashboard. We connect the agreed systems and set who can view or change information.
- Your part
- A nominated person from your team joins regular demonstrations, answers workflow questions and gives feedback as each part is ready.
- What you receive
- A working system with the agreed features and connections ready for your team to test together.
Any new ideas are reviewed with you for cost and timing before they are added to the agreed scope.
Prepare & test — check it with your team
We bring across the agreed starting information, such as customers, active jobs and stock. Your team tries everyday tasks from start to finish, and we fix issues found during testing.
- Your part
- Check the starting records, try the workflows you use each day and ask your accountant to confirm the financial figures and processes.
- What you receive
- Checked starting data, completed test results and an agreed checklist for going live.
You confirm the system is ready before we agree the switch-over date.
Launch & early support — start using it
We train your team and help move the agreed work into the new system. During the first days of use, we monitor the connections, answer questions and resolve launch issues.
- Your part
- Use the system for daily work, raise any problems and tell us where the team needs more guidance.
- What you receive
- Your team is using the system, knows how to get help and has clear instructions for the regular support service.
“Hypercare” simply means extra attention just after launch. After this period, support follows the separately agreed monthly service and coverage.
First commitment
Solution Blueprint
Start here: two weeks to understand how Hume works and agree a practical plan. You show us your current process; we document the features, connections, budget and delivery steps. You receive the plan before deciding whether to proceed with the full implementation.
The amount paid is credited against the Hume OS implementation when Hume proceeds with the full build.
Commercial clarity
What the blueprint must confirm.
- Exact Xero organisations, data objects and accountant sign-off
- Named internal users versus kiosk and portal users
- Opening stock, supplier catalogue and data migration quality
- CabMaster, AutoCAD and CNC boundaries or available interfaces
- Payroll, Arabic translation and native mobile-app requirements
- Hosting, support coverage, security and recovery objectives
Hume may be eligible to claim the GST component and obtain income-tax deductions or depreciation for software expenditure. Eligibility and timing must be confirmed by Hume’s registered tax adviser.
