AI consulting that starts with
your business problem
Amulet helps Australian businesses assess a workflow and decide what to do next. Consider existing software, then agree what work is needed before committing to implementation.
Bring one difficult workflow and a non-confidential summary.
Diagnostic first. Implementation by separate agreement.
We recommend starting with one recurring task. Name its owner and record how it works today. Use that baseline to decide whether a process change, existing software or a scoped build is worth testing.
Workflows we can assess and scope
These are examples of work to assess, not packaged products or promises of prebuilt integrations.
Start with the AI Business BEEP
Use the paid diagnostic to decide what to do next. Any implementation is a separate commitment.
Problem-fit conversation
Bring one recurring problem and a short, non-confidential summary. The first conversation tests whether a deeper review would be useful.
Paid diagnostic
The AI Business BEEP is a paid diagnostic. Agree its scope before work begins: the workflow, systems, feasibility, controls and recommended first step.
Separate implementation decision
Implementation is a separate decision. You can proceed with a defined scope, change the process, build internally, choose another partner or decide not to build.
Scoped support
Where useful, ongoing support can cover adoption, evaluation and improvement within an agreed operating scope.
The first conversation tests fit; it does not commit you to implementation.
Questions to ask before a build
Could existing software do the job?
Check the features and rules in software you already use before commissioning a custom AI workflow.
Who handles an exception?
Name the person who reviews missing inputs, conflicting evidence or an output that should not proceed.
How will you decide whether it works?
Agree representative test cases and acceptance criteria. Include review effort and recovery, rather than measuring speed alone.
Scope the work with 
Ask for evidence about the proposed systems, security controls and data handling.
Data and hosting requirements
Identify what information the workflow may use, where it may be processed and who may access it. Hosting and data residency depend on the agreed implementation and validation.
Confirm the proposed data flowSecurity requirements
Bring your security requirements into scoping. Agree and validate controls for the proposed systems; a service description is not evidence that those controls are in place.
Review implementation-specific evidenceHuman responsibilities
Define who approves outputs, resolves exceptions and owns the workflow after launch. Agree the review and recovery path before increasing its scope.
Keep approval and ownership explicitAsk about your workflow
Send a short, non-sensitive summary, or request a problem-fit call.
Leave confidential names, files and data out of your enquiry.