Skip to content
01About us

Two people, and nobody to hand your project to

BLANQ is deliberately small. The people you meet in the first call are the people who write the code, which is why we can say no to work that is not a fit and why nothing gets lost in a handover.

02The team

Who you will actually be working with

Between us we cover the whole of a project: the systems it has to talk to, and the way it feels to use.

Abdul Quayum

Web Developer & AI Expert

Focus
Conversational systems, integrations, search

Abdul builds the parts of a project that have to talk to something else: a booking calendar, a price list, a stock feed, a search engine. He started BLANQ after several years of watching small businesses buy software that could not reach any of the systems they already ran on.

His approach to AI is deliberately unglamorous. Before any assistant gets built he sits with whoever answers the phone and writes down the decision tree they actually use, because that document is what separates something useful from an expensive novelty. He is equally willing to tell a client they do not need one, which has happened twice and saved both of them a considerable amount of money.

He works in French and English, handles the technical search work on every BLANQ project, and is the person who will tell you which of your five requested features is the one that will actually move revenue.

Nazif

Full-Stack Developer

Focus
Front-end architecture, performance, accessibility

Nazif owns how a BLANQ site feels: how quickly it paints, how it behaves on a five-year-old Android on transit wifi, and whether someone using a keyboard or a screen reader can finish the same tasks as everyone else. He treats a performance budget as a constraint the design has to live within, not a target to aim at afterwards.

He came to development through back-end work, and it shows in how he structures a front end. Content gets modelled before a single screen is designed, so that by launch the client can change every heading, price and photograph on the site without opening a support ticket. It is the least visible part of the job and the one clients thank him for a year later.

On the Atelier Marchand catalogue he took an eleven-second page to under a second on a throttled connection without touching a single photograph the studio had chosen. He is also the one who insists a site works before it is decorated.

03How we work

Three commitments, and what they cost us

These are not values in the poster sense. Each one is something we have had to honour when it was expensive.

01

Say the number before the invoice

We charge for scoping and hand you a specification you own, including a written list of what is out of scope. If we underestimate something that was in that document, it is our cost, not yours. That has happened three times and we absorbed it three times.

02

Build it so you can change it

Every piece of text, every photograph and every price on a site we build is editable by the person who knows it is wrong. If changing your opening hours requires a developer, we have handed you a liability and called it a website.

03

Measure what you asked us to move

We agree at the start on the two or three numbers a project is meant to change, and we report on them at thirty, sixty and ninety days. When something has not moved, we say so first and explain what we would try next.

Small studio, short queue.

We take on a limited number of builds at a time, which is the only way two people can stay on every project. If the timing works, tell us what you are trying to build.

Let's Build Your Site

Or email hello@blanq.ca. We reply to every enquiry within one business day.