Short essays on systems, operations, and why most fixes don't work.
Product photos are the longest-lived visual assets most businesses own. Treating them as a one-time expense is the most common and most expensive mistake.
Read moreCommercial photography has briefs and deliverables. Private photography has vulnerability. The approach needs to be fundamentally different.
Read moreAI is a tool for photography, not a replacement. Knowing when to use it — and when not to — is the skill that matters.
Read moreEvent photography isn't creative work disguised as logistics. It's logistics disguised as creative work. The best coverage comes from systems, not talent alone.
Read moreMost automation saves time once. System-level automation saves time forever — and gets better the longer it runs. The difference is in the architecture.
Read moreNotion, Airtable, and off-the-shelf tools work — until they don't. Custom internal tools work — until nobody maintains them. Here's the decision framework.
Read moreIt's not your subject line. It's not your copy. The infrastructure behind your outreach determines whether anyone sees your message.
Read moreEveryone rewrites subject lines. Almost nobody checks sender reputation. The infrastructure you ignore determines whether your message ever reaches anyone.
Read moreWhat I learned designing and leading an Erasmus+ course on photography and AI visual tools for international educators. Systems over tools.
Read moreThe cost question is the right question but the wrong starting point. A breakdown of what fractional CMO pricing actually looks like — and what it replaces.
Read moreAgencies execute campaigns. A fractional CMO builds the system behind them. The right choice depends on what's missing — execution or direction.
Read moreMedia buying isn't a standalone function — it's a component of the growth system. Separate it from strategy, and you get wasted money.
Read moreMost website migrations lose 30-60% of organic traffic because nobody treats migration as a systems problem. Here's the infrastructure approach.
Read moreDomain separation, DNS authentication, rotation logic. The architecture behind cold outreach that actually lands in the inbox — not the tactics, but the system.
Read moreThe honest comparison nobody wants to make. WordPress is fine — until it isn't. Static is fast — but not always practical. Here's how to decide.
Read moreNot a strategist who disappears after the deck. A fractional CMO owns the growth function, builds the infrastructure, stays until it works, then hands off.
Read moreThere's a goldilocks zone for hiring a fractional CMO. Too early and you waste money. Too late and you've already burned through budget on random tactics.
Read moreIt's not WordPress itself. It's the accumulation of plugins, shared hosting, unoptimized databases, and nobody maintaining the infrastructure underneath.
Read moreWhat happens when you teach photography on a sailboat? Constraints reveal what matters. Lessons from hosting the Sailing + Photography workshop.
Read moreTechnology doesn't make people smarter. It amplifies what's already there. If you can navigate, you move at blazing speed. If you can't, you're stranded in a sea of menus.
Read moreAccountants handle paperwork. They don't prevent operational non-compliance. That's a system problem.
Read moreAll-in-one tools promise simplicity but deliver consolidated complexity. Everything in one place doesn't mean everything is clear.
Read moreGood architectural photography reveals the designer's intent—whether executed or not. It's structural analysis with a camera.
Read moreTeams debate tools endlessly. The tool is almost never the problem. The process underneath, the ownership, the behavior—that's what breaks.
Read moreAsync feels slow at first but it's actually faster—it forces clarity and reduces loops. Less interruption, better decisions.
Read moreAutomation doesn't fix problems — it scales them. If the process is broken, automation multiplies the brokenness faster than anyone can fix it.
Read moreThe waiter, manager, or receptionist will operate this system. They're not audio engineers. Design for the least technical user.
Read moreMost automation advice assumes you have engineers on staff. Small businesses need a different filter: repetitive, predictable, low-judgment.
Read morePhotos get taken, used once, then forgotten. Without a system for organization and retrieval, photography is a cost center, not an asset.
Read moreStabilization follows a pattern: constraints accepted, ownership clarified, exceptions reduced. Stability isn't calm by default — it's calm by design.
Read moreThe bottleneck isn't tool cost. It's adoption, ownership, and behavioral change. Cheap subscriptions lower the barrier to purchase, not the barrier to actual use.
Read moreCompliance fails not because someone ignored the law, but because behavior wasn't encoded. Paperwork proves compliance — systems create it.
Read moreAvailability creates the illusion of speed. Underneath, the system stops carrying load. People stop checking docs—someone will respond.
Read moreTool confusion is a symptom of unclear operational boundaries. Define the process first, then pick the tool. Usually, you need less than you think.
Read moreConsultants are hired for advice when the business needs execution. You get a PDF and an invoice. Nothing changes.
Read moreMost small business CRMs sit empty or outdated. The problem isn't the tool—it's that no one owns the behavior it requires.
Read moreFiscalization rules are poorly explained. Business owners are confused or misinformed. Here's what you actually need to do, without jargon.
Read moreDigitalization in Croatia often means installing software to satisfy EU requirements. But without ownership and behavioral change, it's just theater.
Read moreIt's easy to believe your own framing. Separate thinking output from identity. Revise without ego.
Read moreEU digital vouchers incentivize maximal scope and checkbox adoption, not operational change. Once reporting ends, the system decays.
Read moreSaaS designed for US markets assumes scale and growth trajectories that don't match European SMB reality. Croatian businesses need simpler tools, not more powerful ones.
Read moreDelegation fails not because people are incompetent, but because the system routes everything back to the founder anyway.
Read moreExcel isn't the problem. The problem is when Excel becomes the system of record for things that change, require collaboration, or have compliance implications.
Read moreOn-site improvisation is expensive. Decisions made under pressure are usually wrong. The site is for execution, not design.
Read moreFlying under the radar works until it doesn't. The fine is usually less painful than the audit stress. Compliance upfront is cheaper.
Read moreThe first working system changes expectations. Suddenly, other broken things become visible. That contrast creates appetite for more.
Read moreMost businesses try to grow by pouring more water in. The smart move is fixing the holes first. CAC spirals when retention leaks.
Read moreNew regulations create new failure modes. Most businesses won't know until it's expensive. Here's what's changing and what your system needs to handle.
Read moreVAT treatment for digital services in Croatia creates friction that pure-software businesses underestimate. Digital doesn't mean simple.
Read moreIn live events, failure is immediate and public. The systems that survive pressure, fatigue, and imperfect people are the ones worth studying.
Read moreNot everything interesting is worth doing. Constraints clarify. Say no more often.
Read moreThe cost of manual processes isn't visible until you measure it. What takes 10 minutes daily costs 40+ hours yearly — and that's before the errors.
Read moreWhen founders say marketing isn't working, they usually mean spending without results. But the problem is rarely the channel — it's the system around it.
Read moreMarketing is activity. A growth system is infrastructure. Activity without infrastructure creates leads that go nowhere.
Read moreIf your operations can't absorb demand, more leads just creates more chaos. Growth is only useful if the system can handle it.
Read moreNotion is flexible. That's both its strength and its failure mode. Learn why a blank canvas can't replace operational clarity.
Read moreI work in bursts. Sustained output degrades quality. Publish when clarity stabilizes, not on a schedule.
Read moreBusiness photography is usually treated as marketing. It's more useful as documentation of what's true.
Read moreIf a process requires real-time chat to function, it's not a process—it's a conversation. Design for async-by-default.
Read moreControl isn't presence. It's knowing what's happening without being asked. Design systems that surface exceptions early.
Read moreThe quality of an engagement is determined before work begins. Better questions upfront mean fewer problems later.
Read moreInterruptions aren't random — they're symptoms of missing defaults and unclear ownership. Here's how to reduce them by encoding answers.
Read moreMost automation requests are solutions to problems that don't exist yet, or band-aids for broken processes. I say no when the ROI doesn't justify the complexity.
Read moreSystems debt is invisible until it's expensive. The realization usually comes during growth, when a key person leaves, or when a compliance deadline hits.
Read moreMost automation requests are diagnostic. The problem they point to is rarely the problem they describe.
Read moreHandling things manually works until it doesn't. Memory fails, people leave, and context gets lost.
Read moreSome projects need volume, multiple locations, tight timelines. Scaled visual production needs systems thinking.
Read moreGrowth doesn't break businesses randomly. It breaks them at the seams—handoffs, coordination, and things everyone just knows.
Read moreNot every business is ready for systems work. There are preconditions — real pain, willingness to constrain, and capacity to let systems carry weight.
Read moreNot every problem needs a system. Some problems need more customers, better execution, or just time. Premature systematization creates overhead without payoff.
Read moreAds amplify what's already there. If the system is broken, ads just amplify the brokenness faster.
Read moreWorkflow automation connects tools. A system defines behavior. Understanding the difference prevents expensive mistakes.
Read moreA system can work in testing and fail in production. The gap is stress, fatigue, and distraction. Reliable means it works when everything else is going wrong.
Read moreGet notified when I publish