Maciaszek Szpotowicz
WMMS is a Warsaw-based architecture and interior design studio working at the top end of the residential market.
They came with a clear brief: communicate luxury through restraint. Monochromatic palette, deliberate use of space, typography and layout doing the heavy lifting. Nothing decorative.
- Client
Maciaszek Szpotowicz
- Industry
Architecture, Interior Design, Luxury Brands
- Scope of work
Brand Strategy, Visual Identity, Art Direction, Web Design, Webflow Development
First impression
During the strategy phase, a recurring idea emerged: WMMS wanted to communicate a certain kind of exclusivity — not through boldness, but through selective revelation. A glimpse before you're let in.
I translated that into a clip-path reveal hero animation: a full-screen architectural visualisation starts as a small cropped fragment — enough to pique interest without giving it away.
As you scroll, the fragment scales up to fill the screen, revealing the mystery and satisfying curiosity. By the time a user reads a single word, the page already conveys what WMMS is through visuals.
The animation is built with GSAP and ScrollTrigger, tied to scroll position and works responsively on desktop devices, hiding on mobile.
Flexible Systems, Distinct Experiences
The offering pages — architectural projects, WMMS Club, Identity Architecture — each have their own layout and animation system. Not to show technical range, but because each service has a different character and speaks to a different audience.
All pages pull data from Webflow's native CMS. The process step lists are built so animations work regardless of how many steps there are — you can add a new step through the CMS and it appears correctly on the page without touching the code. I used data attributes so the JavaScript targets the right elements dynamically.
Where possible — the services list, the Club partners section — elements are built as components using Component Slots. New entries can be added from the Webflow editor without any risk of breaking the layout or the underlying structure.
The Identity Architecture page has one additional layer: each step in the process can be linked to a specific experience available exclusively to WMMS Club members. The connection is set in the CMS — my code fetches the title and description of that experience and displays it as a hover toggle alongside the corresponding step. Everything updates dynamically as you scroll through the page, step by step.
Architecture First
The gallery and individual project pages are designed to put the architectural visuals first.
The layout is flexible — sections can be added or removed, specific specification fields can be hidden, all from the CMS.
Each project can look different depending on what there is to show, without touching the code.
Trust before the call
In the premium segment, the decision to hire an architect rarely happens after seeing one project. The client needs to trust the person, not just the portfolio. This part of the site does two things: builds the brand's history through a timeline of key moments, and shows the scale of experience through a map.
WMMS has an extensive database of completed projects — not just the ones selected for the portfolio, but years of work across different locations. They wanted to show that on a map. Existing map solutions had two problems: limited control over appearance, and complicated data management.
I built a custom solution using the Google Maps API with data pulled directly from Google Sheets. Every client knows Sheets — it requires no onboarding or training. The database has columns for project name, description, location, and image URL. The images are hosted on Webflow's hosting and were automatically matched to the correct rows in Sheets using AI, based on file names and project names — which saved manually mapping several dozen entries.
The map is styled in the brand's colours. I stripped out all cartographic elements that weren't relevant to showing the geographic reach of WMMS's work. The pin pop-ups contain exactly the data we planned to show, in a layout I designed from scratch — no compromises from an off-the-shelf plugin.
Mobile first and SEO
The responsive build follows a mobile-first methodology — the mobile version is the source of truth. Where possible, content and data are defined in the mobile version and inherited by desktop, not the other way around. That means content is edited once, not separately for each breakpoint.
It also matters for SEO. Search engines index the mobile version, so it needs to be complete and correctly structured. The site doesn't duplicate elements or content between versions — each breakpoint is considered on its own terms, but built so it doesn't create extra work when content is updated.
Working on something with similar scope?
I take on Webflow projects through agencies — get in touch and let's see if it's a fit.