About us

We build the piece that is missing

Not a platform, not a replacement for everything you run. The one thing that's breaking, built and handed over in a few weeks.

Our story

It started in the family business

Boolean comes out of family roots in manufacturing and construction. We grew up around those businesses and felt the pain of running them: off-the-shelf tools that needed a workaround to do the job, integrations that never quite worked, and systems that created more problems than they solved.

So we built a company around a simple idea: software should adapt to your business, not the other way around. We start small, prove the value, then scale, so you're not betting big on something unproven.

Today we build for small and mid-sized businesses that have outgrown their spreadsheets. The industry matters less than the shape of the bottleneck, so what we deliver is scoped to the specific thing that's breaking rather than to a sector.

The terms

Since 2015

Building custom software

2–6 weeks

Per phase

Fixed

Price per phase

100%

Code ownership

Every one of these is a term of the engagement, not a statistic. You can hold us to all four in writing before any work starts.

What we stand for

Four things we hold to

Transparency

You see the same numbers we do. Scope, price and timeline are written down before work starts, and the weekly demo shows you the real state of it, not a status report.

Quality

Standard tooling, no proprietary frameworks, code your next developer can read. What we hand over is meant to outlive the engagement.

Partnership

You talk to the people writing the code. No account managers, no requirements relayed through two layers of process.

Results

Every phase ends with something your team can use on Monday. If a phase doesn't earn the next one, there's no next one.

How we work

Small team, no account managers

You talk to the people writing the code. That's the whole reason we can hold a fixed price: nobody is relaying your requirements through two layers of process.

01

A discovery call first

We start with a call about the process and where it breaks. If we're a fit, working calls follow to gather the detail and write the spec.

02

One bottleneck at a time

The first build pays for the second. We'd rather prove it in eight weeks than promise it in six months.

03

A demo every Friday

You redirect us while it's still cheap to redirect. Nothing gets revealed at the end.

04

You own 100% of it

Your repository, your hosting, standard tooling. No proprietary framework holding you hostage.

Something breaking?

You don't need a spec or a budget to start. Describe what isn't working and you get a written answer within 24 hours.