About

Toronto, Ontario 32 services · four disciplines

A studio that tells youwhen not to hire it.

We design, build and look after websites, software and automation for businesses in Toronto and across the GTA. That description fits several hundred firms in this city, so the rest of this page is about the part that does not.

Based inToronto, Ontario
Working acrossThe GTA
You ownEverything built
Lock-inNone

You cannot evaluate this kind of work before you buy it. Every firm shows a portfolio, every firm describes itself as honest and communicative, and none of that survives contact with a project going sideways.

Testimonials are selected. Case studies are written by the people being paid. Awards are frequently entered rather than won. Even a referral only tells you that one project, for one business, with one set of circumstances, went well enough that somebody was willing to say so.

The only genuinely useful signal is whether a supplier will tell you something against their own interest — in writing, in public, on the page where they are trying to sell you the thing.

That is what the next section collects. Fourteen places on this site where we argue against spending money with us: cheaper alternatives, work we decline, promises we will not make, and the circumstances in which you should hire somebody else entirely.

They were not written for this page. They were written on the service pages, where they cost us something — each one sits inside a page whose entire purpose is to sell that service.

The evidence

Fourteen times this site talks you out of it

Each one is a direct quote, with a link to the page it lives on. Pick any of them.

from

None of this is modesty. A supplier who never says no is a supplier who will build whatever is asked for, invoice for it, and let you discover afterwards that it was the wrong thing. Saying no early is cheaper for you and, over a few years, better for us.

How we work

Six habits, applied to everything

Not values on a wall. Each one shows up as something concrete in how a project runs.

01

Scope before enthusiasm

The first conversation establishes what decision you are actually trying to make. A surprising number of projects change shape entirely at this point, and a few stop.

02

The boring option gets considered

Every proposal weighs the unglamorous alternative — a subscription tool, a rules-based automation, better documentation — against the thing you asked for. Sometimes it wins.

03

Estimates carry their assumptions

Ranges with the assumptions written next to them rather than a single confident number. When an assumption turns out to be wrong, you can see which one moved.

04

Built to be handed over

Code in your repository, credentials in your name, documentation written for whoever comes next. Nothing depends on us remaining involved.

05

Measured, then reported plainly

What was built, what it cost, whether it did what it was meant to — including the months where the honest answer is that nothing much changed.

06

Failure modes are designed for

What happens when the API is down, the model is wrong, the update breaks something. Decided before launch rather than during an incident.

The stage-by-stage version of a project is on the How It Works page.

Honesty

Who we are wrong for

Worth reading before you get in touch, because these are the engagements that go badly for both sides.

You want the cheapest quote

There is always someone cheaper, and on a fixed brief they will often deliver something that works on the day it launches. If price is the deciding factor, take theirs.

You need it by Friday

Genuine deadlines are fine and get planned around. Deadlines that exist because nobody started until now produce work nobody is proud of.

The brief is "make it like Apple"

Aspirational references are useful. A brief with no stated audience, no measurable outcome and no willingness to decide is not a brief.

You want AI because it is AI

We will ask what decision it improves and what it costs today to do without. If neither has an answer, we will suggest not doing it.

Nobody on your side will own it

Every project needs one person who can answer questions and make decisions. Without that, work stalls in review and the estimate stops meaning anything.

You want guaranteed rankings

Nobody can promise a search position, and anybody who does is either inexperienced or counting on you not checking. We will show a measured grid instead.

Straight answers

The things people ask before committing

01Why are there no client logos?

A logo wall proves somebody paid an invoice. It does not prove the work was good, the relationship was pleasant, or that the client would use you again — and plenty are placed with permission obtained years ago for a project that went badly.

Ask during a conversation and we will put you in touch with people who can speak to specifics. That is worth considerably more than a grid of images.

02How big is the team?

Small and deliberately so, with specialists brought in where a project genuinely needs one — and we will tell you when that is happening rather than presenting it as in-house.

What matters practically is that the person you speak to is the person doing or directing the work, and that nothing gets quietly handed to someone junior once the contract is signed.

03What does a project cost?

It depends far too much on scope for a number on this page to be useful, and any figure quoted before understanding the work would be a guess dressed up as a quote.

What we commit to is a fixed figure once the scope is agreed, with the assumptions it rests on written next to it, and a conversation before anything changes it.

04What happens if we stop working with you?

You keep everything. Code in your repository, hosting and domains in your name, credentials handed over, documentation written for whoever picks it up next.

Nothing we build is designed to be difficult to leave. A client who stays because leaving is painful is not a client relationship worth having.

05Do you use AI to build things?

Yes, as a tool, in the same way as any other. It does not change who is accountable for what ships or who reviews it before it does.

Where it is relevant to what you are buying — generated content, an AI feature inside your product — we say so explicitly on the service page rather than leaving you to guess.

06What is the fastest way to find out if this is a fit?

A short call describing the problem rather than the solution you have in mind. Twenty minutes is usually enough to tell whether it is a fit, roughly what it would take, and where the risk sits.

Occasionally that call ends with a suggestion that costs nothing and needs no supplier. That has happened more than once and it is a good outcome.