Naming this site has been harder than naming a newborn — going with “FavLab” for now

We build digital products people actually enjoy using.

Not websites.Products.
What we're building, below ↓
Analyzing
Building
Experimenting
Breaking
Shipping
Learning
Failed
What We've Built

What we've built so far.

View all projects →

Every experiment starts with a question worth asking.

The Lab

How an idea becomes a product.

The team whiteboarding a product plan
01Problem
02Research
03Prototype
04Build
05Launch
06Measure
07Improve
Philosophy

Four rules we don't break.

What We Refuse

Fewer things that matter. Not many things that don't.

01
Building just because you asked.

Every feature has a cost. We test the assumption before we touch the code.

02
Copying competitors.

Copying ships someone else’s roadmap, six months late.

03
Chasing trends over value.

Trends fade. Whether it worked for your users doesn’t.

04
Disappearing after delivery.

Shipping is the start of the feedback loop, not the end of the invoice.

FAQ

Questions people actually ask.

Most projects land somewhere between 2 and 6 weeks depending on scope. You'll get a real timeline after the first scoping call, not a placeholder number.

Both. Early ideas get a prototype first so we're validating before committing real budget. Existing products get audited before anything's added.

A clear problem statement and access to whatever you already have — brand, existing code, accounts. We'll ask the rest as it comes up.

Launch is a checkpoint, not the finish line. We stick around for fixes, iteration, and the next round of features if you want it.

Fixed scope for defined work, hourly for ongoing iteration. You'll know which one applies before anything is signed.

Chat with us