About
Automation is more than tools. It is an operating model.
CodeCrafters Automation exists because most automation problems are not automation problems. They are ownership, testing, secrets, access and evidence problems that surface as automation nobody wants to touch.
Why this company exists
Across fifteen years in banking, government and United Nations environments, the same pattern repeats: a capable team, real automation in production, and a growing reluctance to change any of it. The playbooks work, but nobody can test them. The platform runs, but nobody can upgrade it. The evidence exists, but only if someone spends a week assembling it.
That is not solved by adding tools. It is solved by treating automation as an operating model — with standards, tests, access control and evidence designed in from the start — and by leaving the client able to run it without the consultant.
How the work is done
Direct senior engagement
You work with the engineer doing the work. No account layer, no hand-off to a junior team.
Maintainability over cleverness
Content your team can read a year from now beats content that was elegant to write.
Security is not a phase
Secrets, identity and least privilege are designed in, not retrofitted before an audit.
Evidence before claims
If it cannot be shown in a job log, a test result or a change record, it is not a result.
Knowledge transfer as a deliverable
Documentation, standards and walkthroughs are part of done, not an optional extra.
Remote-first
Distributed delivery across Europe and Latin America, based in Central European time.
Engagement model
How engagements typically run
- —A discovery call to establish scope and real constraints
- —A written scope with deliverables and acceptance criteria
- —Hands-on delivery inside your repositories and pipelines
- —Regular, plain review of what works and what does not
- —Handover with documentation and standards in place
Code and platform standards
- ✓ Roles and collections, not one-off playbooks
- ✓ Linting and testing in CI as a condition of merge
- ✓ Idempotency as an acceptance criterion
- ✓ Platform configuration held in Git
- ✓ No credentials in source, ever
Business entity
- Legal entity
- CodeCrafters Automation OÜ
- Registered
- Tallinn, Estonia · European Union
- Founded
- 2023
- Operating base
- Ruda Śląska, Poland · CET/CEST
- Delivery
- Remote across Europe and Latin America
- Languages
- English, Spanish
TODO — add registry code and VAT number if these should appear publicly.
The founder
Jairo Escobar, Founder and Principal Automation Consultant. Fifteen years across the IBM ecosystem, European banking, Kyndryl and United Nations organizations — the full progression is on the Experience page.
Sounds like the way you want to work?
Start with the constraint you cannot get past. That conversation is usually more useful than a capability deck.