Four Jira instances, four ways of naming the same ticket, no one able to report across them.
Merged to one Cloud site, 31 workflows reduced to 6, reporting works from one board. Eleven weeks.
§ 01 · How this works
- 01
You write. I read it, ask two or three questions, and say whether I'm the right person.
- 02
First week is reading your setup, not touching it. You get a written plan with a price.
- 03
At the end: working systems, documentation, and a handover your own people can maintain.
§ 02 · Services
01
Atlassian
Jira and Confluence that match how the team actually works. Migrations, cleanup of eight years of workflows, Cloud moves, the scripts nobody wants to write.
02
Web
Sites and internal tools built to be maintained by whoever comes after. Plain stacks, readable code, a handover document you can follow.
03
Automation
The manual step someone does every Monday, removed. Integrations between the systems you already pay for. Logged, monitored, documented.
§ 03 · Selected work
§ 04 · The engineer
I've spent fifteen years inside other people's systems: banks, telcos, two gaming companies, a LOT of Jira. I work alone on purpose. You talk to the person doing the work, the estimate comes from the person who'll have to keep it, and when something breaks at 23:00, I already know where.
Senior engineer · 15 yrs · Tallinn · Remote across EU
§ 05 · Contact
Tell me what's broken.
Got it. Filed as .
I'll read it today. If it's urgent, hello@techodesk.ee