Amaze Labs

Cristian Filimon · Auckland, New Zealand · for teams of 10–50 people

I turn messy processes into systems that run your business.

I start from the problem, not the tool. Then I ship the smallest fix that works, with the tools you already have, and measure what changed.

Cristian Filimon

15+ years

building the systems behind businesses

+50% customer lifetime value

at a podcast studio, through data and automation

2.5x EBITDA

exit for the software company I co-founded

Case studies available on request.

I work best with teams of about 10–50 people who have outgrown spreadsheets and run on tools that don't talk to each other.

What I do

1

Discovery & process mapping

Find the problem worth solving before you spend on new software. I talk to the people doing the work, map how work and data flow across your tools, and size each gap by what it costs you. You get a short list, ranked by impact.

2

Connecting tools & automating manual work

Start with one workflow, not a big project. I connect the tools you already pay for, so each fact lives in one place, and automate the steps in between. You see it working early, and we measure the hours it gives back.

3

Fractional product / ops lead

Get a senior person who owns your internal systems like a product, a few days a week, without a full-time hire. I set the outcomes, prioritise the backlog, manage the vendors and translate between your business and the people building for it.

How I work

  1. 01

    Discover.

    We talk through how work and data move today. I map where they break and what each gap costs you.

  2. 02

    Ship the smallest fix.

    We pick the gap that costs you the most. I fix it with the tools you already have where possible.

  3. 03

    Measure, then decide.

    We check what changed: hours saved, errors gone, numbers you trust. Then you decide if we take on the next gap.

We start small. If it's not useful, you stop there.

Things I've built

My own products, built and run under Amaze Labs.

Tools that don't talk to each other?

Tell me what's slowing your team down. We start from the problem, not the tool. I take on a few independent and challenging projects at a time.

Let's talk