Skip to content
LABS
// client work pays the billsno roadmap · just bets

We build our own.

Product R&D for Monkeys at Work · four bets, one ready to launchfour bets · one ready to launch

MAW Labs is the R&D wing of Monkeys at Work. We build sites for people who care about their business — and somewhere around the hundredth manual check, we started building the tools instead. This is where those live.

Get early accessInspect the betsone email, no demo call
01 / built
On live Shopify and WordPress work. Nothing here started in a strategy deck.
02 / gated
Validate, build, ship or kill. We would rather delete it than let it rot.
03 / based
Quebec. Bilingual by default, because our clients are and the law is.
// the honest version

What Labs is

what_labs_is

Monkeys at Work builds and maintains sites for people who care about their business. Do that for a few years and you end up with a list: the thing that keeps breaking, the check nobody remembers before a launch, the report someone writes by hand on the first of every month.

Labs is where that list turns into software. Every tool gets built for us first and pointed at live client work. Only then does it get a price, a name, and someone answering support — in that order, and usually later than we would like.

It is a second mode, not a second company. The studio keeps shipping client work. Labs keeps shipping our own, and occasionally deleting it.

Runs onShopify
Runs onWordPress
SpeaksFR / EN
If we have to do it by hand twice, we build it. If we build it and nobody reaches for it, we say so out loud and kill it.
— the entire Labs strategy, and yes, that is all of it
// four bets, one ready to launch

Active bets

pick one · see what it does

Every one of these started as a problem on a real client site, on a real Tuesday. Click through and see the actual output — no screenshots of a dashboard that does not exist yet.

select a bet
// statuses are current as of the last deploy, not aspirational
french-parity-scanner · scan reportpreview
French-language scanexample-store.myshopify.com

Crawls a storefront the way a customer moves through it and flags every place the French version is missing, shorter, or quietly falling back to English.

// started because « it is translated » and « it is compliant » are not the same sentence
locationelementresult
/products/:handleSize chartEN only
/cartShipping noticePartial
/checkoutField labelsCompliant
/policies/refundPolicy bodyEN only
meta · og:descriptionSocial previewPartial
01Building MVP

French Parity Scanner

french-parity-scanner

Crawls a storefront the way a customer moves through it and flags every place the French version is missing, shorter, or quietly falling back to English.

// started because « it is translated » and « it is compliant » are not the same sentenceoutput → scan report
02Ready to launch

Website Monitor

website-monitor

Snapshots a live site on a schedule and shows exactly what changed overnight — before a client notices it broke.

// started because nobody enjoys learning about a broken header from the clientoutput → diff + alert
03Prototype

Outreach Tool

outreach-tool

The outreach we were doing by hand in a spreadsheet, turned into a sequence: who to contact, what goes out, when to stop. We use it on ourselves.

// started because the spreadsheet had a tab called « follow up maybe »output → sequence
04Validating

Bulk SEO Editor

bulk-seo-editor

Every title, meta description and image alt on a site in one table. Edit hundreds at once, see the before and after, and publish the batch in one go.

// started because fixing meta descriptions one product page at a time is not a job, it is a punishmentoutput → change batch
// three gates, no committee

How we work

validate → build → ship or kill

Every bet goes through the same three gates. Most never make it past the first one — that is the point of having gates, and it is cheaper than finding out in month six.

Gate 01 · Validate

Does anyone want it

We ask agencies and store owners whether they have the problem, and whether they would pay to stop having it — before a line of product code exists.

// most bets die right here
Gate 02 · Build

Does it survive real work

A narrow first version, running on live client sites. If we do not reach for it ourselves within a month, it is not ready to sell to anyone else.

// we are the worst-behaved user we have
Gate 03 · Ship or kill

Does it earn its keep

It ships with a price and someone answering support, or it gets killed and written up. No half-alive side projects sitting in a folder.

// shipping is a commitment, not a launch post
Killed at any gate → written up, filed, and the reason published internally
// early access

Get the tools as they ship

One email when a bet goes live, with an invite to try it on your own sites. If we ship nothing this quarter, you hear nothing this quarter. That is the whole arrangement.

next up: website-monitor
maw@labs:~$ subscribe

One email when something ships. Nothing else, ever.

// no drip sequence. we built the outreach tool, we know what those look like.