Case study · AI + SaaS Products
A portfolio the studio owns outright
AMDA Architects did not need a showy site. They needed one where the buildings carry the page, and that they own outright.
- Something showy, heavy with interface
- Built so changes route back through the agency
- Clients notice the site, not the work
- Client
- AMDA Architects
- Problem
- A portfolio risked showing off its own interface instead of the work.
- Approach
- Strip the interface back until the projects carry the page, then hand it over.
The problem
AMDA Architects came to Stallwart for a portfolio site. The default a studio is usually offered is something showy, heavy with interface, and built so that future changes route back through the agency that made it.
That serves the agency more than the studio. The work is architecture, so the real question was whether the site could get out of its own way and let the buildings carry the page.
What was assumed
A portfolio should look impressive.
What Stallwart asked
What if the work, not the interface, carried the page?
What Stallwart built
Stallwart stripped the interface back until the projects carried the page, built it to be fast, and handed it over for AMDA to own outright, with no dependency on Stallwart to change it later. Clients open it and talk about the buildings, not the buttons.
- 01
Decide what the page is for
The page exists to show the work. Everything that competes with the architecture for attention is a candidate to remove, starting from that.
- 02
Strip the interface back
Remove interface until the projects carry the page on their own. What stays is what the work needs, not what makes the site look impressive.
- 03
Build it fast and hand it over
Deliver something fast that the studio owns outright, with no standing dependency on Stallwart to make a change later.
The approach
Less interface, so the work carries the page.
What most agencies push
- Something showy, heavy with interface
- Built so changes route back through the agency
- Clients notice the site, not the work
What Stallwart handed over
- Interface stripped back until the projects carry the page
- Fast, and owned outright
- Clients open it and talk about the buildings
Engineering decisions
Less interface, not more
On a portfolio, interface competes with the work. Removing it lets the buildings carry the page.
The trade-off
A restrained site looks less busy than a showy one, which is the intent, not a shortfall.
Hand over full ownership
A studio should not depend on its agency to change its own site. Ownership is the deliverable, not a retainer.
The trade-off
No standing contract to lean on, by design. The studio can change the site itself.
Fast over elaborate
A portfolio that loads fast respects the visitor and keeps attention on the work.
The trade-off
Fewer heavy effects, which is what keeps it fast and out of the work's way.
In practice
Ambrose Dass
Founder & Principal Architect, AMDA Architects
AMDA Architects' founder described Stallwart stripping the interface back until the projects carried the page, delivering something fast that the studio owns outright, and walking away rather than leaving him dependent on the agency to make changes. Clients now open the site and talk about the buildings, not the buttons.
This work connects to
- AI + SaaS Products
- Portfolio and web
- Full ownership
Frequently asked
What makes a good architecture portfolio website?
One where the work carries the page. For an architecture studio that means a fast, minimal site with the interface stripped back, so visitors look at the buildings rather than the site's own design.
Why strip the interface back instead of adding features?
Because on a portfolio the interface competes with the work for attention. Removing it lets the projects carry the page, which is what a visitor came to see.
What does owning the site outright mean?
AMDA Architects can change the site themselves, with no standing dependency on Stallwart. Ownership was the deliverable, not a retainer, so the studio is not tied to its agency to make an update.
Does a minimal site mean a plain one?
No. Minimal here means the interface gets out of the way so the architecture carries the page. The result is restrained by intent, with the work, not the buttons, drawing the eye.
Want a site clients look through, not at?
We strip the interface back until the work carries the page, then hand it over yours.
Last updated: October 8, 2026