We build automation that actually works

Started in 2019 because we got tired of seeing businesses struggle with tools that promised everything and delivered headaches

How this started

Back in early 2019, I was consulting for a packaging company in Taichung. They'd spent a fortune on some enterprise automation platform that was supposed to streamline their inventory. Three months in, they were still doing everything manually because nobody could figure out how to make it work with their actual process.

That's when it clicked. Most automation tools are built by people who've never run a warehouse or managed customer service tickets at 2am. They look impressive in demos but fall apart when you try to use them for real work.

So we started building scripts and bots that solved specific problems. No fancy dashboards. No features you'll never use. Just automation that does what you need it to do and then gets out of your way.

Early workspace setup showing development environment and testing equipment for business automation projects

What we actually care about

These aren't values we put on the website to look good. They're how we decide what to build and what projects to take on.

Practical first

If it doesn't solve a real problem you're having right now, we won't build it. Fancy features that nobody uses just make everything harder to maintain.

Honest about limits

Some things can't be automated well. When that's the case, we'll tell you. Better to do five tasks perfectly than twenty tasks poorly.

Built to last

We write code that you can hand off to someone else if needed. Clear documentation. No weird dependencies. Nothing that breaks when you sneeze.

Linnea Viklund working on script development and testing automation workflows

Linnea Viklund

Technical Director

I handle most of the technical decisions and client implementations. Before this, I spent six years building internal tools for logistics companies in Scandinavia. Moved to Taiwan in 2018 and realized the automation needs here were completely different from what I'd been working on.

My background is in systems engineering, but I've spent enough time talking to warehouse managers and customer service teams to know that the best solution is usually simpler than you think.

When I'm not writing Python or debugging API integrations, I'm probably hiking somewhere in the mountains or trying to keep my plant collection alive.

How we work with clients

This is our standard process. Sometimes it takes three weeks, sometimes six months, depending on what you're trying to automate.

1

Figure out what's broken

We spend time watching how you actually work. Not how you think you work or how the process is supposed to work, but what really happens when someone needs to get something done. Usually takes a few days of just observing and asking annoying questions.

2

Build something small

We automate one specific thing first. Maybe it's pulling data from your supplier emails. Maybe it's generating weekly reports. Something you can start using within a week or two to see if this actually helps.

3

Adjust based on reality

That first version is never quite right. You'll discover edge cases we didn't think about. Or realize you need the data formatted differently. We iterate until it's actually useful, not just technically functional.

4

Expand what works

Once one part is solid, we look at what else could benefit from automation. Some clients stop here. Others end up with a dozen interconnected scripts handling everything from inventory to customer communications.

Let's talk about your actual needs

If you're spending too much time on repetitive tasks that could be automated, or you've tried automation tools that didn't quite work out, reach out. We'll have an honest conversation about whether we can help.

Get in touch