The Cost of Racing Toward Success

4 MIN READ
MIN READ

LogDNA is now Mezmo but the product you know and love is here to stay.

LogDNA recently celebrated 5 years since our launch in Y Combinator and during this half-a-decade we’ve learned several lessons about balancing cost and scalability. As a founder, here are the top 3 things I wish someone had told me as we were racing towards success.

Cloud-Native Costs Will Kill You

The appeal of building a cloud-native application for a startup is a no brainerit’s agile, scalable, and can be managed by a distributed team. Not to mention, it’s the cheapest way to get off the ground. However, like many resources, costs can add up if you aren’t paying close attention.

Be prepared to manage cloud costs at the outset to ensure you’ll be able to scale without being blindsided by hidden expenses for things like migration and run time. When we were getting started, we used credits from multiple cloud providers to host our product. Back then, we didn’t consider this a multi-cloud strategy, it was just a way to keep our costs low (now we realize that doing this helped us solve problems that larger enterprises are just tackling today). 

In my experience, smaller companies are better at controlling the costs of their workloads as the bottom line feels very real when you’re the one building the technology and paying the bills. But, as your company scales, there will come a breaking point where you need to weigh the pros and cons of moving fast versus growing sustainably. Our breaking point was when our cloud hosting bill exceeded our personnel costs. At that point, about 40% of our total spend was going towards servers alone and we knew we needed to find a more sustainable solution. For us, that was moving to bare metal, and we found an awesome partner in Equinix Metal (back then they were known as Packet). Their bare metal offering provided the scalability of cloud but the cost and ability to customize that we needed to grow. For example, instead of using a cloud Kubernetes service like AKS or GKE, we built a custom Kubernetes solution to meet our exact requirements. 

Prove Your Market Fit, Then Worry About Optimization

If you’re a cash-strapped startup, you might think that your number one priority is to maintain a long runway and show investors that you’re being smart with their money. It’s easy to fall into that line of thinking. If your product doesn’t have a clean and clear fit into the market, you will ultimately struggle, no matter how conservative you are with capital or how innovative and groundbreaking your technology is. A product needs to solve challenges that have a significant enough impact that people are willing to invest in the solution. Read that again—your number one priority is to solve a problem worth solving. 

Use your network to attract beta testers and get their feedback about the onboarding experience and how long it took them to see value from the product. If it takes a significant amount of time and effort to get a proof of concept and deploy a solution, it will be extremely hard to sell. Marketing to early adopters is also important. Don’t be afraid to target specific personas or a niche market. This helps you gather focused feedback and build a strong, loyal following. 

Once you’ve proven your market fit, you can think about optimization. Many people look to systems and infrastructure when considering optimization, and there are definitely some wins to be had here. For us, ensuring that our engineering team was appropriately balancing workloads to optimize the use of resources helped with system performance and managing costs. We also focused on developer productivity and efficiency. This isn’t unique to LogDNA, as operations shift left, your developers play an important role in keeping your products functioning seamlessly. Invest in the tools and resources they need to move fast, debug with ease and continuously innovate. DevOps tools like logging are important as it provides developers with insight—both for debugging and identifying trends in app performance that can be used to prevent future problems. Developer tools are often the second highest expense for startups. Companies should use tools that give them control over usage and spend, while enabling development teams to access the data they need to optimize their productivity. Ultimately, this ensures they have more time to build revenue-driving products and features.

Shortcutting Security is a Fast Track to Failure

We’ve seen a lot of high-profile breaches in the news lately, proving that no one is immune to an attack. For a SaaS provider, security is an ethical obligation, but it can seem expensive when you’re young. 

We chose early on to be secure by design. It was a straightforward decision since we knew that we wanted to operate globally within highly regulated markets such as healthcare and finance. These industries have strict security and privacy mandates so we chose to build security and compliance into the core of the LogDNA product. Now, that’s enabled us to move a lot faster while competitors catch up with ever-changing compliance regulations. In 2015, this was a differentiator but now it’s table stakes to gain the trust and confidence of companies that engage with you. Don’t cut corners here, invest from the start. 

