Stackdrop
L.00Products LabFoundry

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

The Products Lab is our methodology with real users, real uptime, and real consequences. Every product here is the full Stackdrop stack at work: architecture, UI/UX, governance, shipped and operating.

Built in-houseRuns on our own platformOperated in production
5
Products in the lab
1
Shared build methodology
100%
Run on our own stack
L.01 · The methodDogfood, then productize
Why a lab

Dogfood, then
productize.

Every product here started as a tool we needed ourselves. A gap in our own operations, built the exact way we build for clients: on our own platform, in weekly cycles, with governance from day one.

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

P.01 · Meeting intelligencemeetso.ai
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
  • Zero setup: connect a calendar and it works on your next call
Proof

Connect a calendar and it works on your next call, with no configuration. Users report saving hours of meeting follow-up every week.

Visit meetso.ai ↗
meetso.ai · post-call summary viewscreenshot
WhatMeeting intelligence
ForTeams on Google Meet
Works withGoogle Meet · Calendar
SetupZero · connect a calendar
P.02 · Applicant trackingbringboard.com
Applicant trackingOpen beta
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
Proof

In open beta and free during beta. Early teams building with Bringboard include Vercel, Linear, Raycast, Resend, Clerk and Neon.

Visit bringboard.com ↗
bringboard.com · hiring pipeline boardscreenshot
WhatApplicant tracking
ForStartups & small teams
Data modelFully customizable
AccessOpen beta · free
P.03 · Database designschemadrop.com
Collaborative database designBeta
schemadrop.com

Schemas that never drift from the diagram.

Write DBML, watch the ER diagram render live, and edit multiplayer-style with your team. Export SQL for Postgres, MySQL or MSSQL, drop a PNG, or publish versioned public releases. For engineering teams who want the schema and the diagram to stay one thing.

  • Write DBML, get a live ER diagram
  • Multiplayer editing with your team
  • Export SQL: Postgres, MySQL, MSSQL, plus PNG
  • Versioned public releases, embeds and a REST API
Proof

Free during beta. Sign in with GitHub and you are sketching a schema in under a minute.

Visit schemadrop.com ↗
schemadrop.com · DBML editor and live diagramscreenshot
WhatDatabase design
ForEngineering teams
ExportsPostgres · MySQL · MSSQL
AccessGitHub sign-in · beta
L.02 · How the lab worksFrom our backlog to your stack
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: our platform, weekly cycles, a working surface fast.

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.

L.04 · PrinciplesWhat we refuse to skip
Pr.01

Build it for ourselves first

No product ships until we have relied on it in our own work. Need comes before roadmap.

Pr.02

If it survives our ops, it is real

Daily use is the filter. A tool that cannot carry our own week has no business carrying yours.

Pr.03

Ship a working surface weekly

We work in weekly cycles on our own products too. Real screens every Friday, never slideware.

Pr.04

Governance from day one

Access, audit and data handling are designed in at the start, not bolted on before a launch.

L.05 · The clockIdea to shipped, in weeks
Week 00

Spec the pain

We write down the workflow that hurts, the people it touches, and what a good day looks like once it is fixed.

Week 01–02

Prototype in the open

A working surface goes up in days. We use it ourselves immediately and let the rough edges tell us what matters.

Week 03–04

Harden under load

Governance, integrations and reliability get built while the tool runs in real work. The failure modes are found by us, not you.

Week 05

Ship it

The tool becomes a product: onboarding, docs and a public surface, on the same cadence we hold ourselves to for clients.

Ongoing

Keep running it

We never stop being the user. Every product in the lab is still part of how Stackdrop runs day to day.

See them running

The lab is open

Every product here is live. Go use the ones we built for ourselves, then tell us what your team is trying to build.

meetso.ai ↗bringboard.com ↗schemadrop.com ↗