about blockwork

No mission statement, no stock photos. Just who we are, how we work, and why we're obsessed with your operations.

it all started with the wrong tool.

Ron has been building systems everywhere he goes: Notion for his school's media team, Airtable and Monday for a non-profit he worked with. So when he founded Curiosity Learning, which builds education communities around the world, he researched properly. Fibery came up and he thought "that's for startups, not for us", so he signed up for Asana instead.

Long story short, he didn't like it. So he gave Fibery another shot, and realized it's not a project tool. It's a builder. Grant tracker, meeting notes, a CRM for reaching out to schools. It worked the way he naturally thinks, which he can't say about any other tool he'd fought with.

And yet nobody was talking about it. Proper structure is what most companies are missing when they grow, and this tool can actually get you there. So Ron started blockwork to help people get there. And yes, because it was a pretty obvious business opportunity.

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.

we stay up to date.

Regular check-ins at the pace you pick, plus quarterly roadmap reviews. When priorities shift, we reroute early instead of building the wrong thing.

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?

Fibery is part app builder, part database builder. You can create whatever your business needs now, and whatever it'll need later. It strikes the best balance I've found between structured and unstructured data: database-first like Airtable, with real documents living inside it like Notion. And it's fast. Even 200,000 records won't slow it down.

I also admire the team behind it. They ship meaningful changes every week, listen to their community, and share everything openly. In a SaaS world full of slimy tactics, they do it ethically.

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.

so, are we a match?

Maybe, you tell us:

Your team is 10–100 people and growing fast.
Work moves between people and departments and things fall through the cracks.
Your information lives in five tools, forty spreadsheets, and someone's head.
Reporting means an afternoon of copy-pasting numbers between tabs.
You have the authority and budget to fix it properly, not just patch it.
You're willing to change how you work, not just add another tool on top.

book an intro with Ron