01
find the real cause behind recurring technical problems
Software architect and technical consultant
Clear engineering for systems that are slow, fragile, or hard to change.
I help companies diagnose weak technical foundations, choose the right next move, and improve the systems their business depends on.
No pitch — just a direct technical review of your architecture and bottlenecks.
Common signals
Slow or unstable systems that block delivery
Integrations with unclear ownership and repeated failures
Data that exists but does not guide decisions
Technical choices that create more work than progress
The fix is rarely “more code”. It is usually better structure, clearer ownership, and fewer accidental dependencies.
Goran Štimac
Software architect and technical consultant
How I help
Clearer systems. Better technical decisions. Less wasted effort.
I work as an external architect and technical consultant when the system is hard to trust, change, or scale.
02
simplify architecture before adding more tools
03
connect systems, data, and automation around how the business works
The goal is not more activity. The goal is a system the team can understand, operate, and improve.
What I Do
Focused consulting for the systems behind the business.
The strongest fit is architecture, integrations, automation, data and AI workflows, and ongoing technical direction.
Technical clarity before you waste capital on a rebuild.
What I deliver
- Prioritized, evidence-based findings you can act on
- A practical roadmap that separates diagnosis from implementation
- Clear infrastructure and hosting trade-offs for your actual system
Connect systems cleanly so data moves reliably without manual effort.
What I deliver
- Explicit data contracts and authentication between systems
- Reliable workflows with observable triggers, exceptions, and approvals
- Maintainable websites, commerce, and marketing systems that integrate cleanly
Turn unstructured data into practical, automated internal tools.
What I deliver
- Workflows built around a defined task, source material, and review boundary
- Retrieval, evaluation, and guardrails designed together
- A measurement layer that shows whether the workflow is useful
What you get
Practical outcomes backed by senior engineering judgment.
You get clearer direction, fewer fragile edges, and help from someone used to complex environments.
Results
01
A clearer technical direction
02
Fewer fragile integrations and operational surprises
03
Less complexity for the team to carry
Why me
01
20+ years of hands-on engineering experience
02
Experience with complex systems in large-scale environments
03
Practical, vendor-neutral judgment before implementation
Process
Three steps. Clear scope. No unnecessary rewrite.
Understand the problem, choose the right move, and act on a plan the team can use.
01
Review the setup
We look at what is happening, what is breaking, and where the business feels the cost.
02
Define the right direction
I recommend the simplest workable path, the changes to avoid, and where effort is best spent.
03
Move with a clear plan
You get a practical next step that reduces risk and keeps the work aligned with business goals.
Blog
Recent posts
A few posts worth a look.
Security & Privacy
SBOM Release Gates for Small Teams: From Inventory to Action
How small teams turn generated SBOMs into release gates that change what ships: consumption checks in CI, one canonical format, exploitability-aware triage, and expiring exceptions with retained evidence.
Linux & Server Administration
Reliable systemd Timers: Replacing Cron Without Surprises
A hands-on cron-to-systemd-timer migration tutorial: writing a reliable .timer/.service pair, translating schedules and their traps, tightening privileges, verifying runs, and rolling back safely.
Infrastructure & DevOps
Cloud Cost Guardrails for Small Teams: Budgets, Alerts, and Ownership
An opinionated, practical stack of cloud cost guardrails for small teams: resource ownership, provider budgets and anomaly alerts, creation-time controls, and an alert response path with named owners and expiring exceptions.
Marketing & SEO
Core Web Vitals after INP: what to actually optimize in 2026
A practical 2026 Core Web Vitals guide covering the LCP, INP, and CLS failures that still cost real sites field performance, plus fixes you can measure.
Web Development
Modern CSS You Can Actually Ship in 2026
A production-safety guide to modern CSS in 2026: where :has() and container queries are ready, and where view transitions or masonry still need graceful fallbacks.
Infrastructure & DevOps
Why Are We Still Talking About Containers? Kelsey Hightower's Case for Useful Abstractions
A commentary on Kelsey Hightower's ContainerDays London 2026 talk and its argument that containers remain useful when treated as a practical operating-system abstraction, not a destination.
Free discovery call
Book a free 30-minute discovery call and get a clear direction for your system.
I can help you review the current setup, decide what to fix first, and create a practical path forward.