About
You work directly with me, start to finish.
I'm Ayantu Regassa, an engineer and software developer. Regassa Automations is my independent practice: there is no account manager or hand-off to a junior team. The person who asks about your process is the person who builds and documents the system.
I'm Ayantu Regassa, an engineer and software developer. Regassa Automations is my independent practice: the person who asks about your process is the person who builds and documents the system.

How my background shapes the work
Engineering
I trained as an engineer at MIT. That training shows up as a habit of mapping a system completely, including the inputs nobody mentions, before changing any part of it.
MIT-trained. I map a system completely, including inputs nobody mentions, before changing any part of it.
Software development
I have more than seven years of software engineering experience, much of it building workflow automation in Python and Google Apps Script for real teams with real constraints.
More than seven years of software engineering, much of it workflow automation in Python and Google Apps Script.
Patent technical work
As a patent technical specialist, I read dense technical material and described exactly what a system does and does not do. I apply the same precision to your business rules and their exceptions.
Describing exactly what a system does and does not do. I apply the same precision to your rules and exceptions.
Project approach
From discovery to handoff
01 · Discovery
Understand the process
Conversations with the people who do the work, plus a look at the real files and tools.
Talk with the people who do the work; look at real files.
02 · Definition
Rules and exceptions
A written description of the rules, edge cases and the decisions that stay with your staff.
Written down, including which decisions stay with staff.
03 · Build
Build and review
Built in stages and reviewed with you against realistic cases before anything goes live.
In stages, reviewed against realistic cases.
04 · Handoff
Document and hand off
Documentation your team can follow, and support terms agreed for the engagement.
Documentation your team can follow; support terms agreed.
Tools and capabilities
Listed separately so it is clear what I have used in delivered work and what would be new for a given project.
Used in delivered work
Possible future integrations
Other systems with a usable API or export, such as CRMs, accounting tools or practice-management software. These are assessed during discovery, not assumed.
Other systems with a usable API or export, assessed during discovery rather than assumed.
Start with a short description
Tell me what the process is and what is frustrating about it. I'll reply personally.