BarbagalloDigital

Custom business automation

Stop being the glue between your tools.

Most small businesses don’t need to replace their software. They need the systems they already pay for to pass information along, without someone retyping it. I find where work gets copied by hand, then build and test the connections, and any small tools that fill the gaps, in your own accounts.

Custom quote Quoted after a conversation, for any tool or path I haven’t tested.

Where the copying happens

Six jobs that eat time in a small business, and what each one becomes once your tools are connected.

The copying moves to the tools. The customers stay with you.

Here’s what a connected job can look like, step by step: which steps run on their own, and which stay yours.

One enquiry, followed through

  1. Start: An enquiry arrives through your website form
  2. Automatic: It becomes a row in your enquiry sheetName, job, town and message, each in its own column.
  3. Automatic: You get an email with the details
  4. You: You call back and send the quoteMarked “quoted” in the sheet, with the date.
  5. Automatic: No answer after the days you set? It’s flaggedA follow-up draft waits in Gmail. You decide whether to send it.
  6. You: You win the job and mark it done
  7. Automatic: It goes on the to-invoice list
  8. Automatic: Friday’s report counts itEnquiries, quotes, wins and what’s waiting, emailed to you.

If any automatic step failsAn error email to you, so a broken step doesn’t sit unnoticed.

Illustrative An invented example of the kind of workflow I build, not a client’s system. Each job is scoped to your tools and quoted.

What I build with, and what it isn’t

Every job is a custom quote. Quoted after a conversation, for any tool or path I haven’t tested. Automation monitoring is planned, not available yet.

Tools I connect

  • Documented APIs and webhooks: CRMs, job, accounting and booking software
  • Custom code where no connector fits: scripts, scheduled jobs, small web tools
  • Databases, spreadsheets and file imports, cleaned and kept in sync
  • Often used: WordPress forms, Formspree, Google Workspace, Zapier and Make

What it isn’t

  • No chatbots, and nothing that makes decisions on its own.
  • No forced move to new software. Anything new I build is small, documented and yours.
  • No estimate of hours saved. Nobody can honestly measure that in advance, so I don’t claim it.
  • Nothing in my name. It runs in tools and licences you own, with access you can remove.

Is it worth automating?

A quick test before you write to me. Most good candidates tick three of the first four.

Good candidates

  • It happens every week, or more often.
  • The steps are the same each time.
  • The information is already typed somewhere once.
  • A slip costs money: a lost enquiry, a late invoice, a missed follow-up.

Probably not worth it

  • It happens a few times a year.
  • Each case needs your judgement.
  • One of the tools has no way in: no API, no integration or connector, no database or file access.

How a custom job runs

From your first message to handover. The standard terms in full.

  1. Tell me about the work

    Through the contact form: what gets copied by hand, between which tools, and who does it now. No preparation needed.

  2. Discovery

    For one simple workflow, a 15-minute call or a few emails is enough to scope it. For anything bigger, a paid automation audit maps your tools and picks the three workflows worth doing first, each with a price.

  3. A written quote

    The scope, the tools and licences you pay for, the access I need, a target date and the checklist we’ll use to agree it’s done. A fixed price, or hours at $125 an hour against a cap you approve. You accept by reply.

  4. Built in your accounts

    Jobs under $1,000 are paid in full before work starts. Then you grant access you can remove later. Anything outside the scope is priced and approved in writing before it’s done.

  5. Tested end to end

    Recorded test runs with sample data, checked against the checklist, and a deliberately broken run to show the error email arrives.

  6. Handover

    A one-page map of how it works, the permissions it uses and how to switch it off. You have 7 days to report anything that doesn’t match the checklist, and it’s fixed at no charge.

Questions

Something else? Send me a message.

What does a custom automation cost?

It depends on the tools and the steps, so each job is quoted in writing before any work: a fixed price for a defined workflow, or hours at $125 an hour against a cap you approve. Bespoke software and multi-system integrations have a $995 minimum. Tool plans and plugin licences are yours, and the quote lists them.

Do I have to switch software?

No. The point is to connect what you already use. If a tool has no way in, the quote says so and suggests a workaround, or leaves that step out.

My software isn’t on your list. Can you still connect it?

Often, if it has a documented way in: an API, webhooks, a database you can grant access to, file imports, or a Zapier or Make connector. Anything I haven’t worked with before is quoted after a conversation and a look at its documentation, and checked end to end before handover. Where it isn’t clear, a connection test of at most 4 hours and $500 comes first and ends in a written go or no-go. If there’s no way in, the quote says so.

Can you build something new, not just connect tools?

Yes, when nothing you already use fits: a small internal web tool, a form with its own logic, or a script that processes your records on a schedule. It’s scoped, quoted and documented like any other job, and runs on accounts in your name. The software I’ve built and run myself is on the work page.

What happens if it breaks later?

Where the tools allow it, a failed run sends you an error email. A repair is quoted when you need one. Ongoing monitoring is planned, not available yet.

Can it email my customers?

Most jobs keep you in charge of what customers receive: drafts you review and send yourself. A fixed message sent automatically is quoted only if your tools support it and the trials show it arrives.

Who can see my data?

It stays in your own tools. I use access you grant for the job, and you can remove it whenever you like. The handover note lists every permission the automation uses.

Can I see your work?

The example on this page is invented. One client automation project is written up without the client’s name or details, linked below. My own projects, and how I build and test them, are on the work page.

A client automation project, written up without the client’s name or details: lead tracker automation. My own projects, and how I build and test them: the work page.

Tell me what gets copied by hand.

A few lines are enough: the job, the tools, who does it now. I’ll reply with whether it fits and what a quote would need.

Quoted in writing first.

Describe your workflow