Beyond Free Pizza: What Building a Friend’s Website Taught Me About Tech, Business & Boundaries
We’ve all been there. A friend, eyes wide with hopeful enthusiasm, says those fateful words: “You know computers, right? Could you maybe… build me a website?” For me, it started exactly like that. “I made a website for a friend once.” Sounds simple, maybe even fun – a chance to flex some skills, help someone out, maybe earn some goodwill (or pizza). What unfolded, however, was a crash course in far more than just HTML and CSS. It was a deep dive into the messy intersection of personal relationships, undefined expectations, and the realities of bringing a digital vision to life.
My friend, let’s call her Sarah, had a brilliant small business idea – handmade, eco-friendly ceramics. Her passion was palpable, her products beautiful. But her online presence? Non-existent. She needed a digital storefront, and fast. Eager to help and excited by the creative challenge, I jumped in, fueled by enthusiasm and the promise of gratitude (and yes, maybe that pizza). The initial phase felt great. Brainstorming layouts, choosing fonts that felt earthy and organic, setting up her first product listings – it was collaborative and fun.
The First Tremors: When “Simple” Isn’t Simple
The cracks began to show almost immediately, though I brushed them aside at first.
1. The Scope Creep Monster: What started as “just a few pages and a contact form” quickly evolved. “Oh, could we add an online booking system for workshops?” “Maybe a blog section where I share pottery techniques?” “Is it possible to integrate Instagram and Pinterest and have a newsletter signup pop-up?” Each new request felt small individually, but collectively, they transformed the project’s scale and complexity exponentially. I hadn’t established clear boundaries or a defined project scope upfront. My mistake.
2. The “Free” Factor: Because it was for a friend, I hesitated to talk about value, time, or limitations. “It’s just a favor,” I told myself. But my evenings and weekends began disappearing into coding fixes, image optimization battles, and wrestling with a clunky e-commerce plugin. The lack of formal agreement meant Sarah understandably saw this as an open-ended favor, while I was sinking significant unpaid hours into it. Resentment, subtly at first, started brewing on my end.
3. Communication Breakdowns: Assumptions became our downfall. I assumed she understood basic web concepts; she assumed I could magically implement every feature she saw on massive corporate sites instantly. Feedback cycles were vague: “I don’t like how it looks” without specifics. My explanations about technical constraints often met with polite confusion. We weren’t speaking the same language, and we lacked a process for clear, constructive feedback.
4. The Hosting & Domain Headache: I naively set everything up under my own hosting account and registered the domain in my name initially, intending to transfer it later. This created an unnecessary tangle. When Sarah needed access or I needed payment for renewal (years down the line!), it became awkward. Ownership was muddy.
The Hard-Won Lessons: More Valuable Than Any Payment
Despite the frustrations, the website eventually launched. Sarah was thrilled, her business gained visibility, and that was genuinely rewarding. But the real value lay in the brutal, practical education I received:
1. Define Scope Like Your Sanity Depends On It (It Does): Even for friends, write down what you will do and, crucially, what you WON’T do. Be specific: “Includes 5 pages (Home, About, Products, Contact, Blog), basic contact form, and integration with X payment processor. Does not include ongoing blog writing, social media management, or advanced booking systems.” Get mutual agreement before you start coding.
2. Value Your Time & Skill, Even Among Friends: “Free” projects breed unrealistic expectations and resentment. Offer a clear, friendly alternative: a significant discount, a trade of services (her pottery for your web work?), or a capped number of hours. Acknowledge the value exchange. If truly free, explicitly state the limits: “I can dedicate 10 hours to setting up the basic site.” This protects the friendship.
3. Communicate Proactively and Set Expectations: Don’t assume technical knowledge. Explain processes, timelines, and potential roadblocks in plain language. Establish regular, short check-ins. Provide clear ways for feedback: “Instead of ‘I don’t like it,’ could you tell me what specifically feels off? The colors, the spacing, the font?” Use visual aids like screenshots.
4. Ownership & Logistics from Day One: Register the domain and set up hosting in the CLIENT’S name (your friend’s name/business), using their payment details. Provide them with all login credentials securely as soon as the basic setup is done. This prevents future headaches and establishes clear ownership. Document everything.
5. Learn to Say “No” (Kindly): Scope creep is inevitable. Be prepared to say, “That’s a great idea for phase 2! For this initial launch, as we agreed, we’re focusing on X, Y, Z. Adding that now would take significant extra time/cost.” Offer alternatives if possible, but hold the boundary.
6. Under-Promise, Over-Deliver (Within Scope): It’s better to estimate conservatively and finish early than to miss a deadline you set too optimistically. Manage expectations about timelines realistically, factoring in your other commitments.
7. Document Your Work: Keep notes on decisions made, code snippets, plugin configurations. This helps immensely if they need future help (even from someone else) or if you need to revisit the site months later.
Why This “Simple” Favor Matters
Building that website for Sarah was far more than a technical exercise. It was a microcosm of client relationships, project management, and professional boundaries. These lessons are universal:
For New Developers/Freelancers: Your first projects are invaluable learning labs, but protect yourself. Practice setting boundaries and clear communication now. It gets harder later.
For Small Business Owners (like Sarah): Understand that a website, even a “simple” one, involves real skill, time, and costs. Value the person helping you. Be clear about your needs and budget (even if that budget is gratitude and pizza plus respect for their time limits). Ask questions!
For Anyone Doing Favors: Be honest about your capacity. A smaller favor done well is infinitely better than a massive, half-finished project that strains the relationship. It’s okay to say, “I’d love to help, but I only have capacity for X right now.”
“I made a website for a friend once.” It sounds like the start of a simple story. But for many of us, it’s the beginning of a profound lesson in navigating the often-tricky waters where personal goodwill meets professional demands. That little ceramics site helped Sarah sell her wares, but it taught me about respect – for my own time, my skills, and the importance of clear agreements, even between friends. The next time the question comes, I’ll still likely say yes (I love building things!), but it will be a very different, much healthier “yes,” grounded in the hard-earned wisdom of that first, well-intentioned project. The pizza tasted better that way too.
Please indicate: Thinking In Educating » Beyond Free Pizza: What Building a Friend’s Website Taught Me About Tech, Business & Boundaries