tm.← Back to journal

· 4 min read · Framer, Web Design, Process

How a premium site gets built in seven days


NPC Group got a premium interactive site in seven days: custom visuals, Lottie animation, five-star praise when it shipped. Fifty Two North, a real estate brand, got a full site in three days. SuperteamBLKN got one in under five hours.

None of those numbers are a trick. They're what happens when scope gets fixed before the clock starts, not during.

The compressed process

Every fast build follows roughly the same shape, whether it takes days or hours.

  1. Lock the structure first: pages, sections, the order someone scrolls through the story, before a single pixel gets styled.
  2. Design and build in the same pass, inside Framer, instead of finishing a Figma file and translating it afterward.
  3. Spend whatever time is left on motion and detail, once the structure is solid and approved.

That order matters more than the hours themselves. A seven-day build that spends three days on structure and four on polish will beat a seven-day build that spends five days redesigning the homepage twice and rushes everything else in two. Compression punishes indecision, not speed.

None of it works without a client who can approve fast. A seven-day build assumes same-day feedback, not a stakeholder chain that takes three days to sign off on a homepage. The tightest timelines aren't just a function of how fast I can design and build. They're a function of how fast the other side can look at something and say yes, change this, or ship it.

For NPC Group, seven days meant the structure had to be right early, because the remaining time went into the custom visuals and Lottie work that made the site feel premium instead of templated. SuperteamBLKN happened in under five hours, which leaves no real room for a redesign pass. Whatever gets approved in that first conversation is close to what ships.

What gets cut

Something always gets cut on a compressed timeline. The question is whether it's cut on purpose.

The first thing to go is usually scope, not quality: fewer sections, fewer states, fewer edge cases handled in the first version, rather than a rushed version of everything the client originally imagined. A site with fewer sections built well beats a site with twice as many and half of them unfinished.

The second thing to go is anything that needs its own review cycle. Custom illustration, bespoke 3D, anything that has to go back and forth for feedback before it's usable, doesn't fit inside a three-day or five-hour window. That work either gets simplified into something that can be finished in one pass, or it gets left out of version one entirely.

Copy and assets are the other place compressed timelines get exposed. A site can be built in days, but only if the words and images it needs already exist. Waiting on final copy or a brand shoot mid-build turns a five-hour job into a week and a seven-day job into a month. Fast builds move fast because everything the build depends on shows up on time, not because the design and development work itself gets rushed.

What doesn't get cut is the thing the client is actually paying for. The site works, it holds together on mobile, and it doesn't look rushed, even when it was.

Where Lottie earns its slot

NPC Group's site leans on Lottie for its motion, not custom 3D, and that isn't a budget compromise. It's the correct tool for a seven-day window.

A Lottie animation is a vector file that plays like video and weighs like an icon. It can be built, previewed, and swapped fast, without a render pipeline or a scene to light. On a build where every day is accounted for, that speed is the entire point. Spline or a custom 3D scene earns its place on a four-week build with room for iteration. It doesn't belong on a seven-day one, no matter how good it would look on a slide.

The visual result still reads as premium because the motion is doing real work, not sitting on top of a finished page as decoration. A well-placed Lottie loop on a hero section carries as much perceived quality as a heavier animation, at a fraction of the build time.

What "premium" means at speed

Premium at speed isn't about cramming a slower project into a smaller window. It's picking the version of the site that was always buildable in that window, and executing it without any of the usual hesitation.

Clients rarely notice the hours. They notice whether the site looks considered: whether the type is right, the motion has intent, the layout doesn't feel like a template with a new logo dropped in. None of that requires four weeks. It requires knowing, before day one, exactly what the days available can hold.