How to Make Freelancing Easier

Episode Summary

Executive Summary: The episode is a practical guide to making freelancing easier for web developers by reducing cognitive load in code, communication, scheduling, contracts, billing, taxes, and marketing. Scott and Wes emphasize repeatable systems, value-based pricing, clear client expectations, and using tools like calendars, CRMs, Sentry, Netlify, and accounting software to run freelancing like a business rather than a series of emergencies.

Main Topics: Reusable code and proven tech choices: Build a personal library of starters, snippets, component patterns, and familiar stacks so projects start faster and with less risk. The hosts argue for using stable, well-understood technologies over brand-new tools when deadlines matter. Communication and expectation management: Freelancers should communicate often, clearly, and without overwhelming clients with technical details. Regular updates, concise emails, and bounded availability reduce friction and decision fatigue. Time management and planning: Use calendars aggressively, set reminders, block focused work time, and avoid overcommitting. Time management is presented as essential both for meeting deadlines and for protecting uninterrupted development time. Contracts, quoting, and value-based billing: Create boilerplate contracts and estimate based on value rather than raw hours whenever possible. The episode argues that clear deliverables, scope exclusions, and pricing tied to business value are healthier than trading time for money. Taxes, accounting, and business separation: Freelancers should separate business and personal finances, withhold taxes from each payment, and use accounting tools to simplify bookkeeping and avoid tax-time surprises. Marketing, referrals, and niche positioning: Long-term freelance success depends on making it easy for others to understand what you do, targeting similar clients, and staying visible through referrals, CRMs, and genuine follow-up. When freelancing is or is not the right fit: Freelancing can be a stopgap or stepping stone, but not everyone will enjoy it. The hosts stress that there is no shame in choosing employment or other business models if freelancing is not fulfilling.

Key Arguments: Reusing code and standardizing your stack makes freelancing faster and lowers the mental burden of every new project. It is acceptable to exceed your estimated time internally when learning, but not to bill clients dishonestly for it. Choosing proven, stable technology is often smarter than using the newest framework or beta feature under deadline pressure. Clear, frequent communication matters more than technical detail; clients want progress updates, not architecture explanations. Freelancers should reduce client decision fatigue by asking fewer questions and making expert decisions when appropriate. Calendars and reminders are not optional; they are critical tools for remembering deadlines and protecting development blocks. Value-based billing aligns price with business value and avoids awkward hourly-trading dynamics. Contracts should be boilerplate but reviewed by a lawyer, and scope exclusions must be explicit. Taxes must be set aside immediately after payment because freelancers do not have withholding automatically handled for them. Marketing is mostly about clarity, reputation, and referrals; if people cannot explain what you do, you are not visible enough. If freelancing is not enjoyable or sustainable, it is valid to stop and pursue employment or another business path.

Data Points: Frequency of freelancing-focused episodes: about six months - The hosts mention it has been roughly six months since the last freelancing episode. Sample internal labor estimate: 5 hours - Used as an example of a freelancer’s initial estimate for a task. Mechanic book time example: 2 hours - The hosts describe a car repair billed as two book hours even if it is completed faster. Example of work taking longer than estimate: extra five hours - A mechanic learning a new repair may take several hours longer than book time. Example app/site age comparison: 10 years - Wes contrasts a WordPress site that ran for 10 years with a newer Node/React/Gatsby stack that had build issues after 6 months. Store locator reuse example: 5 or 6 different clients - Reusable code for a store locator was reused across multiple client projects. Code reuse percentage: 80% - Approximate share of code that can be reused from one similar client project to another. Response options example: 1, 2, or 3 - A suggested low-friction email format where clients reply with one of three options. Delay example: 1 week - A client not replying for a week is cited as a common source of schedule friction. Tax withholding example: 20% - Suggested amount to set aside for taxes in one example. Local tax example: 13% - Ontario HST rate mentioned when billing in-province clients. Small business support program: $40,000 - A government loan/program mentioned as available to small businesses during COVID. Forgivable portion of support program: 25% - Part of the small-business loan was forgivable. Forgivable amount example: $10,000 - Illustrative amount that could be forgiven from the $40,000 program. Gift card referral reward: $100 - A realtor sent a $100 gift card to a fancy steak restaurant for a referral. Follow-up gift card: $15 - The realtor later sent a Starbucks gift card as another small touchpoint. Episode reference: 117 - The hosts reference a prior Syntax Hasty Treat episode on emailing busy people. React course positioning: 101 - Wes describes his React course as a beginner-level introduction. Discount for Master Gatsby: $10 off - Scott mentions a coupon code that takes $10 off the course. Annual subscription discount: 25% - The React course mention includes a 25% savings if signing up for the year.

Pivotal Quotes: "The goal should be to reduce the cognitive overhead." — Wes: Discussing client communication and how to avoid overwhelming people with too much information. "Don't be upset if freelancing isn't for you." — Scott: Closing advice emphasizing that freelancing is optional and not a moral requirement for developers. "If you're not getting a no on your first quote, then you went too low." — Scott: Explaining value-based pricing and why freelancers should not undervalue their work.

Implications: Successful freelancing depends less on raw coding skill and more on systems: communication, scope control, pricing, taxes, and repeatable delivery. Developers who adopt those habits can grow sustainably; those who dislike the business side may be better off in a team role.