Goodland Premium Foods
A food-production business running orders, inventory and fulfilment from one architected workspace.
operations architecture for owner-run businesses
workspaces shipped for food production, venture funds and clinics – by one architect
For owner-run businesses – roughly 3-15 people – where the team is busy but execution leaks. I find what's worth automating, architect the system, then build it. The business runs itself; you get back to shaping it.
If there's no build worth doing, I'll say so on the call.
Three people ping you about the same client.
The CRM still says negotiating. The deal moved on weeks ago.
Onboarding lives in your head. All of it.
Forty tools, and the mess just has more places to live.
The workspace you started building is still half-built.
The usual ways out don't hold. Pushing through works until a key person leaves and the process walks out with them. DIY works until the build stalls – you're running the business, not architecting it. And a freelancer will wire up whatever you point at, but automation is an amplifier. Knowing where to point is the actual work.
Automate a mess and you get an automated mess. Architect it first, and your operations start thinking with you – not just for you.
When owners describe the dream, automation barely comes up. It sounds more like this:
How things work lives in one place the whole team can see – not in your memory, not in a departed hire's notes.
A system your team adopts and keeps using, built all the way to done – no eternal construction site.
The routing, chasing and status-asking your week currently leaks – handled by the system instead of you.
Every client, deal and handoff visible at a glance. Delegation you can trust, because nothing depends on someone remembering.
The floor of this is clarity – most ops problems are decisions nobody ever made. The ceiling is a system that thinks with you: it captures decisions, surfaces patterns, drafts the busywork. The ceiling is where AI earns its place.
Most things shouldn't be automated. The architecture is knowing which ones should.
We start with how work actually moves through your business – including the parts that live in people's heads – and decide together what's worth building at all.
Then I design the system around the real bottlenecks: where handoffs break, where decisions stall, whose attention needs protecting. One system of truth, shaped to how your team already works.
And then the build – on the tools your team already opens every day, with AI designed in from the start: it files decisions, chases handoffs, drafts the boring emails.
Free. We walk through your messiest process and see whether there's a build worth doing. If there isn't, you'll hear it from me first – and you leave seeing your operation more clearly either way.
A paid, fixed-scope diagnosis of how your business actually runs. You get the roadmap – what's worth building, in what order, and why. It's yours to keep, build with me or not; if we build, it becomes the exact scope. No discovery theatre, no surprises later.
Bundles sized off the roadmap, from one core module to the full system – priced on what ships, not on metered hours. The first piece goes live inside week one, and the system grows module by module from there.
The first working piece is live within seven days of kickoff.
Delivered as scoped and your team actively using it within 30 days – or I keep working at no extra cost until it is.
Every number is agreed before the build starts. No hourly meter.
Workspaces architected and shipped across food production, venture capital, clinics and more – every one of them by me, Krystof Ekl, start to finish. Three recent builds:
A food-production business running orders, inventory and fulfilment from one architected workspace.
Dealflow pipeline and operations dashboards for a venture fund – scope that grew session by session as trust did.
Furniture-production planning with an AI agent that proposes production-slot assignments a human approves.
“His automations save us hours every day and prevent critical steps from falling through the cracks.”
Dash Media
“We got everything we asked for and even more – some of the things we couldn't think of ourselves.”
Vibing Out
“Our clinic process is complex, but Krystof was able to quickly see through the complexity and simplify it.”
NeuroDiverse Online
The first working piece is live within seven days of kickoff – guaranteed.
I architect operations because of what a well-built system makes possible. A business that can see itself – decisions captured, patterns visible, knowledge that stays when people move on – gets to spend its attention on better questions.
And to be clear about the AI in all this: I'm not here to replace your people with bots. I systematise the rote so your people can do the work only they can do.
The organisations I want to exist are wiser ones: teams that manage themselves more than they're managed, systems that think with the people inside them. The consulting is how that starts. If that resonates, we'll get along.
Metanoia Ops is the operations-architecture practice of Krystof Ekl – based in Prague, working remotely with owner-run teams across Europe and beyond.
Before anything gets automated, someone has to decide how the work should flow – what the stages are, who owns each handoff, what the system should catch. That's architecture. I do that first, then build it – in your tools, with AI doing real work, quietly.
The sentence I hear more than any other – and not a you problem. Running a business and architecting one are different jobs. We keep what works, redesign what doesn't – and finishing is the whole job here: the Blueprint defines the final state before the build starts, and the build is guaranteed delivered and adopted – your team actively using it within 30 days, or I keep working at no extra cost until they are.
Because the build is the cheap part now – AI made it cheaper. What you're hiring is the judgment about what's worth building, and delivery that holds up: deterministic automations doing the reliable work, AI only where it pays for itself. That judgment gets more valuable as the tools get better, not less.
Notion is usually the substrate – most owner-run teams already live there, and it's the most malleable place to build a single source of truth. But the architecture comes first: where an existing tool already does its job well – a CRM your team actually uses, say – the system connects to it rather than replacing it. And if Notion is the wrong tool for your case, I'd rather tell you than build you the wrong system.
The discovery call is free. Everything after is fixed and agreed before we start – no hourly meter, no surprise invoices. The Blueprint is a paid, fixed-scope diagnosis priced by the size of the operation; the build comes in bundles sized off the roadmap, priced on the value of what ships. On the call you get real numbers for your case.
Guaranteed: the first working piece is live within seven days of kickoff, so the system proves itself long before handoff. And the roadmap pays off the week you get it – it's a clear map of your own operation.
No. I'm not here to replace your people with bots. I systematise the rote so your people can do the work only they can do.
Owner-run businesses, roughly 3-15 people – big enough that the mess costs real money, small enough that one person can decide to fix it. Too complex for a template, too small to interest the big-agency rebuilds. Funds and larger teams are welcome too – the same architecture scales up.
Prague – working remotely with owner-run teams across Europe and beyond. Everything from discovery to delivery runs online, in your workspace.
One call, your messiest process on the table. If there's a build worth doing, you'll see its shape before we hang up – and if there isn't, that's worth knowing too.
The call is free. The first working piece of any build: live within seven days.
Not ready for a call? Email me the mess as you'd describe it to a colleague – I'll reply with a first read.
krystof@metanoia-ops.com