How To Kick SaaS
  • Introduction
  • Forward
  • Who & How
  • The business of SaaS
    • The Business of SaaS
    • Basic Lessons of Saas
    • The Process
    • Parts of a SaaS
  • Validating You SaaS
    • Validating Your SaaS
    • What happens when you don't validate
    • The SaaS Validation Process
      • Why are you doing this?
      • Should you do this?
      • Competition Analysis
      • Buyer Analysis
      • Sales & Distribution
      • Time & Money
      • The Secret Sauce
      • Buyer Categorization By Sales Method
      • The Advisory Approach
    • Validation Success
  • SaaS Build Process
    • SaaS Build Lessons
    • Planning & Costing
      • The Costing Process
      • The Estimate
      • The Scope of Work
      • Information Architecture Development
      • Working Numbers
      • The Project Plan
    • Build Team Roles
      • What To Expect From Your SaaS Development Team
      • Build Teams
      • The Project Manager
      • Information Architect
      • UX Designer
      • Developers
      • Quality Assurance
    • Standard Tools
      • Project Management Tools in SaaS Development
      • Development Environment & Dependencies
      • Remote Development Environments
      • Code Repositories in SaaS Development
      • Monitoring Your SaaS
    • Steps to Developing a SaaS
      • What to expect in SaaS development
      • Systems Setup
      • Creative
      • Project Planning
      • SaaS User Experience (UX)
      • Concept Design
        • SaaS UX Design Case Study
      • Content Development
      • FrontEnd Development
      • BackEnd Development
      • Quality Assurance (QA)
      • Alpha Testing
      • Beta Testing
      • Launching Your SaaS
      • Continuous Integration
    • Things to know and expect
      • You MUST learn at least the basics of Project Management
      • Things you do and do not know
      • How to tell if your development team is working
      • Good, Cheap, Fast. Choose Two.
      • Positivity is Key in Management
      • Storytime: The Story of a Ton of Lost Users and Money!
      • Development is iterative
      • Development Time Increases As Complexity Increases
      • Storytime: Don't Send Me Shit
      • Story Time: The Best of the Best
      • Sunk Costs
    • Your SaaS MVP Pre-Development Build Checklist
  • Appraisement: Pricing Your SaaS
    • Appraisement: SaaS Pricing
    • SaaS Pricing Metrics
    • SaaS Pricing Metrics Glossary
    • Science of Pricing
    • What You Need To Know About Your Customers
    • How To Price Your SaaS
    • Customer Types Case Study
    • Storytime With Brennan
    • Pricing Page: The Most Valuable Page On Your Website
      • Pricing Page Examples
  • Acquisition: Gaining SaaS Users
    • Acquisition: Getting SaaS Users
    • SaaS Traction Lessons
    • Acquiring your first users
    • Getting ready for growth
    • Organic Search Marketing
      • Content Marketing Is An Investment
      • Step 1: Keyword Research
      • Step 2: Content Planning
      • Step 3: Writing, Formatting, & Beyond
    • Marketing Automation in SaaS
      • Marketing Automation Basics
      • Storytime: Learning about marketing automation the hard way
      • Lead Scoring, Tagging, & Triggers
      • Marketing Automation Systems
    • Lifetime Deals
    • Outbound Campaigns
    • Affiliates & Partnerships for SaaS Businesses
    • Narrowing Your Message With Adaptive Design
    • Social Media Marketing
      • Social Media Retargeting
      • Testing your social media ads
      • Social Media Ad Tricks
    • Pay Per Click (PPC)
    • SaaS Software Checklist
    • Email Marketing
    • The Marketing Website
  • Activiation
    • Activation
    • Getting Personal
    • Stalking Your Users
    • Onboarding
    • Training Webinars
    • Onboarding Emails
    • New User Tour
    • Setup Checklist
  • Attrition: Supporting Your Community and Growing Your Business
    • Supporting Your SaaS Customers
    • SaaS Community Building
    • Chatbots
    • Events
    • Swag
    • Education
    • The Knowledge Base
  • NOTES
    • NOTES
    • The best growth hacks no one wants you to know
Powered by GitBook
On this page
  • If it’s good and cheap, it won’t be fast.
  • If it’s good and fast, it won’t be cheap.
  • If it’s fast and it’s cheap, it won’t be good.
  • This applies to all types of teams
  1. SaaS Build Process
  2. Things to know and expect

Good, Cheap, Fast. Choose Two.

PreviousHow to tell if your development team is workingNextPositivity is Key in Management

Last updated 6 years ago

This is a fundamental concept to understand. It is simple, but powerful.

If it’s good and cheap, it won’t be fast.

If something is good and you don’t spend much money on it it, the odds are whomever is building it, isn’t going to build it fast. That is because if you have someone who knows how to build something well, they are in demand from other organizations to build the same kinds of things. They are almost always going to prioritize the thing that is paying them more -- because they have to.

This is especially true in SaaS development because these systems are large, complex, and time consuming to build, and anyone who is worth their salt is in demand to build these kinds of systems right now.

If it’s good and fast, it won’t be cheap.

For exactly the same reason as the previous item, if something is done well and done quickly, it is going to cost more. You have a set amount of time it will take to build the system. The only way to decrease the amount of time is to decrease the functionality of the system in one way or another. So if you build it well, it costs more time, and to fit more hours into less days requires more people or longer days. Both of these increase your cost.

If it’s fast and it’s cheap, it won’t be good.

Think you’re getting a deal? One company is offering you something for a lot less than the others, so why not right? Let’s break it down one more time. It will take a set amount of time, with some variance but not that much, for any company to build the system. One company is cheaper and faster, that means they are using less expensive people and more of them. There is a bottom in pricing in this industry, no matter where you go in the world. Development is a worldwide business, so people in countries that have a lower cost of living that really know what they’re doing still know what they can charge, and it isn’t $10/hr.

So think about this, if there is a minimum rate for good developers, it will take a certain amount of time to do a project within a slim variance, and you have set number of features and thus time required. Then if someone is offering a cheaper price and to do something fast, they are either cutting time somewhere or don’t know what they’re doing. Unless they specifically show you that they have done the thing in the past, they almost certainly don’t know what they’re doing and you are going to have to start over.

This applies to all types of teams

What people don’t think about when they think about this rule is that this applies no matter what kind of team you’re working on. A SaaS project ALWAYS takes a certain amount of time, no matter who does it. Often times, more experienced, and thus more expensive people are faster. But the project still takes a certain amount of hours. So, if you have a team you put together, an agency, or your good friend Bill Gates doing this for you, if they are cutting or you think they are cutting you a deal these principles STILL APPLY.

So remember, if someone is going to ‘cut you a deal’ and you value time or quality of your product, know what you’re getting into. Caveat emptor (buyer beware)!

One of my first videos was on this concept.