about blockwork

Our story is a series of broken tools that led us here. Here's how we fixed our problems and how we can help you do the same.

it all started with a very annoying trial period.

We were growing Curiosity Learning, a non-profit building education communities around the world. Volunteers give their time. You can't afford to waste it. So we needed a system built right from day one.

We tried the usual tools. One of them waited until after the trial to tell us custom fields cost extra. Then we found Fibery.

It was a blank slate that worked the way we actually needed it to. We built exactly what the org needed. Then we noticed other teams stuck in the same trap, so we started blockwork.

since then, we've been building systems for neat freaks like us. and we love it.

blockwork's non-negotiables

The values we build by, the ones that shape how we design, build, and support systems that actually hold up in the real world.

adoption starts before launch.

We get people involved, curious, and invested, so launch day feels like relief, not dread.

we don't just build what you ask for.

We dig into how work actually happens, then build the system that fixes the root problem, not a shinier version of the same mess.

we write things down (properly).

Walkthrough videos, written guides, support when needed. So your team stays informed without calling us every time.

fewer meetings, more progress.

Your feature tracker lives in your workspace. Weekly written updates. Meetings only when your input actually matters.

no "ugh, another tool" energy.

We make sure your team is comfortable before we go live. By the time we ship, the reaction is simple: "Finally."

copying broken systems doesn't help.

Same data, same problems, shinier tool. No thanks. We rethink the structure so the new system actually fixes things.

founder's q&a

We skipped the mission statement because nobody reads them. Get the honest take on why we're obsessed with getting your workflow right.

why do most implementation projects fail, and what do you do differently?

Most restructures fail because they treat the symptoms, not the disease. If your process is a disaster, a new tool just makes it a digital disaster. So we poke around until we find the real friction, usually the stuff you didn't even realize was broken.

We build with the future in mind, moving communication out of messy chat threads and into a structured database. By the time we're done, you'll have the data to see exactly how long work takes and where the bottlenecks live.

why fibery specifically, and not other project tools?

Most tools treat data like a messy pile of digital sticky notes. Fibery uses a proper database structure, the same kind banks use, so it stays fast with millions of rows. We've synced 500,000 records without a flinch, showing a client exactly which team habits were making them money.

Try that in a "block-based" app without it crashing. Between the heavy-duty storage and the ability to write custom scripts, we can build the weird, specific features that off-the-shelf software won't touch. If you can dream it, we can probably make it run.

what does success look like to you?

Five years from now, when a past client describes working with us, I want them to say: "They can make anything we need possible." "We officially deleted that spreadsheet." "This is so much easier than how we were doing things before."

That's the goal. Not just delivering a system, but fundamentally changing how operational work feels.

what part of your job still genuinely excites you?

Seeing a client's specific idea come to life in Fibery, something no off-the-shelf software in their niche has ever done. They tell me exactly what they need, I build it, and then I get to see their face when they realize it works: 'This is exactly what we needed.'

That's the good stuff.

again, is this for you?

Maybe, you tell us:

  • Your team is 10–100 people and growing fast.
  • Your tools don't talk to each other.
  • You tried fixing it yourself and made it… interesting.
  • You're ready to hand the systems headache to someone else.
  • You have budget for proper implementation (not just advice).
  • You found Fibery and want someone who actually knows it inside out.
book a fit call