Pressure-test the plan
Pipeline grew 48% month-over-month to $955k — the strongest in our history. But we're not converting fast enough. Revenue is tracking 2.79% below budget across all channels. The Salesforce non-renewal creates a $600k gap we have to fill.
The mid-year gate is $1M enterprise ARR. We're close but not there. Our sales cycles are too long, our enterprise readiness (security, SLAs) isn't where it needs to be, and we're competing against Botify at $10–50k/month with a product that doesn't always feel enterprise-grade.
The EBITDA headroom exists to invest in this — but where exactly?
Partner ARR pipeline sits at $230k against a $500k gate. Salesforce — our largest partner — isn't renewing, creating a $600k revenue gap. We had a single-partner dependency and it's gone.
We have over $230k of partner-sourced opportunities in pipeline and are prioritizing technical partnership development. But we don't have a scalable partner program — it's been relationship-driven, not systematic.
The partner channel should be our most capital-efficient growth engine. It isn't yet.
Let's be honest: the product looks and feels like it barely works. The dashboard doesn't communicate value to non-technical users. 67% of new signups don't complete integration. The onboarding journey is confusing and unsupported.
Nexus (the integration copilot) was a downpayment, but it's missing critical pieces. Integration rates improved from 24% to 33% — progress, but still means two-thirds of potential customers drop off before they see any value.
Janine went through our onboarding as a customer in her first week. Her observations are probably the most honest assessment we have. We can't sell enterprise if the self-serve experience undermines our credibility.
We've done deep work on the category — "Machine Visibility" names the problem accurately and travels across audiences. But it hasn't landed in how we actually talk to customers.
Ask five people at Prerender what we do and you'll get five different answers. The ambiguity bleeds into sales conversations, marketing messaging, website copy, and internal alignment. We're not even consistent with each other, let alone the market.
This morning's Category Creation session gave us direction. This priority is about translating that into language everyone uses — consistently, starting tomorrow.
We have a proliferation of tools and silos and broken data streams. The stuff we need to know to do something is either missing or not trustworthy.
HubSpot doesn't have the data it needs. Mixpanel breaks silently when code changes. Automations that depend on these systems fail and nobody notices. The pricing project hit the wrong customers because we couldn't segment properly.
The Mixpanel integration is a patch. The real problem is that nobody has defined what data each system needs, where it comes from, and who owns keeping it clean. Every new integration is another patch on broken foundations.
Building PRISM helped me understand how little we have ever actually thought about security. We cache insecure pages and serve them to crawlers. I've seen hacking attempts coming through our proxy servers. There's no clean off-boarding process — people who've left the company may still have access. Everyone seems to have root access to everything.
We have no security program, no security owner, no regular audits. SOC2 was called out in the mandate as a Q3 prerequisite for enterprise scale. We're nowhere near it.
We're one incident away from a breach that destroys customer trust and kills our enterprise pipeline. This isn't hypothetical — the vulnerabilities are real and known.
Stability is improving — uptime meets contract SLAs now and MTTR is trending down. But the improvements are masking how fragile the foundation still is.
The system is full of accumulated technical decisions that create hidden risk. The cached_urls database is a ticking time bomb. Infrastructure migration is progressing but not complete. We're one edge case, one unexpected load spike, one misconfigured deployment away from a major incident.
We can't sell enterprise-grade reliability when we don't fully trust our own infrastructure. Charles's infrastructure migration is the right move — managed Kubernetes, auto-scaling, proper observability. But until it's complete, we're running on borrowed stability.