NewCompany news
The rebrand is the smallest thing we changed.
Stackdrop has a new mark, a new site, and a clearer story. Same team, a new chapter.
JMJohn MiniadisFounder3 min 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.
FeaturedCompany news
LatestIn case you missed it
01Data 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.
4 min02Data foundationsWhat is tool sprawl, and when does it start costing you?
Every tool works. Nobody is sure which one holds the right number.
4 min03Security and complianceWhat 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.
4 min04RetoolWhat is a custom Retool component, and when do you need one?
For when Retool's built-in components stop one requirement short.
5 minThe index
Index
- ExplainerWhat 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.Explainer21 Oct 2026
- ExplainerWhy internal tools become production risksA tool built as a side project ends up running a core process, with no access control, no audit log, and no owner.Explainer29 Jun 2026
- ExplainerA one-line change should not take three weeksWhen a small change to an internal tool takes weeks, the cause is usually architecture: coupled queries, scattered logic, and no shared data model.Explainer29 Jun 2026
- ExplainerWhat it costs to build a production-ready internal toolScreen count barely moves the price. Scope, integrations, access rules, and audit requirements do.Explainer26 Jun 2026
- ComparisonWhat a Retool certified partner can do that a freelancer can'tEnvironments, access control, and a path to production: where certification shows up in the work.Comparison26 Jun 2026
- ExplainerFour controls that make an internal tool safe to rely onAccess control, audit trails, separate environments, and change management, and what each one prevents.Explainer25 Jun 2026
- How-toA pre-build checklist for internal tools that have to lastSix questions to answer before anyone opens the editor.How-to24 Jun 2026
- DecisionCustom software for operations teams, without a large dev teamTwo routes to custom software, and where each one breaks.Decision24 Jun 2026
- ComparisonWhich providers deliver maintained, production-ready internal tools?Compare providers on what happens after launch: maintenance, ownership, and who answers when it breaks.Comparison23 Jun 2026
- ExplainerThe tool was free to build. Maintaining it is not.Why internal tools built in-house get hard to change, and the design choices that keep them cheap to maintain.Explainer23 Jun 2026
- How-toHow to hire a Retool developer, and when you do not need oneWhat to screen for, where to find them, and when hiring is the wrong move.How-to22 Jun 2026
- ExplainerCustom code on the new Retool, with the controls IT asks forWhat changed in Retool for teams that need custom code and still have to pass an IT review.Explainer18 Jun 2026
- DecisionIs Retool worth it at enterprise scale?Where Retool pays off for enterprise operations teams, and where it does not.Decision09 Jun 2026
- DecisionBuild internal tools in-house, or hire a Retool agency?A decision framework, including the cases where you should not hire us.Decision08 Jun 2026
- ExplainerThe tool shipped. The team went back to Slack.Most internal tool failures trace back to building for the person who asked for it instead of the people who use it.Explainer03 Jun 2026
- How-toEditor.js for Retool: an open-source block editor componentBlock-style editing in Retool, free to use and extend.How-to19 May 2026
- How-toA range slider that shows users what they are filteringA custom Retool filter control with the data distribution built in.How-to19 May 2026
- How-toA custom RadioGroup component for RetoolSelection controls with the layouts and states the native RadioGroup does not offer.How-to19 May 2026
- ExplainerHow long does a Retool implementation take? What 200+ builds taught usReal timelines from 200+ builds, and the decisions that move them.Explainer14 May 2026
- How-toA custom document viewer component for RetoolPreviews for the file formats Retool's built-in components do not render.How-to14 May 2026
- ExplainerWhat is a Retool certified partner? A guide for technical buyersWhat the badge means and what to check beyond it before you sign.Explainer05 May 2026
- How-toHow to run full-text search across multiple columns in PostgreSQLOne search box across several columns, with a generated tsvector column and a GIN index.How-to04 May 2026
- DecisionHow to evaluate a Retool development agencyQuestions on architecture, compliance, integrations, and the engagement model, and the answers to listen for.Decision27 Apr 2026
- How-toPostgreSQL INT4RANGE: enforce non-overlapping zones in SQLLet the database refuse overlapping ranges, so the app does not have to check.How-to27 Apr 2026
- How-toRetool HTML component events: why every handler fires at onceWhy one click triggers every handler on a Retool HTML component, and how to route each event to the right one.How-to27 Apr 2026
- How-toAn AI-assisted rich text editor component for RetoolRich text editing inside a Retool app, with an AI model drafting alongside the user.How-to27 Apr 2026
- How-toWhy signed S3 URLs fail in Retool's PDF component, and the fixA PDF that will not load in Retool, traced to how the S3 URL was signed.How-to20 Apr 2026
- ExplainerThe hidden cost of manual processes and spreadsheet workflowsDelayed decisions, errors that compound, and the one person who knows how the file works.Explainer16 Apr 2026
- ExplainerYour workaround has workarounds: when temporary fixes become infrastructureThe spreadsheet that was temporary four years ago, and the other ways workarounds harden into systems the business depends on.Explainer15 Apr 2026
- ExplainerBuilt well, used by nobody: why internal tools get abandonedShared language, documentation, and a feedback loop: what keeps a working tool in use. Pillar 4 of internal tools literacy.Explainer13 Apr 2026
- ExplainerThe architecture behind creative operations at enterprise scaleHow one internal platform gives creative teams their pace and gives the enterprise approvals, access control, and an audit trail.Explainer01 Apr 2026
- How-toSlow tools are an architecture problem: keeping internal tools fast as they growMultipage design, query optimization, and caching for internal tools that slow down as the team grows. Pillar 3 of internal tools literacy.How-to30 Mar 2026
- ExplainerWhen your tools work and your operations still don'tThe manual handoffs between systems that absorb hours every week, and which to fix first. Pillar 2 of internal tools literacy.Explainer16 Mar 2026
- ExplainerWhy your internal tools behave the way they doMap the workflow logic before you build, or debug it in production. Pillar 1 of internal tools literacy.Explainer10 Mar 2026
- ExplainerInternal tools literacy: what every team should understand about its own toolsSystems logic, integration, performance, and adoption: the four things that decide whether an internal tool keeps working.Explainer25 Feb 2026
- How-toThe security and compliance checklist to run before buying low-codeRBAC, audit logging, encryption, SSO, and the compliance frameworks to check before a low-code platform reaches procurement.How-to13 Nov 2025
- How-toGiving a low-code app a real back end with SupabaseAuth, storage, and database logic for a Retool or FlutterFlow app, without writing a custom API.How-to08 Oct 2025
- How-toHow to build internal software that still works as the business growsArchitecture choices that keep a Retool app from needing a rebuild every two years.How-to01 Oct 2025
- DecisionThe ROI of low-code: the numbers to see before you commitTime to market, build cost, and maintenance cost, measured before and after, with two customer examples.Decision24 Sept 2025
- ExplainerWhat your security team will ask about low-code, and the answersAccess control, data exposure, integrations, and compliance: the four questions every low-code review comes back to.Explainer19 Sept 2025
- ExplainerWhy agile works on low-code internal tool buildsClinic staff asked to see client records across locations. The feature was designed and tested in days.Explainer05 Sept 2025
- ComparisonLow-code or no-code: the choice that matters two years from nowA cost and maintenance comparison for teams picking a platform they will still be running in two years.Comparison03 Sept 2025
- ExplainerBack-office automation: what operations teams automate firstApproval chains in an inbox, documents made by hand, re-keying between systems. Where automation pays back first.Explainer30 Jul 2025
- ComparisonLow-code or traditional development: which fits your stack?Total cost, security, lock-in, and a selection matrix you can use on your next build.Comparison23 Jul 2025
- How-toCool demo. Now what? Building production-ready internal toolsFrom a prototype that works on your machine to a tool IT will sign off.How-to18 Jul 2025
- ExplainerWhat is low-code, and why do operations teams use it?Low-code explained for the people who have to run operations on it.Explainer16 Jul 2025
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 storiesstackdrop stories --latest 3zsh