What I've Learned After Building Websites for Local Businesses as a Web Designer

Blend Designs — Sun, 19 Apr 2026 09:54:57 +0000

I'm a web designer based in Melbourne, Australia. Over the past few years I've designed and built websites for lawyers, restaurants, trades businesses, real estate agents, and e-commerce brands - and the lessons I've learned have almost nothing to do with code.

Here's what actually matters when you do this professionally.

1. Clients Don't Buy Websites - They Buy Outcomes
The biggest mindset shift early in my career: stop leading with "I build websites" and start asking "what do you need more of - phone calls, bookings, online sales?"

A tradie doesn't care about React. They care that when someone Googles "plumber Melbourne" at 9pm, their phone rings.

Once I started framing every project around the client's actual business goal, my close rate went up and scope creep went down. The website becomes the vehicle, not the product.

2. Speed and Mobile Are Non-Negotiable - But Most Local Business Sites Fail Both
I audit competitor sites before every pitch. The average local business website in Melbourne:

Takes 6-9 seconds to load on mobile
Has images that aren't compressed
Isn't optimized for touch
Has a phone number that isn't a tap-to-call link

These aren't design problems. They're conversion problems. Fixing them is one of the fastest ways to show ROI to a new client within the first month.

3. The Homepage Doesn't Matter as Much as You Think
Most clients obsess over the homepage. Most visitors land on a service page, an industry page, or a blog post from Google.

I spend more time on the pages that actually get organic traffic - the "web design for lawyers Melbourne" pages, the "how much does a website cost" blog posts, the suburb-targeted landing pages. These are the pages working 24/7 to bring in leads.

At Blend Designs I build these programmatically so a client can have 50 targeted pages live at once without writing each one by hand.

4. Design Trends Are a Tool, Not a Goal
Glassmorphism, 3D elements, animated gradients - these look incredible when used with restraint. But I've seen stunning portfolio sites that convert terribly because the visitor couldn't find the phone number.

My rule: one "wow" moment per page, then get out of the way. The animation draws attention. The clear headline holds it. The CTA converts it.

5. The Clients Who Invest in SEO from Day One Win Long-Term
I've had clients launch a beautiful site, get zero traffic, and blame the design. The design was fine — they had no Google presence.

I now push every client toward at least basic on-page SEO at launch: proper title tags, local business schema, a Google Business Profile linked to the site, and at least one piece of content targeting their main keyword.

The businesses that do this from day one are still thanking me 18 months later. The ones who skip it come back frustrated.

6. Your Portfolio Is Your Most Important Sales Tool
No one hires a web designer without seeing their work. My entire business changed when I started treating my own website like a client project - with the same care, the same performance standards, the same attention to mobile.

If your portfolio site is slow, outdated, or hard to navigate, that's the first impression. You're telling potential clients exactly what their website will look like.

7. Referrals Beat Every Marketing Channel
Paid ads, cold email, social media - I've tried all of them. Nothing comes close to a happy client telling someone they trust.

The practical version of this: follow up with every client 60 days after launch. Ask how the site is performing. Offer to fix anything that isn't working. That follow-up call has generated more new business than any campaign I've run.

What I'd Tell Someone Starting Out

Pick a niche early. "Web designer for restaurants" books more work than "web designer."
Learn enough SEO to have an intelligent conversation about it. Clients who understand its value are your best clients.
Build your own site properly. It's free advertising that works while you sleep.
Charge what the outcome is worth, not what your hours are worth.

If you're a business owner reading this and wondering whether your current website is working as hard as it should — that's a question worth answering. You can see the kind of work I do at Blend Designs.

And if you're a fellow web designer, I'd love to hear what's worked (or hasn't) for you in the comments.

I built an AI contract analyzer in 6 weeks - here's what I learned about prompting Claude for structured output

Blend Designs — Sun, 19 Apr 2026 09:39:51 +0000

Six weeks ago I had an idea. Today it's a live product
with real users.

fynPrint reads any contract (PDF or DOCX), flags risky
clauses in plain English, and writes the negotiation email
for you.

The stack:

Next.js 14 + TypeScript + Tailwind (App Router)
Supabase (PostgreSQL + encryption at rest)
Clerk for auth
Claude Sonnet 4.6 API with zero data retention
Stripe (credit-based pricing)
Vercel

The hardest part - prompting Claude for consistent
structured JSON:

Getting reliable JSON output with risk scores, confidence
levels, and plain-language explanations per clause took
a lot of iteration. The key things that worked:

Be extremely specific about the exact JSON structure
you want. Include field names, types, and examples.
Tell Claude explicitly what NOT to include in low-risk
clauses to reduce output tokens and speed up response time.
Add "Return ONLY valid JSON. No markdown, no code
fences, no preamble." at the end of every prompt -
without this you'll get inconsistent formatting.
For the negotiation email, pass only the selected
high-risk clauses back to Claude, not the full analysis -
keeps the second API call fast and cheap.

Pricing decision:
Went credit-based ($2.99 per analysis) instead of
subscriptions. Most freelancers don't sign contracts every
week - a monthly subscription felt wrong for that use case.

Looking for beta testers:
If you're a developer who freelances and signs client
contracts, I'd love your honest feedback on the analysis accuracy.
5 free credits - just sign up at fynprint and DM me.

Happy to answer questions about the architecture or
prompting approach in the comments.

DEV Community: Blend Designs

What I've Learned After Building Websites for Local Businesses as a Web Designer

I built an AI contract analyzer in 6 weeks - here's what I learned about prompting Claude for structured output