Engineering Firm Website
Designing a Digital Foundation
Client management
Rapid turnarounds
Stakeholder alignment
The Client and the Challenge
Building For Clarity and Credibility
A civil engineering business owner wanted to grow through a website that passively advertises his services with clarity, credibility, and trust.
Goal
Build Trust Fast With Prospective Clients
Turn the client’s site from a resume into a credible, lead-supporting website with clearer structure and stronger decision-making around layout and content priorities.
Timeline
6 months
Role
Web designer
Deliverables
Squarespace site
Tools
Figma, FigJam
My Process
Get Design Feedback Early
1
Design sprint
1-week Figma prototype sprint, building small galleries of distinct directions so the client could choose a path quickly.
Iterative building
Iterative building using feedback loops from the clients, translating requests into business coming.
2
Scope check
Owning scope control by clarifying ownership of copy up front and revisions to prevent “client homework” and reduce churn.
3
What Worked Best
Project Wins and Honorable Mentions
Presenting a few strong choices with tradeoffs increased buy-in and reduced second-guessing later.
Option-Based Decision Making
Clear boundaries in the design proposal kept the project focused and predictable. Set expections for a two-phase launch.
Setting Timeline Expecations
Constraint-Based Reasoning
All decisions are grounded in feasibility, time, and budget. Any decision was filtered through these 3 factors and was appreciated by the client.
Projected timeline with client decision tracking.
Copious notes and time-tracking to cover our bases.
Site map artifact generated from an information architecture workshop.
Results
Clarity First. Rework Last.
Early concepts and clear tradeoffs got us on the same page quickly.
Faster alignment on direction
Less rework in revisions
A shared rationale reduced second-guessing and kept changes focused.
Repeatable approach
I turned the process into a reusable playbook I now use with clients.
How My Process Changed
From Project to Playbook
Standardized onboarding process
So every project starts the same way.
Confirm prototype-first alignment
Before any build work begins.
Strengthen service agreements
For scope clarity and change requests.
Offer ongoing site management
For SEO, post-launch maintenance.
Home page before and after comparison.
Early version mockup with client notes.
About section updated with more value-centered copy.
Typescale used for global font settings.