Last spring we worked with a small logistics startup in Lviv called Freta. The founder, Mariana, wanted a new site before a funding round in June. We had the kickoff call on a Tuesday. She expected a homepage concept by the following Monday. We told her it would take closer to three weeks before she saw a single pixel, and that the three weeks mattered more than the pixels would.
The gap between briefing and designing
Most clients think a web project starts with design and ends with development. In practice, the useful part of the process happens before either. It’s the stretch where you figure out what the site actually has to do, who reads it, and what happens if it fails. Skip that stretch and you end up designing opinions instead of answers.
What the brief doesn’t tell you
Freta’s brief was two pages long and mentioned words like “modern,” “trustworthy” and “scalable.” None of those are design instructions. They’re feelings. Our job in week one wasn’t to interpret the feelings but to find the decisions hiding underneath them: which three customer segments actually book shipments online, what the sales team currently says on calls that the website should say instead, and why the old site’s bounce rate was sitting at 71 percent on mobile.

Sitting with the material
We spent the first four days reading, not designing. Support tickets, the last twelve months of analytics, two investor decks, and a folder of competitor screenshots Mariana had saved. We also asked for call recordings. Listening to an actual sales call, where a prospect asks “wait, do you handle customs clearance or not,” tells you more about information architecture than any workshop does.
The three questions that actually matter
By day five we had boiled the whole brief down to three questions that the homepage needed to answer in under eight seconds: what does Freta move, who is it for, and how is it different from the three competitors already bookmarked in the client’s browser. Everything after that, every section, every piece of copy, got tested against those three questions. If a section didn’t help answer one of them, it moved further down the page or got cut.
A brief tells you what the client wants to say. Research tells you what the visitor needs to hear. The gap between those two is where the real project lives.
Structure before style
Only in the second week did we open Figma, and even then it wasn’t for visuals. We built a rough sitemap and a content outline, basically a document with headings and bullet points standing in for every section of every page. No colour, no typography, nothing a client could react to emotionally. This is the part people resist, because it feels slow and looks unimpressive, but it’s where you catch the expensive mistakes.
Catching problems on paper, not in code
In Freta’s outline, we discovered the pricing page needed four different structures depending on shipment type, something nobody had mentioned on the kickoff call. Finding that in a document took an afternoon of back and forth. Finding it after the page was built in Webflow would have taken a week of rework and an uncomfortable conversation about scope.
Bringing design in gradually
Once the outline was approved, we moved to low fidelity wireframes, still grey boxes and placeholder text, still deliberately ugly. The point of ugly wireframes is that clients comment on structure instead of colour. Mariana’s first note wasn’t “We don’t like the blue,” because there was no blue yet. It was “customers need to see transit times before pricing,” which is a far more useful note to get early.
Only after two rounds of wireframe feedback did we open a moodboard and start pulling references: shipping manifests, warehouse signage, the typography on cargo containers. That became the visual direction. By the time we designed the actual homepage, in week three, there were almost no surprises left to react to. The meeting where we presented it lasted twenty minutes and ended with one small change to a button label.
A rough shape for the early weeks
- Days 1 to 4: read everything, talk to the team, no opinions yet
- Day 5: write down the three or four questions the site must answer
- Days 6 to 8: build a content outline, no visuals
- Days 9 to 12: low fidelity wireframes, client feedback on structure only
- Days 13 to 15: visual direction and moodboard
- Day 16 onward: first real mockups
Why clients come around to the slower pace
Most clients are nervous about this timeline at first, because it feels like nothing visible is happening. We’ve started sharing a short written update at the end of each of those early days, even just three sentences, so they can see the thinking accumulate even when there’s nothing to look at yet. That small habit has done more to build trust than any deliverable.
What changes when you skip this part
We’ve been hired twice to rescue projects that skipped straight to design. Both times the symptom was the same: endless revision rounds that never converged, because nobody had agreed on what the site was supposed to do before arguing about what it should look like. Revisions on structure disguised as revisions on colour are the most expensive kind, because they’re the hardest to diagnose.
Freta’s site launched nine days before the funding round. Mariana told us afterward that the part she remembered most wasn’t the homepage design, it was a single line in the content outline that reframed how the company described itself. That line didn’t come from a design tool. It came from listening to a recorded sales call on a Wednesday afternoon in week one, before anything had a colour at all.
Leave a Reply