Workflow automation consulting

Workflow automation for complex, everyday operations.

I turn disconnected spreadsheets, manual handoffs, and complicated business rules into reliable systems, so your team spends less time moving information and more time using it.

  • Operational applications
  • Integrations and data sync
  • Reporting and AI-assisted workflows
Client Route Manager table for a fictional customer listing six FCL and LCL routes with origin, destination, routing, container sizes, carrier and match status, including one unmatched route.
Fictional demo data Route review screen from the logistics rate-sheet application. Routes, carriers and rates are invented.Logistics rate-sheet demo.

Selected work

Systems built for real operational processes

See all five projects
  • First page of a generated rate sheet for a fictional customer, with validity dates and container prices.
    Operational application

    Logistics rate sheets

    Matches requested routes to cost data, applies pricing rules, holds exceptions for review, and generates a client-ready PDF.

    Matches routes to cost data, applies pricing rules, holds exceptions for review, and generates a PDF.

  • MasterClient AClient BClient C… about 30
    Integration and data sync

    PR pipeline sync

    Publishes a PR agency's opportunities from one master pipeline to about 30 client trackers, and keeps each one current until coverage is secured.

    Publishes a PR agency's opportunities from one master pipeline to about 30 client trackers.

  • GridBloom dashboard with headline electricity figures above demand and generation charts.
    Reporting and AI-assisted workflowReporting and AI-assistedIndependent project

    GridBloom electricity data

    A data pipeline, dashboard and weekly report that withhold figures the data can't support, with an AI briefing whose every number is checked.

    A pipeline, dashboard and weekly report that withhold unsupported figures, with a checked AI briefing.

See all five projects

Problems I work on

Does any of this sound like your week?

Each of these is a process that works, but only because people keep it working by hand. Each links to the service and a project that addresses it.

Services

Three kinds of work, often combined

  • Operational applications

    Small, purpose-built tools that hold your business rules, so the process does not depend on who is in the office.Purpose-built tools that hold your business rules, so the process does not depend on who is in the office.

    Addresses

    • Rules kept in personal spreadsheets
    • Documents assembled by hand
    • Exceptions handled from memory
  • Integrations and data synchronization

    Connections between the tools you already use, with reconciliation so you can see what changed and what needs a decision.Connections between the tools you use, with reconciliation so you can see what changed.

    Addresses

    • Repeated data entry between systems
    • Records that drift out of sync
    • Duplicate records from several sources
  • Reporting and AI-assisted workflows

    Dashboards fed directly from your sources, and, where it helps, a language model that drafts research or summaries for a person to check.Dashboards fed from your sources, and model-drafted summaries that a person checks.

    Addresses

    • Reports rebuilt by hand each week
    • Figures scattered across exports
    • Recurring research and summary writing

How a project runs

Process first, software second

  1. 01

    Understand the process

    I learn how the work actually runs today, who touches it, and where it slows down.How the work really runs, and where it slows down.

  2. 02

    Define rules and exceptions

    We write down the rules, the edge cases, and which decisions stay with your staff.Which decisions stay with your staff.

  3. 03

    Build and review

    I build in stages and review each one with you against real or realistic cases.In stages, against realistic cases.

  4. 04

    Document and hand off

    You get written documentation of how it works and how to change it.Written documentation of how to run and change it.

Scope, deliverables and any ongoing support are agreed in writing for each engagement before work begins.Scope and any ongoing support are agreed in writing for each engagement.

What clients say

Five-star reviews on Upwork

See these reviews on Upwork(opens in a new tab)

“If your systems feel like a tangled plate of spaghetti and you’d rather have a neat picket fence, this freelancer is for you.”

★★★★★Client, verified Upwork review · Volunteer registration and rostersVolunteer rostersRead the full review
  • “Super responsive/communicative. Fantastic to work with.”

    ★★★★★Client, verified Upwork reviewClient · Lead intake dashboards
  • “Amazing to work with, she went above and beyond. She far exceeded my expectations.”

    ★★★★★Client, verified Upwork reviewClient · Quotes library
See these reviews on Upwork(opens in a new tab)
Ayantu Regassa, founder of Regassa Automations

Who you will work withWho you work with

I'm Ayantu Regassa

I'm an engineer and software developer. Earlier in my career I worked as a patent technical specialist, where the job was reading dense technical material closely and describing exactly what a system does. I bring the same care to your operations: I learn the process, including its exceptions, before I write any code.

Regassa Automations is just me. You work with me directly, from the first conversation to the handoff.

An engineer and software developer, formerly a patent technical specialist. I learn your process, including its exceptions, before I write any code. You work with me directly, from first conversation to handoff.

More about my background and approachMore about my background

Discuss your workflow

Tell me about a process that takes too much of your team's time.

A few sentences is enough. You do not need to know what the solution looks like.A few sentences is enough. I read every inquiry myself and reply if it looks like a fit, or tell you if it is not.

Prefer to pick a time? Book a free consultation (opens in a new tab).

What happens next

  1. I read every inquiry myself.
  2. If it looks like a fit, I reply to arrange a short conversation about how the process works today.
  3. If it is not a fit, I tell you so, and suggest a direction where I can.

Inquiry form

What happens today, and what is frustrating about it.

For example Google Sheets, a CRM, email.

For example weekly, two people in operations.

I use these details only to reply to your inquiry. See the Privacy page for how submissions are handled and how to ask for one to be removed.Used only to reply to you. Privacy

Discuss your workflow