Swizec Teller - a geek with a hatswizec.com

    Building software is a distraction

    We often write code to distract ourselves from the fact we don't know what we're building.

    Yesterday I had a long conversation with a friend who's starting a company. Let's call him Matt because that's not his name.

    After months of thought, Matt quit his job and went looking for investors. He realized it was too early and he doesn't know shit. So he started really digging into his idea and his market.

    He uncovered a goldmine.

    A swathe of the economy that's growing, inefficient, and needs some help. His wonderful idea will grease the wheels, the economy will flourish, the consumers will love him, and he'll get filthy rich in the process 💪

    Matt wanted my help hiring an engineer. Or a designer. Someone, anyone, who could help him build the product.

    Matt is not technical, you see. His skill lies in business development, sales, and big picture thinking. The skills you really need to succeed in the market he's targeting. The stuff us engineers run away from screaming.

    "How do I find an engineer? Someone local, someone I can sit down and work with, who won't rip me off."


    He's unfunded, bootstrapping, and on his own in San Francisco. Money is always tight when you have no income.

    "Mate, you're looking for a cofounder?"

    "Yeah but nobody I talked to wants to work for equity"

    Well yeah. You're a guy with an idea.

    "Matt, what have you done to prove people will pay for this? Why do you think you're ready to build software?"

    Hint: he isn't.

    Software is a tool, not a goal

    Through conversation we discovered that Matt wants to build software because his company doesn't feel real without it. You need something that you're building. You can't just "be a company".

    But you can.

    A company isn't the software it sells. A company isn't the offices. It isn't the team. It isn't even anything in particular.

    A company is a set of processes. A machine.

    Some of those processes are encoded in software, some are done by people, some aren't even documented. That's a company. That set of processes and ideas.

    Software is just a tool.

    What Matt needs are customers. People whose problem his solving. People who are better people because they use his service.

    That service is what he needs to build. Not some nebulous piece software the definition of which he doesn't even know yet.

    I dug deeper.

    "Matt, what do you need? What's blocking you from making your first sale?"

    Well I need a website.


    So I look real when I'm talking to people. So there's something to point them at.


    Because it builds credibility. Without a website I'm just a random schmo.

    Okay that's fair. Credibility and authority. You don't need a designer or even an engineer for that. You definitely don't need to hire anyone. Get an account on square space, carrd, or similar, pick the prettiest template you can find, and fill in your info.

    Voila, a website.

    You can even hire a freelancer to cobble it together for you. Don't waste money on a custom solution until you need one.

    Ok there's your website, you've got your credibility. What's next? Why do you need an engineer, Matt?

    Well I need to build the product.


    ... because I'm a product company? Because it isn't real without a product?


    Err ...

    Matt, did anyone pay you yet? Do you know exactly what they need to make their jobs easier? Have you talked to them?

    Well I know they have to fill out a form with 465 fields and reproduce it in triplicate and file it to the right people and it's just a mess and super hard and nobody wants to do that.

    Okay and you can make it easier with software?

    Yes! I can build a beautiful flow and a wonderful UI that guides them through needing just 250 fields it's gonna be amazing!

    And you need an engineer for that?

    Well I can't build it myself.

    Mate, you need a google form and some customer research. Go sell a shitty version of your product. No code, no software, just your elbow grease and a smile.

    People buy your solution, not your software

    People don't really care how you solve their problem. They just want somebody to do it for them.

    When I hire an accountant to do my taxes, I'm not buying the software they use, I'm buying peace of mind. The confidence that I won't overpay or underpay and that we'll find every legal loophole.

    When I pay for Spotify, I'm paying for ease of access to all the world's music. Their software, the player, just needs to be good enough.

    When I hire a lawyer to help me get a visa, I don't care what they use to make the process easier or their margins higher. I only care that I get my visa and Trump doesn't kick me out. That's it. That's what I'm paying for.

    And that was my advice to Matt.

    Build the service first. Solve somebody's problem. Make them a better human. Get paid.

    Then, when you're ready, when you feel the inefficiency deep within your bones, then build your software. You'll know what you need.



    Did you enjoy this article?

    Published on September 20th, 2019 in Business, Side Projects, Startups

    Learned something new?
    Want to become an expert?

    Here's how it works 👇

    Leave your email and I'll send you thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

    Join Swizec's Newsletter

    And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer? I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own?  Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created bySwizecwith ❤️