La Fleur Mockup
ArchivedJune 1, 2018
An unsolicited website redesign mockup for a local business — a lesson in creating your own opportunities by improving someone else's digital footprint and using it to build real industry relationships.
Purpose
Picked a local business with a weak web presence, redesigned their site from scratch as a mockup, and used it as a conversation starter. The goal was not just practice — it was proof that you can create professional opportunities out of thin air.
Stack
What I Learned
- You do not need permission to improve something — find a business with a weak digital footprint, build a better version, and show it to them
- The barrier between "student" and "professional" is self-imposed. The moment you deem yourself capable enough to judge and improve a real business's website, you have crossed it
- Giving away work strategically is not charity — it is relationship-building. A free mockup that lands a conversation with a business owner is worth more than any cold email
- The mockup does not need to be perfect. It needs to be obviously better than what they have. That delta is the pitch.
Key Insights
- In the age of AI, this approach is absurdly powerful. What used to take a weekend of grinding out HTML and CSS can now be done in hours with an AI agent. Find a business with a bad website, prompt an agent to redesign it, hand the business owner a polished mockup, and you have a working relationship for almost zero difficulty.
- The skill is not the code — it is the taste to identify what is broken, the initiative to fix it unprompted, and the social awareness to present it as a gift rather than a critique
- This is a repeatable playbook: spot a weak digital presence, improve it speculatively, deliver the improvement. It works for freelancers, agencies, and anyone trying to build a portfolio of real-world work without waiting for someone to hire them first.
This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.