I map the process, build the automation, and answer when it breaks
I’m Rami B., Automation Engineer at Slipwork. I work alone: one person maps how a business actually operates, builds the automation, and is still there when something goes wrong. There is no account manager relaying your problem to someone else, and no support queue between you and the person who wrote the workflow.
I build automation systems for SMBs that are already running: teams doing the work manually in spreadsheets, inboxes and CRMs, who want to grow without adding headcount. I work inside the tools already in use (HubSpot, Pipedrive, Airtable, Make, n8n, Zapier) rather than asking anyone to adopt something new. The three case studies below are what that has looked like in practice.
Most builds run between two and twelve weeks, shipped one process at a time, with scope and price agreed in writing before anything starts.
How I work
Report-only before anything writes
Every workflow logs what it would have done for a full week before it is allowed to touch anything live. We read the log together, and only then does it get permission.
Inside the tools you already run
HubSpot, Pipedrive, Airtable, Make, n8n, Zapier: whatever your team is already in. Switching tools is not part of the job I am selling.
Documented and handed over
You get the workflows and the rules behind them, documented well enough that your own team edits them, not me.
Recent work
Which part of your operation eats the most hours each week?
Tell us. You get a written answer on what to automate first, free, whether or not we ever work together.