The rebrand is the smallest thing we changed.
reading · 00%

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.

Published
Reading3 min
CategoryCompany news
Words663

New mark, new site. Underneath, two years of rebuilding how Stackdrop works.

A new logo is the easy part. In the last two years we rebuilt the way Stackdrop runs, from the products we ship to the compute nodes our test suite now needs, and our new website is one of the systems that came out of it.

Here is what changed.

The company outgrew its description. Finally.

Two years ago our website said we build web products, and we were already past that. Today it's three hundred systems and 20+ specialists in four countries. Fortune 100 companies are on the customer list, across more industries, teams, and job titles than that homepage could spell.

What we build: portals, workflows, consoles, automations, internal tools, and more. On top of whatever you already run, or from scratch when nothing off the shelf fits. Three hundred or so of those is how you get specialists instead of generalists: people who have made the call before, in production, and know which ones hold up.

We're an Official Retool Partner and an Official Anthropic Partner now. Products Lab has two products out, fully AI-pilled, already live. More are in the works.

And we did it to ourselves too. Everything we need to run Stackdrop, from project allocation to invoicing, lives on software we built. This website is one of those systems.

So "web products" stopped being the job a while ago. We just hadn't updated the docs.

Here's the description that fits: Stackdrop is the technical lead that builds, together with your team, the software your business depends on. With your team, not around it. Your product owner keeps the final say, and we make the ramp a lot smoother.

One block. One cut. One drop.

Our new mark is that sentence, drawn. The block is the software your business runs on. Then the business moved, but the software didn't, and a corner went missing. You know the corner: the spreadsheet, the script, the workarounds of workarounds. Every team we have ever met has one. Most have a drawer full.

Into the cut drops one amber bar. That's us.

And the last bit of the corner stays open. On purpose. Your business will move again, and the system leaves room for it. We did check the rounded-corner option, by the way. Still square.

One thing hasn't changed: Stackdrop ships what you started.

Most of the time you've already started. A prototype, a spreadsheet that became a system, a build a vendor walked away from. Sometimes we keep it. Sometimes we don't. First we work out what it was built to do, where you need it to go, and how much room it has to grow. Then we lay out the paths, with the limits of each one, and tell you which we'd take and why. That part has never changed. It just has a better logo now.

First we shape it. A technical lead owns the architecture from the first call, and we interview everyone who touches the process, in your tools, on your data. Not because it's a nice ritual. Because the brief is never the whole problem. You asked for one thing. Inside it was what you actually needed.

Then we build it, with you. Weekly cycles, and a working surface over a slide deck. Your product owner keeps the final say and can say no. They do, sometimes. That's the point.

Then we run it. Deployment, monitoring, new surfaces, new integrations, and the edge cases nobody foresaw. Especially those. Nothing ships on vibes.

The final goal is boring on purpose: a reliable system in production, used every day, by people who stopped noticing the pain. Not a demo. Not a handover doc and a goodbye.

That is the rebrand. Same team, same founder, same way of working. Now with a look that finally feels like us. Have a look around.

Speak soon,
John

P.S. Up, up, down, down. Left, right. You know the rest.

Filed underCompany news
Worth passing along? Share this note.
LinkedInX
Rather not build it yourself

You read the notes. We can write the code

Before we quote, an hour with the people who use the current process.

Founder

John Miniadis

Keep readingCompany news
Related notes

Still here? Good sign

More notes from real builds, written up for the next person who needs one.

All articles
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?