Less friction
A workflow should reduce repeated entry, unclear handoffs, and quiet failures without forcing your team to replace every tool it already knows.
Available for new projects · Remote worldwide
I make the systems you already use work together.
I’m an IT systems & automation consultant for lawyers and small businesses. I connect the tools your team already relies on, replace repetitive handoffs with dependable workflows, and add AI only when it has a clear, controlled job. Every build comes with safeguards, documentation, and a plan for support.
Practical systems integration
Human review where it matters
Documented and supported
● Start with a general, non-confidential description · typical reply within one business day
See the method: scope, test, document, supportTriggerwebhook · event
Validatefields · auth
Processtransform · enrich
Deliverwrite · notify
Audit LogPII-masked
Fallbackon error · retry
How it feels
The same work, repeated. One dependable workflow.
scroll to see scattered steps become one clear workflow
What a dependable workflow includes
Connected
Reviewed
Human approval stays in the workflow where judgment matters.
Visible
Failures are logged, surfaced, and given a recovery path.
Clear
Your team gets useful documentation and knows who owns the next step.
- Understand the process before choosing the automation
- Fit the solution to your existing systems and team
- Use rules for predictable work and AI only where it helps
- Plan for monitoring, recovery, and support from the start
Is a routine process taking more attention than it should?
Discuss the workflow →The math
What could a repetitive process be costing you?
Use the calculator to estimate the labor tied up in one repeated process. It is a planning aid, not a promise of savings.
10h
$50
Estimated manual-work cost · yearly
$0
Estimate based on the inputs you selected
Team capacity represented0x
Five-year equivalent$0
Talk through the process →
● Start with a general, non-confidential description
Prefer to start by email? Send a general workflow outline →
Who I help
For teams that need their systems to be dependable.
Most clients do not need another app. They need the tools they already pay for to exchange the right information, at the right time, with clear ownership when something needs attention.
Law firms
Intake, follow-up, document, billing, and reporting steps need to stay organized without exposing confidential information or removing human judgment.
Safer handoffs and clearer accountability →
Small businesses
Sales, scheduling, billing, and customer updates often span several tools and depend on someone remembering the next step.
Connected systems and less repeated work →
Operations teams
Existing automations work on the happy path but fail quietly when data is incomplete, a vendor changes something, or an approval is needed.
Monitoring, recovery, and support →
Who you'd be working with
Hi, I’m Lorenz. I make business systems easier to run and easier to trust.
Available for new projects
I’m an IT systems & automation consultant who helps lawyers and small businesses connect the tools they already use. I start by understanding the process, the people responsible for it, and the exceptions that cause trouble. Then I build the smallest dependable solution that solves the problem.
Every build includes the safeguards the work calls for: validation, retries, approval steps, logging, and recovery paths. I document what was built, explain how it is operated, and can stay involved for monitoring and ongoing improvements.
My background includes enterprise Microsoft Cloud, multi-tenant IT, and marketing automation for Le Cordon Bleu International. That experience shapes how I approach access, reliability, change control, and support for smaller teams.
n8n Level 2 Certified
AWS Cloud Practitioner
Azure AZ-900
Make & Zapier Certified
GitHub Foundations
Lorenz Leslie EspinosaIT Systems & Automation Consultant · remote worldwide
Designed around your environment
I work with the systems you already use and recommend self-hosting only when it improves privacy, control, cost, or reliability for your situation.
Observable and recoverable
Important actions can be logged, sensitive data can be masked, and failures are surfaced with a defined way to recover.
Clear ownership after launch
You receive documentation and a practical handover. Ongoing monitoring and support are available when your team would rather not maintain the workflow alone.
Representative work
The kinds of systems I build.
These examples show the work behind a dependable automation: connecting existing tools, keeping important decisions reviewable, and making failures visible instead of letting them disappear.
Approval-gated
View the public stack →
AI assistance inside an existing team channel
A controller routes requests to specialist tools while keeping consequential actions behind human approval. Predictable tasks stay rule-based, and AI is limited to work that actually needs interpretation.
Controlledclear permissions and approval points
Slack · n8n · MCP · AI assistants
▸ See the situation → approach → outcome
Systems integration
See the public templates →
Structured intake across phone, forms, and CRM
New inquiries are validated, routed, and written to the right system without asking staff to re-enter the same information. Exceptions are held for review instead of being guessed at or dropped.
Connectedone intake path across several tools
n8n · phone · web forms · CRM
▸ See the situation → approach → outcome
Human in the loop
Lead triage with review before outreach
Rules handle routing and required fields. AI can help summarize or draft, but a person stays responsible for decisions and outbound communication where context matters.
ReviewableAI assists without owning the decision
n8n · CRM · constrained AI
▸ See the situation → approach → outcome
Business-critical
View the public toolkit →
Billing and case-system reconciliation
Deterministic rules keep records aligned, flag conflicts, and preserve an audit trail. Money-related steps do not rely on a model to decide what is correct.
Traceablerules, logs, and exception handling
n8n · case management · billing · Airtable
▸ See the situation → approach → outcome
Have a process like one of these?
Discuss the workflow →From the Blog
Notes from the work.
Plain-language articles about dependable automation, responsible AI use, and what changes when a workflow has to survive outside a demo.
The token tax is real
Why autonomous agents can cost much more than a chat request, and when running part of the stack yourself may make sense.
Read the article →Schema markup will not get you cited by AI
Schema helps machines understand a page, but clear answers, consistent entities, and sourceable claims do more of the real work.
Read the article →Which automations actually mattered?
The useful systems were rarely the flashiest ones. They reduced repeated work, closed gaps, and made exceptions easier to handle.
Read the article →Open source
Public examples of how I build.
These repositories show some of the patterns I use for validation, approvals, retries, recovery, and audit trails. They are technical proof for anyone who wants to look under the hood, not a requirement for working with me.
openclaw-n8n-stack★ 2
One-command Docker stack, OpenClaw AI agent + n8n + PostgreSQL, with MCP pre-wired for multi-agent ops.
n8n-legal-ops-templates★ 2
Reusable n8n examples for law-firm operations, including intake, missed-call follow-up, billing sync, and routing patterns.
airtable-automation-toolkit★ 1
Python toolkit for Airtable, a staging layer, dead-letter queue, PII-masked audit logging, and bidirectional sync.
n8n-error-handling-pattern★ 1
The reliability backbone, retry with exponential backoff, a dead-letter queue, fallback paths, and audit logging.
n8n-ai-agent-delegator★ 1
Multi-agent delegation for n8n, an orchestrator routes plain-language commands to specialist agents with confidence scoring and human-in-the-loop gates.
How every build works
The operating habits behind a dependable workflow, with public examples for technical review.
- Input validation & authpayloads can be checked before they reach a connected system
legal-ops-templates - Retry with backoff + DLQtransient failures can retry, then move to a review queue
error-handling-pattern - Fallback pathsfailed steps can follow a defined recovery path
error-handling-pattern - PII-masked audit loggingimportant actions can be logged while sensitive fields are masked
airtable-toolkit - Credential-leak linting in CIautomated checks can flag likely secret exposure and workflow defects
n8n-lint - Human-in-the-loop gatesAI can assist inside narrow permissions while a person approves consequential actions
ai-agent-delegator
What I build
Four practical ways to improve how the work gets done.
Start with a review, fix one workflow, add carefully controlled AI where it helps, or keep me involved for ongoing support. The recommendation depends on the process and the systems you already have.
01
Workflow review
Decide what is worth changing before paying to build it.
I map the current process, identify the handoffs and failure points, and give you a prioritized recommendation with scope, dependencies, and practical next steps.
From $750 · fixed fee
Best first step · ~1 week
02
Systems integration & automation
Connect the tools you already use around one clear process.
One defined workflow is designed, built, tested, documented, and handed over. Hosting and tooling are chosen around your privacy, reliability, and support needs.
From $2,500 · fixed scope
Most popular · 2 to 4 weeks
03
Careful AI integration
Use AI for a specific job without giving it unchecked control.
AI can summarize, classify, or draft inside a controlled workflow. Important actions stay permissioned, reviewable, and bounded by clear rules and cost limits.
From $4,500 · per project
For teams putting AI into production
04
Ongoing systems support
Keep workflows monitored, maintained, and improving after launch.
I monitor what is running, handle changes and failures, maintain documentation, and work through a prioritized improvement backlog with your team.
$1,500/mo · retainer
Ongoing · monthly retainer
How I work
Start with the process. Finish with a system your team can run.
A short, general conversation is enough to decide whether the problem and my approach fit. Please leave out client names, matter details, and confidential information at this stage.
Discovery
Free 15-min call
You describe the process and systems in general terms. I tell you whether I can help.
Scope
Proposal
We agree on the outcome, responsibilities, safeguards, timeline, and support needs.
Build
Build & test
The workflow is built and tested against normal cases, exceptions, permissions, and recovery paths.
Launch
Ship + docs
The system is deployed with documentation, handover, and a clear owner for follow-up.
Support
Stay ahead
Ongoing monitoring, maintenance, and improvements are available when needed.
"Good automation is quiet. It moves the right information, asks for a decision when judgment matters, and tells someone when it needs help."
how every build works · understand the process · connect the systems · test the exceptions · document the handover
The stack
Tools I can work with.
Integration & orchestration
n8nDocker ComposeTraefikTemporalMake
AI, when the job calls for it
Local modelsClaude (capped)Semantic cacheHybrid routingMCP
Data & business systems
SupabasePostgresQdrantAirtablePython
Questions
Before you reach out.
A few practical questions before we speak.
How do projects usually start?+
A short call or email is enough to start. Describe the process, systems, and timeline in general terms, and leave out client names, matter details, and confidential information. I will tell you whether I can help and what a sensible next step would be.
What does it cost?+
It depends on scope, so I quote per project after the call. As a rough guide: a focused Automation Audit starts around $750, a fixed-scope Build & Ship from $2,500, and an ongoing retainer from $1,500/month. No surprise invoices, and you'll get a clear proposal with deliverables and a timeline before anything starts.
Won't this just be more AI tools and bills?+
It should not be. I begin with the process and the systems you already have. AI is included only for a defined task where it adds useful judgment, and important actions can remain behind human approval. The aim is a simpler operating process, not a larger collection of tools.
Do you work with the tools we already use?+
That is usually the starting point. I work with CRMs, billing systems, phone platforms, databases, Microsoft tools, n8n, Make, Zapier, Power Automate, and other services that provide a safe way to integrate. The recommendation depends on access, reliability, privacy, and maintenance needs.
What happens when something breaks?+
Failures should be expected and designed for. Depending on the workflow, that can include validation, retries, alerts, logs, fallback paths, and a queue for items that need attention. Ongoing support is available for changes that cannot be handled safely by your team.
Are you available, and how do you work?+
Yes. I work remotely with teams worldwide and usually reply to a new inquiry within one business day.
Will my team be able to maintain it?+
Yes. I document what was built, how it is operated, what to check when something fails, and who owns each follow-up. If your team would rather not maintain it, I can provide ongoing monitoring and support.
Let's talk
Have a process that depends on too much copying, chasing, or remembering? Let’s make it dependable.
Send a general description of the process, the systems involved, and your timeline. Please leave out client names, matter details, and confidential information. I’ll reply with whether I can help and a sensible next step.
Fully remote · working with teams worldwide, across time zones · typical reply within one business day.