Cloud services and automation

Make your technology work together and reduce repetitive work

If your team copies the same information between apps, chases the same reports every week, or has cloud services nobody fully understands, there's usually a simpler way. I find it, set it up, and document it.

Tell me what you need Call or text (864) 702-8223

Connecting the apps you already use

Most small businesses already pay for good tools. They just don't talk to each other. Common examples:

A website form that adds the lead to a spreadsheet or CRM and notifies you right away
Invoices or payment links sent automatically when a job is marked complete
Follow-up emails or appointment reminders that go out on their own
New-employee setup steps that happen in the right order every time

Where an existing service like Zapier or Make does the job, I'll use it. It's quicker to set up, easier for you to see and change, and doesn't depend on me. Any subscription it needs is in your name.

Scripts and Microsoft cloud automation

Some jobs are better handled with a script, especially in Microsoft 365: adding and removing employee accounts consistently, regular reports on licenses, sign-ins, or mailbox sizes, and routine checks that would otherwise be done by hand. PowerShell automation is something I've done extensively in enterprise IT. I write custom scripts only when there's a clear reason to, and you get the script and notes on how it works.

AWS setup and troubleshooting

For businesses that already use Amazon Web Services, or need to, I can help with:

Setting up and configuring AWS services sensibly from the start
Troubleshooting things that stopped working or never quite did
Reviewing who has access (IAM), security groups, and other security settings
Selected infrastructure improvements, including repeatable setups with Terraform where that makes sense
Practical monitoring, logging, and alerts, so problems get noticed

This draws on my enterprise work with multi-account AWS environments. It's project work. I don't offer 24/7 cloud operations or a security operations center.

Approach

The simplest thing that works

Automation is only useful if you can keep relying on it. That shapes how I build it.

Start with the task

What takes time, how often, and what goes wrong when it's done by hand. Sometimes the answer is a setting you already have, not a new tool.

Prefer managed tools

Existing services and built-in features first. Custom code only when it's clearly the better option, never to make the solution sound impressive.

Build it to be handed over

Accounts in your name, clear notes on what runs where, and nothing that only I can understand.

FAQ

Automation and cloud questions

I don't know what could be automated. Can you help?

Yes. Describe a normal week and the tasks that feel repetitive. On the free call I'll point out what's worth automating and what isn't.

Do you build custom software?

Not as a software development shop. I write scripts and small integrations when they're the right fit, and I use modern coding assistants to help write and test them. For a full custom application, you'd want a dedicated developer, and I'll say so.

Do you manage AWS around the clock?

No. I help with setup, configuration, troubleshooting, and specific improvements as projects. If you need 24/7 operations or security monitoring, I'll tell you what kind of provider to look for.

What happens if an automation breaks later?

You'll have notes on how it works, so you or someone else can check it. I'm also available for fixes as a quoted job or as part of scheduled support.

Tell me what you're trying to accomplish

New setup, something to fix, or just a question about what makes sense. The first 15-minute conversation is free, and I reply within one business day.