HANDSOME TOAD
Business automation FAQs
Answers about custom software, client portals, business-system integrations, AI workflows, maintenance and working with Handsome Toad.
Do you work beyond Google Workspace?
Yes. Our work includes custom web applications, client portals, serverless services and API integrations. Google Workspace is one option, rather than a boundary. Explore the Essiettson Farm workflow for a client example that connects staff badges, business documents and AI document extraction.
What does Handsome Toad help businesses automate?
We build custom web applications, client portals and automation for enquiries, documents, reporting and operations. We connect existing business systems through supported integrations and APIs, choosing the technology around your process, data and access requirements.
Do we need to replace all our current software?
Start by describing the tools you already use. A focused integration or workflow improvement may be enough. Some requirements need a different platform or additional services; we explain those choices before agreeing the work.
Can AI make decisions without anyone checking?
AI can assist with tasks such as drafting or classifying information, but it can make mistakes. We agree which actions can be automated and which require a person’s approval, especially where an error would affect a customer or business decision.
How much does an automation project cost?
The price depends on the process, integrations, data migration, testing and support needed. Share a description of the problem so we can establish scope and provide an appropriate proposal. Third-party subscriptions or usage charges should be considered separately.
How long will implementation take?
We establish a delivery plan after reviewing the requirements, access, dependencies and acceptance criteria. There is no fixed delivery promise for every project.
What happens when an automated step fails?
Exception handling is part of workflow design. Depending on the project, this may include a visible status, an alert, a safe retry or a manual recovery step. We agree how failures are monitored and who is responsible for follow-up.
Can you maintain the system after launch?
Discuss maintenance, monitoring and changes during scoping so responsibilities and ongoing costs are clear. Support arrangements depend on the agreed engagement.
What information should I provide first?
Describe the process, the people involved, the tools used, the repeated problem and the outcome you want. An anonymised example is useful. Do not send passwords, customer databases or unnecessary personal information through an initial enquiry.
Start a business automation enquiry. For job-search support, visit the separate Career Concierge FAQs.
When is Google Apps Script a good fit?
Assess workload, data sensitivity, integration support and required availability before choosing a platform. Apps Script has execution and service quotas; larger or more demanding workflows may need another architecture. Start with Plan your enquiry workflow rather than assuming every process belongs in a spreadsheet.
Who will own the accounts, code and documentation?
Agree account ownership, code rights, integration access and documentation in the proposal before work starts. Identify who can administer the workflow after handover and how access will be transferred or withdrawn. Do not assume that access to a working demo establishes ownership.
What access or data should we provide?
First share an anonymised process example and the tools involved. The implementation needs an agreed access plan covering necessary permissions, authorised users and data handling. Do not send passwords or a customer database through the initial enquiry form.
What ongoing costs should we budget for?
Ask for an itemised view of software licences, API usage, hosting, monitoring and maintenance that apply to the proposed design. A build fee alone does not describe running costs. Usage limits and responsibility for alerts should be agreed before launch.
What makes a sensible first automation project?
Choose a repeated process with a clear owner, known inputs and a measurable problem. Record the present handling time or error rate, identify exceptions and agree acceptance checks. A small pilot can reveal data and access issues before a wider rollout.
What should be agreed for handover and future changes?
Define acceptance criteria, the workflow map, access arrangements, recovery instructions and documentation in the agreed scope. Name the person responsible for operation and agree how support and later changes are requested and priced. These details belong in the proposal or agreement.
Your next step
Ready to review a process? Request an assessment using your contact details and the relevant pain points. Detailed scope, costs and timing are agreed separately.