Problem
A motion-design studio is judged on how its work looks the moment it loads. The studio needed a portfolio that did the reels justice, fast, clean, and built to be theirs, not a rented template on someone else's account that they would have to migrate later.
Approach
A build-then-handoff engagement. I designed and built the site to show the motion work at full quality, then handed over the whole thing: code, hosting, the lot. No lock-in, no monthly tether to me. The client owns their infrastructure outright and can run, extend, or hand it to another team without asking permission.
Outcome
Delivered and live as the studio's public portfolio. The client fully owns the infrastructure. This is the clean version of a project engagement: build it well, hand it over, leave the client independent. Not every engagement should turn into a retainer, and this one was right to end at handoff.
Notes
What I delivered
A public portfolio site for a motion-design studio, built so the work loads fast and looks the way the work actually is. Then I handed it over in full: the client owns the code and the hosting.
This is build-then-handoff done cleanly. Some engagements are a moment, not a relationship. This was one of them, and that was the right call.
What's next
Nothing from me, by design. The client runs it. If you want a site built well and then handed to you, no lock-in and no monthly tether, that is a shape I am happy to work in. Reach out.