Final Thoughts

As you get off the ground, use the resources that are available to you and create a strategy that will help you race toward success. I’ve learned that the key is to stay focused, consider how your product adds value, and look for signs for when it is time to optimize. Setting this foundation now will help you move a lot faster in 5 years when your market may be ripe for the picking. 


Table of Contents

    Share Article

    RSS Feed

    Next blog post
    You're viewing our latest blog post.
    Previous blog post
    You're viewing our oldest blog post.
    Mezmo + Catchpoint deliver observability SREs can rely on
    Mezmo’s AI-powered Site Reliability Engineering (SRE) agent for Root Cause Analysis (RCA)
    What is Active Telemetry
    Launching an agentic SRE for root cause analysis
    Paving the way for a new era: Mezmo's Active Telemetry
    The Answer to SRE Agent Failures: Context Engineering
    Empowering an MCP server with a telemetry pipeline
    The Debugging Bottleneck: A Manual Log-Sifting Expedition
    The Smartest Member of Your Developer Ecosystem: Introducing the Mezmo MCP Server
    Your New AI Assistant for a Smarter Workflow
    The Observability Problem Isn't Data Volume Anymore—It's Context
    Beyond the Pipeline: Data Isn't Oil, It's Power.
    The Platform Engineer's Playbook: Mastering OpenTelemetry & Compliance with Mezmo and Dynatrace
    From Alert to Answer in Seconds: Accelerating Incident Response in Dynatrace
    Taming Your Dynatrace Bill: How to Cut Observability Costs, Not Visibility
    Architecting for Value: A Playbook for Sustainable Observability
    How to Cut Observability Costs with Synthetic Monitoring and Responsive Pipelines
    Unlock Deeper Insights: Introducing GitLab Event Integration with Mezmo
    Introducing the New Mezmo Product Homepage
    The Inconvenient Truth About AI Ethics in Observability
    Observability's Moneyball Moment: How AI Is Changing the Game (Not Ending It)
    Do you Grok It?
    Top Five Reasons Telemetry Pipelines Should Be on Every Engineer’s Radar
    Is It a Cup or a Pot? Helping You Pinpoint the Problem—and Sleep Through the Night
    Smarter Telemetry Pipelines: The Key to Cutting Datadog Costs and Observability Chaos
    Why Datadog Falls Short for Log Management and What to Do Instead
    Telemetry for Modern Apps: Reducing MTTR with Smarter Signals
    Transforming Observability: Simpler, Smarter, and More Affordable Data Control
    Datadog: The Good, The Bad, The Costly
    Mezmo Recognized with 25 G2 Awards for Spring 2025
    Reducing Telemetry Toil with Rapid Pipelining
    Cut Costs, Not Insights:   A Practical Guide to Telemetry Data Optimization
    Webinar Recap: Telemetry Pipeline 101
    Petabyte Scale, Gigabyte Costs: Mezmo’s Evolution from ElasticSearch to Quickwit
    2024 Recap - Highlights of Mezmo’s product enhancements
    My Favorite Observability and DevOps Articles of 2024
    AWS re:Invent ‘24: Generative AI Observability, Platform Engineering, and 99.9995% Availability
    From Gartner IOCS 2024 Conference: AI, Observability Data, and Telemetry Pipelines
    Our team’s learnings from Kubecon: Use Exemplars, Configuring OTel, and OTTL cookbook
    How Mezmo Uses a Telemetry Pipeline to Handle Metrics, Part II
    Webinar Recap: 2024 DORA Report: Accelerate State of DevOps
    Kubecon ‘24 recap: Patent Trolls, OTel Lessons at Scale, and Principle Platform Abstractions
    Announcing Mezmo Flow: Build a Telemetry Pipeline in 15 minutes
    Key Takeaways from the 2024 DORA Report
    Webinar Recap | Telemetry Data Management: Tales from the Trenches
    What are SLOs/SLIs/SLAs?
    Webinar Recap | Next Gen Log Management: Maximize Log Value with Telemetry Pipelines
    Creating In-Stream Alerts for Telemetry Data
    Creating Re-Usable Components for Telemetry Pipelines
    Optimizing Data for Service Management Objective Monitoring
    More Value From Your Logs: Next Generation Log Management from Mezmo
    A Day in the Life of a Mezmo SRE
    Webinar Recap: Applying a Data Engineering Approach to Telemetry Data
    Dogfooding at Mezmo: How we used telemetry pipeline to reduce data volume
    Unlocking Business Insights with Telemetry Pipelines
    Why Your Telemetry (Observability) Pipelines Need to be Responsive
    How Data Profiling Can Reduce Burnout
    Data Optimization Technique: Route Data to Specialized Processing Chains
    Data Privacy Takeaways from Gartner Security & Risk Summit
    Mastering Telemetry Pipelines: Driving Compliance and Data Optimization
    A Recap of Gartner Security and Risk Summit: GenAI, Augmented Cybersecurity, Burnout
    Why Telemetry Pipelines Should Be A Part Of Your Compliance Strategy
    Pipeline Module: Event to Metric
    Telemetry Data Compliance Module
    OpenTelemetry: The Key To Unified Telemetry Data
    Data optimization technique: convert events to metrics
    What’s New With Mezmo: In-stream Alerting
    How Mezmo Used Telemetry Pipeline to Handle Metrics
    Webinar Recap: Mastering Telemetry Pipelines - A DevOps Lifecycle Approach to Data Management
    Open-source Telemetry Pipelines: An Overview
    SRECon Recap: Product Reliability, Burn Out, and more
    Webinar Recap: How to Manage Telemetry Data with Confidence
    Webinar Recap: Myths and Realities in Telemetry Data Handling
    Using Vector to Build a Telemetry Pipeline Solution
    Managing Telemetry Data Overflow in Kubernetes with Resource Quotas and Limits
    How To Optimize Telemetry Pipelines For Better Observability and Security
    Gartner IOCS Conference Recap: Monitoring and Observing Environments with Telemetry Pipelines
    AWS re:Invent 2023 highlights: Observability at Stripe, Capital One, and McDonald’s
    Webinar Recap: Best Practices for Observability Pipelines
    Introducing Responsive Pipelines from Mezmo
    My First KubeCon - Tales of the K8’s community, DE&I, sustainability, and OTel
    Modernize Telemetry Pipeline Management with Mezmo Pipeline as Code
    How To Profile and Optimize Telemetry Data: A Deep Dive
    Kubernetes Telemetry Data Optimization in Five Steps with Mezmo
    Introducing Mezmo Edge: A Secure Approach To Telemetry Data
    Understand Kubernetes Telemetry Data Immediately With Mezmo’s Welcome Pipeline
    Unearthing Gold: Deriving Metrics from Logs with Mezmo Telemetry Pipeline
    Webinar Recap: The Single Pane of Glass Myth
    Empower Observability Engineers: Enhance Engineering With Mezmo
    Webinar Recap: How to Get More Out of Your Log Data
    Unraveling the Log Data Explosion: New Market Research Shows Trends and Challenges
    Webinar Recap: Unlocking the Full Value of Telemetry Data
    Data-Driven Decision Making: Leveraging Metrics and Logs-to-Metrics Processors
    How To Configure The Mezmo Telemetry Pipeline
    Supercharge Elasticsearch Observability With Telemetry Pipelines
    Enhancing Grafana Observability With Telemetry Pipelines
    Optimizing Your Splunk Experience with Telemetry Pipelines
    Webinar Recap: Unlocking Business Performance with Telemetry Data
    Enhancing Datadog Observability with Telemetry Pipelines
    Transforming Your Data With Telemetry Pipelines