From 100 to 2,500 Users: What We Shipped, What We Learned, and Thank You

A few months ago we wrote a short post celebrating our first 100 users. This week, Decky crossed 2,500.

For a small team building enterprise software for corporate presentations, that number is not an abstraction. It is 2,500 people who trusted an early product with their real sales decks, QBRs, board updates, and launch narratives. Before anything else: thank you.

Below is what actually happened between 100 and 2,500 - the things we shipped, the workflows that surprised us, and where we are pointing next.

The headline: we grew up as an enterprise product

The three biggest changes since the 100-user post are not features you can see on a marketing page. They are the things enterprise buyers ask about on the second call.

1. SOC 2 Type II

We are now SOC 2 Type II compliant. Type I proves you designed the controls. Type II proves you actually operated them, over months, under audit. It is the difference between "we have a security policy" and "here is the evidence, for every day of the observation window."

Practically, this unblocks legal and security reviews at mid-market and enterprise accounts that could previously only run us as a pilot. If you need our report, your account team can share it under NDA.

2. The enterprise admin layer

The single biggest lesson from 100 to 2,500 users: brand consistency is not a slide problem, it is a permissions problem. Great templates do not survive first contact with a 400-person sales org unless someone can see who is generating what, from which library, against which brand system.

So we built the admin layer enterprise buyers kept asking us for:

• Workspaces, roles, and SSO for real org structures - brand, revenue, ops, and regional teams with different libraries and templates.
• Slide Library governance - who can publish a slide into the shared library, who can only consume it, and what happens when a source slide changes downstream.
• Usage and generation visibility so leadership can actually see which templates are driving the most decks, which brand rules are being respected, and where the workflow is still leaking into "File > Make a Copy."
• Audit trail for every deck generated through Decky, tied back to the user, template, and library version.

This is the layer that made Decky a system of record for corporate presentations, not just a generator.

3. MCP support

We shipped an MCP server so Decky's slide libraries, templates, and generation actions are callable from any MCP-aware AI assistant - Claude, ChatGPT, internal agents, whatever your team standardizes on.

Why this matters for enterprise: the AI stack inside big companies is consolidating around a few assistants and a lot of internal tools. MCP lets Decky show up inside those assistants as a first-class tool - "draft a QBR for this account using our Q3 template and the latest Salesforce data" - without another tab, another login, or another prompt-engineering exercise.

For teams already using our REST API, MCP is the same capability surface, exposed in the shape modern AI agents expect.

What 2,500 users taught us about corporate presentations

A few patterns showed up over and over in the data and the customer calls.

• The highest-value decks are the boring ones. QBRs, renewal reviews, pipeline updates, monthly board slides. The "hero pitch deck" is what marketing pages sell; the recurring, templated decks are what actually eat a team's week.
• Brand teams do not want a design tool. They want a distribution problem solved. Their fonts, colors, and grid rules already exist. They need every rep, CSM, and PM to use them, in Google Slides and PowerPoint, without a design review.
• AI-generated slides only get used if they open in Google Slides or PowerPoint natively. Beautiful hosted web decks lose to a slightly-less-beautiful .pptx the client can edit. This is why we did not chase the "hosted web presentation" pattern.
• Templates beat generation. The number of decks produced from a governed Template dwarfs the number produced from an open prompt. Prompts are magical in demos; Templates are what teams live in.

What is next

The next chapter is about making Decky the connective tissue between the systems that already hold your company's truth - CRM, product data, brand systems, docs - and the deck that gets sent to a customer or a board.

Concretely, that means:

• Deeper Salesforce, HubSpot, and data-warehouse integrations for revenue decks.
• More MCP tools and agent-friendly primitives so Decky can be orchestrated by internal AI assistants, not just used directly.
• Expanded PowerPoint parity for enterprises still standardized on Office.
• More governance controls for the brand, security, and ops teams who own the "who can do what" question.

Thank you

To every one of our 2,500 users: thank you for using Decky on decks that actually matter, for telling us when something felt off, and for treating a young product like a real part of your workflow. We are building this for you.

If your team is still stuck between AI that breaks your brand and manual work that breaks your budget, we would love to show you what the last few months of work looks like. Book a demo and we will walk you through it.

Every deck on brand, in minutes.