Built in-houseRuns on our own platformOperated in production

Anyone can pitch a process.
We run ours in production.

2
Products live
1
Shared build methodology
100%
Built in-house
The methodDogfood, then productize
Why a lab

Dogfood, then
productize.

Every product here started as a problem on our own team: notes lost after every call, hiring run on a spreadsheet. We built the fix the way we build for clients, and we still run it every day.

If a tool survives daily use across the team, it earns a second life as a product. The lab is where we pressure-test the method we sell, before we recommend it to you.

P.01 · meetso.aiMeeting intelligence
AI meeting intelligenceLive
meetso.ai

Your meetings, transcribed and summarized before you leave the call.

A bot auto-joins your Google Meet calls, transcribes with speaker identification, and delivers summaries with action items minutes after the call ends. Searchable, shareable meeting records without manual note-taking.

  • Auto-joins your Google Meet calls
  • Speaker-identified, searchable transcripts
  • Summaries and action items minutes after the call
  • One step to set up: connect a calendar, and it joins your next call.
Visit meetso.ai
WhatMeeting intelligence
ForTeams on Google Meet
Works withGoogle Meet · Calendar
SetupConnect your calendar
P.02 · bringboard.comApplicant tracking
Applicant trackingLive
bringboard.com

Hiring that outgrows the spreadsheet, not your team.

Pipeline, candidate email, interview scheduling, branded careers pages, automations, and analytics in one tool, with a fully customizable data model. For startups and small teams replacing spreadsheet-based hiring.

  • Pipeline, candidate email, and interview scheduling
  • Branded careers pages
  • Automations and analytics built in
  • A fully customizable data model
Visit bringboard.com
WhatApplicant tracking
ForStartups and small teams
Data modelFully customizable
AccessLive
How the lab worksWhat we refuse to skip
The build loop

Five stages, one loop

The same loop runs every product in the lab. It is the loop we run for clients, turned on ourselves.

01

Feel the pain

A product starts as a gap in our own operations, something slowing the team down every week.

02

Build for ourselves

We build the tool the way we build for clients, in weekly cycles, with a working surface every Friday.

03

Put it under load

We run it daily, in real work. Most ideas stop here. The ones that stick have earned it.

04

Extract the product

What survived gets hardened: governance, onboarding and edges, so someone outside the team can use it.

05

Ship and run

It ships as a product, and we keep running it ourselves. We stay our own most demanding user.

In productionOrg commit activity
The last 6 months

Shipped, every day

Commit activity across the whole Stackdrop org over the last six months: every product in the lab, plus the platform they run on. We use the lab's products every day; this is the receipt.

4,850 commits · as of 17 Aug 2026
ContactLet's chat
Let's chat

Tell us what
you're building

Describe the process that is slowing your team down: the inbox, the spreadsheet, the portal nobody owns. We'll come back with a concrete approach, a rough timeline, and, where it helps, a working prototype within weeks.

What happens next
  1. We read every messageAn architect reads what you sent before anyone replies.
  2. You hear back in ≤ 2 daysA short reply with first questions and a suggested next step.
  3. We scope and prototypeA scoping call, then a working surface, not a slide deck.
Where are you in the process?