Huber BuildsWebsites & automation
Menu

Workflow automation.
Less repeat work.

Connect your tools so recurring paperwork, emails, and data entry take less of your day.

Based in Edwardsville, Illinois. Automation for nearby businesses, the St. Louis area, and teams nationwide.

Talk about a repetitive task

Real client workflow · VEST First Responder

The class ends.
The certificate follows.

I connected VEST’s post-training paperwork using Google tools. Each participant gets a certificate matched to their training level.

  1. Complete a form

    Name, email, and training level.

  2. Collect the details

    Responses arrive in a Google Sheet.

  3. Create the certificate

    A script personalizes it for the participant’s level.

  4. Send it by email

    The participant receives their certificate.

A repeatable process for every class, without preparing and emailing each certificate by hand.

Talk about a workflow like this

Workflow automation project

One time-consuming, repeatable process

Starting at $1,500

USD · one-time project

  • One workflow with agreed inputs & outputs
  • A script or integration with failure checks
  • Testing with agreed sample cases
  • Setup, source files & operating notes
Get a project estimate

Assumes tool access and sample data. Your quote fixes the scope and price; ongoing monitoring and support are separate.

Ownership, support & quotes

Built for everyday use.

  1. Plan

    Agree the inputs, rules, and result.

  2. Connect

    Build around the tools your team uses.

  3. Test

    Check real samples and agreed failure cases.

  4. Hand over

    Provide setup, source files, and operating notes.

Your quote defines the tools, rules, outputs, and exceptions. Extra workflows and paid services are separate.

Timing & your part.

About 1–2 weeks

For a small, defined workflow. I confirm timing after reviewing your tools and sample data.

Try an early version

Review a working version, refine it, and check the agreed test cases before handover.

Your part

Share your goals and materials, send one feedback list per revision round, and give final approval. Rough notes are fine to start.

Your quote confirms scope, revisions, price, payment terms, and dates. Larger projects, missing materials, or slower feedback can extend these estimates.

What to provide for automation
  • The repeated task, its steps, frequency, and bottlenecks.
  • Your apps or spreadsheets and what needs to move between them.
  • Samples with private details removed, the desired result, and exceptions.
  • Who uses the result and who can arrange tool access.

A walkthrough or screenshots help. We agree access and test cases during planning.

Try the interactive sample Clean up six fictional enquiries
Try one small step

Turn a messy enquiry list into a useful follow-up list.

This sample shows the input checking that can sit inside a larger workflow. Try it with six fictional contacts: tidy the formatting, catch duplicates, and flag missing details.

Before

6 sample enquiries
  1. 1
    Alex Rivera ALEX.RIVERA@example.com
  2. 2
    Rowan Kimrowan.kim@EXAMPLE.COM
  3. 3
    Sam Taylor sam.taylor@example.com
  4. 4
    Alex Riveraalex.rivera@EXAMPLE.COM
  5. 5
    Parker JordanEmail missing
  6. 6
    Casey Morgan CASEY.MORGAN@example.com

After

Follow-up list

Run the sample to see the cleaned list.

Checks formatting and exact email duplicates, not whether an address can receive mail. Missing details stay flagged.

Illustrative sample data, processed in your browser. No uploads or network requests.

Other possibilities: enquiry handoffs, recurring data imports, and monthly reports.

My software experience