Skip to content
Menlo·Labs

1140 Doyle Street, Suite 4

Menlo Park, California 94025

Mon–Thu, 09:00–18:00 PT

§ The studio

Five people, one
room, no bench.

Menlo Labs Studio opened in 2019 above a bicycle shop on Doyle Street. We stayed small on purpose: the studio is sized so that every person here can hold the whole of every project in their head, which is the only way we know to keep the work honest.

§ How we work

I

The people in the pitch do the work

There is no bench and no hand-off to a junior team after signature. If you met them, they are on it. This is the main reason we stay at five.

II

Measure after launch, publish the number

Every engagement ends with instrumentation and a follow-up read at ninety days. We report what we find, including the times a feature we argued for went unused.

III

Plan the exit in week one

Runbooks, recorded walkthroughs, and a named owner on your side are line items in the contract, not goodwill at the end. Retainers are available and rarely necessary.

IV

Refuse the wrong engagement early

We turn down roughly half of what we are asked to quote — usually because a rewrite is being proposed where a repair would serve, or because the timeline only works if we lie about it.

§ Who does the work

The five

  • TB

    Tomás Beckwith

    Founder, studio director

    Fifteen years building instrumentation for utilities and ports. Started the studio after one too many six-figure dashboards nobody opened.

    2019

  • RO

    Rosalind Okafor

    Principal engineer, interfaces

    Spent six years on trading terminals, where a hundred milliseconds is a real number. Writes the rendering code and most of the arguments against adding features.

    2020

  • IM

    Ines Marchetti

    Head of design systems

    Type and interface systems, formerly in editorial. Believes most component libraries are three components wearing a trench coat.

    2021

  • DR

    Devendra Raman

    Applied machine learning

    Computer vision on factory floors and farm equipment. Prefers a four-megabyte model on the line to a large one in a datacenter.

    2022

  • JH

    Junia Halloway

    Producer, studio operations

    Keeps engagements honest about scope and dates. The reason the hand-off phase exists as a line item rather than an afterthought.

    2022

§ Disciplines

  • AInterface engineering
  • BInstrumentation
  • CApplied machine learning
  • DData visualization
  • ETechnical diligence

§ Phases

  1. 01 Survey

    1–2 weeks

    We sit where the work happens before we propose anything. Fixed fee, and it ends in a written document you own whether or not you hire us again.

  2. 02 Prototype

    2–4 weeks

    One narrow slice, built for real and put in front of the people who will use it. We are looking to be wrong early and cheaply.

  3. 03 Build

    6–14 weeks

    Two-week cycles, a working deploy at the end of each. Your engineers are in the repository from the first commit, not the last.

  4. 04 Hand-off

    2 weeks

    Runbooks, recorded walkthroughs, and a named owner on your side. We plan our own exit at the start of the engagement.

§ Visit

Doyle Street, above the bicycle shop. Coffee is genuinely good.

1140 Doyle Street, Suite 4

Menlo Park, California 94025

studio@menlolabs.example

Mon–Thu, 09:00–18:00 PT

Start a project