What we build

Internal toolsAdmin panels, portals and ops consoles

AI in productionAgents in queues and workflows, with audit on every model call

Workflow automationApprovals, handoffs and exports that no longer live in a spreadsheet

Data foundationsOne view over SAP, Salesforce and Snowflake, with safe write-backs

Rescue and migrationStalled builds and legacy apps: an audit first, then a realistic plan

Security and complianceSSO, RBAC and audit trails built in, not added before go-live

How we buildOur method

One method, four stages, from the first scope to long-term care. Jump to a stage:

Discovery sprintA focused week to map your ops and scope the build Build engagementHands-on delivery of your tools and workflows Embedded engineeringOur engineers inside your team and backlog Governance retainerPost-launch support with an SLA

Products LabVisit the lab

The products we have built and shipped ourselves. We feel the pain, build for our own team, then extract the product.

P.01 · meetso.aimeetsoYour meetings, transcribed and summarized before you leave the call.P.02 · bringboard.combringboardHiring that outgrows the spreadsheet, not your team.

Company

About usWho we are and how we work CareersOpen roles and life on the team

BlogHow we build internal tools, and why Customer storiesProof from the field — the numbers, the builds

BlogAll articles

By topic

Retool21 Production20 Workflow automation12 Security and compliance07 Data foundations06 Rescue and migration04

By reader

For builders For operators For leaders For security & IT

Latest postWhat is visibility debt? When nobody can see how the work gets doneThe process runs. Nobody can tell you where it stalls, or why.Read

Customer storiesAll stories Featured · CS.01Banking78.3% faster to market at Saxo Bank. Here is what changed.How Saxo Bank's creative operations team moved requests, approvals, and assets onto one platform and cut median time to market by 78.3%.Read the story

More stories

CS.02From a manual fraud queue to a daily risk scoreEducation CS.03Error monitoring in Retool, without a log leaving the regionTechnology

Latest postWhat is visibility debt? When nobody can see how the work gets doneThe process runs. Nobody can tell you where it stalls, or why.Read

Notes from the build.

How we build internal tools, and what they cost, change and return for the teams that run them. Written from our own work.

TopicsReaders

Topics

All Building with AI Data foundations Production Rescue and migration Retool Security and compliance Workflow automation

Readers

For builders For operators For leaders For security & IT

FeaturedData foundations

NewData foundations

What is visibility debt? When nobody can see how the work gets done

The process runs. Nobody can tell you where it stalls, or why.

JMJohn MiniadisFounder4 min read

Read the article

LatestIn case you missed it

01Data foundations

What is tool sprawl, and when does it start costing you?

Every tool works. Nobody is sure which one holds the right number.

4 min 02Security and compliance

What is shadow IT? The tools your team built because it had to

A critical process one person runs from a personal spreadsheet. Correctly, most days.

What is a custom Retool component, and when do you need one?

For when Retool's built-in components stop one requirement short.

5 min 04Building with AI

What is vibe coding, and what does it take to run the result?

The app works on your machine. Auth, data, deployment, and monitoring are still open.

The index

Index

Customer storiesProof from the field

From the field

The stories behind the articles

Every article here started as a real build. See the customers, the workflows they brought us, and the tools they run now.

Read the customer stories

stackdrop stories --latest 3zsh

3 of 7 stories · newest first