The technical operator you wish you hired earlier.

The short version

I'm Carsten. I build operational systems for small and mid-sized businesses - and I run the ones I build. Production Laravel since 2013. Magento years before that. I've spent the last five years effectively as outsourced CTO for a Belgian real-estate SaaS, where I built and maintained the platform that ran their business.

I also build and operate SitePerfector, a content-operations platform of my own, plus the orchestration layer underneath everything I run. I ship and operate real products, not just client work - the systems I build for clients are the systems I already run for myself.

The embedded-operator track record

For five years I held the operational complexity of someone else's business. Architected the platform, built the team patterns, made the technical decisions that compounded. Lead intake from six-plus sources, scoring, automated distribution, CRM sync, billing, reporting, lifecycle email. Thousands of leads per month, processed without me being online.

That's the kind of relationship most founders only realize they need after they've hired and lost three engineers. It's also the kind of work I'm now selectively available for.

Penang, async, and why that's a feature not a bug

I live in Penang, Malaysia. My clients are in Belgium, the Netherlands, Germany. I've worked with operators I've never met in person for five years at a time.

Async-by-default isn't a compromise - it's the operating model. Short async exchanges, weekly written updates, calls when they're genuinely useful and not before. Daily overlap with European working hours. No standups, no decks, no theatre.

If you've worked with offshore teams that felt like an extraction problem, you've worked with the wrong shape of engagement. The shape that works is closer to a senior in-house engineer who happens to be in another timezone - code access from day one, written context, decisions made in commits and PRs.

How I got here

Twenty-five years of building things on the web. The first half doing ecommerce, freelance dev, agency work. The second half going deeper - Magento and Laravel production, my own digital products since 2014, niche content sites with real SEO budgets, paid newsletters, SaaS.

Three months ago my long-term Belgian engagement wound down - the founder shifted from technical operations to go-to-market and budget moved with him. That's a fair trade. It also freed up capacity I'd been holding for a single client for five years. Hence this site existing now and not last year.

TinyWorkers

I built TinyWorkers because most operator work needs orchestration infrastructure that survives between client engagements. It's the internal layer underneath the workflow automation work I sell - clients' workflows run on it, but they don't buy it. Think n8n meets spreadsheet logic, with humans in the loop, AI-assisted where it earns its place. It's not a product. It's the invisible economic engine.

What's next

In order of revenue weight:

1. Operational systems engagements for NL/BE SMBs - workflow automation, internal tooling, lead flow, Laravel. Selectively available.
2. Articles, slowly. Notes from production. The patterns that survive a quarter in real workloads.

If your business needs an operator who can hold the technical complexity and the operational systems thinking, tell me where it breaks - info@pawon.dev.