Kori StroudOperations automation
Available

Services

Automation help for teams drowning in manual steps

I work with small operations, sales, and back-office teams whose day runs on spreadsheets, browser tabs, and copy-and-paste. The best first project is one bounded workflow with a visible owner and a costly failure mode.

The starting point

Automation Fix Sprint

One painful workflow, fixed scope, no long commitment. This is the low-risk way to find out what working with me is like — and whether automation is even the right answer for your process.

  1. You bring one workflow

    A repetitive spreadsheet, CSV, browser, reporting, or copy-and-paste task. A screenshot and a short description are enough.

  2. I map it and build the fix

    I document how the work actually flows, then build the smallest tool that removes the drag — using sanitized or synthetic test data.

  3. You get a working result

    The automation or repair itself, test evidence showing it behaves, and plain operating notes so your team can run it.

If your workflow isn't a responsible fit for a small sprint — too risky, too entangled, or better solved without software — I'll tell you before any paid work begins.

Beyond the sprint

Three ways I typically help

01

Workflow Automation Assessment and Quick Win

Map one repetitive process, find the highest-value failure point, and deliver a working fix or an implementation-ready plan.

Good fit if
Teams with one repetitive, failure-prone process and a clear operator who owns the outcome.
You receive
A workflow map, a prioritized quick win, and a tested fix or an implementation-ready plan.
Where I draw lines
I don't take on vague transformation programs, and I don't touch production systems before scope, data handling, and approvals are agreed.
02

CRM/Data Cleanup and Operational Reporting

Turn inconsistent exports into validated, deduplicated data you can review — plus reports you can rerun.

Good fit if
Operations teams working around inconsistent CRM exports, duplicate records, and manual reporting.
You receive
Import mapping, validation rules, duplicate candidates you can review, an audit trail, and exports you can rerun.
Where I draw lines
No silent merges, no opaque lead scoring, and no writing back to your CRM or contacting anyone without a separate, explicit agreement.
03

Public-Data Monitoring or Browser Workflow Automation

Careful collection and browser-assisted workflows that keep sources traceable, permissions minimal, and approvals human.

Good fit if
Teams repeatedly collecting legitimate public information or doing structured browser work by hand.
You receive
A source and permission review, a bounded collection or browser workflow, visible failure states, and human review points.
Where I draw lines
No scraping restricted data, no evading access controls, and no automatic submissions — a person always makes the consequential move.

Working principles

Useful before clever.

  • Start narrow.Define the smallest useful workflow and agree on what "done" means.
  • Keep changes explainable.Source context, reasons, and history stay visible in the output.
  • Keep judgment human.Consequential actions wait for explicit review and approval.
  • Earn complexity.The predictable version has to be valuable before AI gets added.

Next step

Start with the workflow, not a technology wish list.

Tell me what the process is and where it hurts — I'll tell you honestly whether it's worth automating.

Go to contact kori@tradeopsdata.com