Question 1

What exactly does TaskSmith automate?

Accepted Answer

TaskSmith automates operational workflows that currently depend on people moving information between documents, inboxes and business systems. That can include quoting, order entry, invoice processing, goods receiving, delivery paperwork, compliance documents and exception handling. We focus on a named bottleneck with a measurable consequence, not "AI transformation" for its own sake.

Question 2

How do I know which process to automate first?

Accepted Answer

Start with the process creating the clearest combination of repetitive work, errors, delays, risk, lost capacity or poor visibility. We assess the opportunity with your team and compare automation with simpler alternatives. If an SOP change, training, an existing feature or a ready made product is the better first move, we will tell you.

Question 3

Do I need to know exactly what solution I want?

Accepted Answer

No. Most clients begin with a frustrating operational problem rather than a technical specification. Bring us the bottleneck, a recent difficult example and the people who understand the work. We will help map what actually happens and determine whether there is a practical project inside it.

Question 4

What if our processes and SOPs are not properly documented?

Accepted Answer

That is normal. We sit with the people doing the work, follow real examples and document the triggers, decisions, exceptions and hand-offs. We expect to discover details during testing that were invisible in the first conversation, so the build process is designed to incorporate agreed refinements instead of pretending every rule was known on day one.

Question 5

Should we use an ERP feature or ready made product instead?

Accepted Answer

Sometimes. Ready made software is usually the right answer when the problem is common, the workflow is stable and the product fits without excessive compromise. TaskSmith is most useful when the bottleneck crosses several systems, involves messy documents or business specific rules, and generic software leaves people manually bridging the gaps.

Question 6

Does TaskSmith replace our ERP?

Accepted Answer

Usually not. Your ERP remains the system of record. TaskSmith works around and between the systems you already use, handling the repetitive collection, interpretation, checking, routing and entry that those systems do not handle well. The aim is to remove a painful workflow without forcing an organisation-wide replacement project. We want to derisk and extend the life of your ERP, not replace it.

Question 7

Can TaskSmith work with our ERP, even if it is old?

Accepted Answer

Often, yes. We do not need to have used every ERP previously, but we do need a dependable and authorised way to read or update the information involved. We have worked with older systems such as Opto/iTMS as well as newer platforms such as Odoo. Depending on the system, an integration may use a supported API, import or export, database access, an existing extension point or carefully controlled interface automation. If the route is uncertain, we can scope a small technical proof before committing to the whole workflow.

Question 8

What if our software does not have an API?

Accepted Answer

No API does not automatically mean no integration. We investigate supported imports and exports, database or reporting access, vendor extension points and controlled interaction with the existing interface. Interface automation can be more fragile when screens or logins change, so we will explain that trade-off and prove the route where necessary. We will not promise an unsafe or unauthorised connection merely to win the project.

Question 9

How does a TaskSmith project work?

Accepted Answer

We begin with the workflow and the result you want. We then map the current process, assess whether the opportunity is worthwhile, and provide a proposal. Once approved, we prepare a written module specification, build and test the workflow, deploy it for user acceptance testing, correct agreed issues, train the team and support the live system.

Question 10

How long does implementation take?

Accepted Answer

We aim to deliver a bounded first workflow in roughly four to six weeks once we have the required examples, access and decisions. Integration uncertainty, multiple departments, complex exceptions or delayed client feedback can extend that timeline. The module specification confirms the realistic plan before the detailed build proceeds.

Question 11

How much time will our team need to contribute?

Accepted Answer

We normally need a process owner, someone who performs the work, and an IT or software contact where integrations are involved. They help us understand real examples, answer rule and exception questions, and test the result. The involvement is concentrated around discovery, short review sessions and user acceptance testing rather than becoming another full-time internal project.

Question 12

Can we start with a small pilot?

Accepted Answer

Yes, and that is usually the best approach. We can begin with one workflow, document family, customer group or transaction type, then measure how it performs with real examples. This gives your team something concrete to evaluate before you expand into additional processes.

Question 13

Will implementation disrupt our live operation?

Accepted Answer

We design testing around controlled samples, review workflows, test environments or a limited live pilot wherever practical. Actions that could affect orders, stock, invoices or customers are agreed and tested before broader automation. Your existing manual process remains the fallback until the new workflow has earned the team's trust.

Question 14

What happens when AI is uncertain or makes a mistake?

Accepted Answer

AI is not treated as infallible. A TaskSmith workflow can apply confidence thresholds, validation rules and human review before sensitive actions occur. Straightforward cases can move automatically while missing, conflicting or unusual cases are routed to the right person to review, edit, approve, reject or hold.

Question 15

Will automation replace our staff?

Accepted Answer

The objective is normally to remove repetitive workload and release capacity, not remove the people who understand the business. Staff still handle customers, judgement, negotiation, improvement and unusual cases. Involving the people who perform the work also produces a better system and makes adoption much more likely.

Question 16

How secure is our data?

Accepted Answer

Security is designed around the risk of each build. Controls can include encrypted connections and storage, multifactor authentication, access based on roles, tenant separation, audit history and restricted administrative access. We use OWASP guidance and consider applicable Australian Privacy Principle obligations. TaskSmith does not currently claim an independent certification such as ISO 27001 or SOC 2, so we will state our controls and any material limitations plainly rather than imply a certification we do not hold.

Question 17

Will AI providers use our business data to train their models?

Accepted Answer

We disclose the AI, OCR and cloud providers proposed for each build and do not intentionally send operational data through consumer chat accounts. Commercial API providers commonly exclude API data from general model training by default, but retention and processing terms differ by provider and feature. Where required and available, we can design around stricter retention controls, eligible zero data retention arrangements or privately hosted models. The exact data path is documented for your build.

Question 18

Where is our data hosted, and can the system run inside our network?

Accepted Answer

TaskSmith controlled application infrastructure is hosted in Australia. Some external AI or cloud processing may occur overseas unless the project is specifically designed for processing only in Australia. Where the risk warrants it, we can assess deployment in an Australian cloud, private cloud or client network. Those options can change the available models, implementation cost and support model, so they are agreed during scoping rather than assumed.

Question 19

What happens after launch, and what if we stop using TaskSmith?

Accepted Answer

After launch, support can cover failed processing, access issues, bug fixes, exception routing problems and minor tuning within the agreed workflow. New modules, major rule changes or new integrations are scoped separately. Your business data remains yours. TaskSmith retains its underlying platform and client configuration under the current standard model, and the applicable agreement defines your licence, export period, retention and deletion arrangements if the service ends.

Question 20

What does a TaskSmith project cost, and how do you estimate the return?

Accepted Answer

Cost depends on the workflow, integration route, exception complexity, operational risk and expected processing volume. A typical engagement separates the initial build from ongoing hosting, processing, maintenance and support. Before recommending a build, we assess the likely value across staff capacity, errors, delays, risk, service, revenue and management visibility so the project is tied to a business result rather than a list of software features.

Turn Hours of Manual Work Into Minutes

TaskSmith puts a software engineer inside your business to build custom automation around the way your team actually works. If your team isn't saving measurable time in 30 days, we'll work for free until they do.

Answer two quick questions before booking a workflow chat.

How it works

Discovery

Build

Continuous Improvement

Hear From Businesses Like You

Quote Assistant

Proof of Delivery

Delivery Dockets & Test Certificates

TaskSmith started inside the operation.

The team

Robbie Newton

Duncan Fekete

Moon Dog

Start the conversation.

Answer two quick questions before booking a workflow chat.