maiierik.com
You are looking at the case study.
A portfolio that only shows work is a brochure. If I claim to build booking systems and CRMs, the site making that claim should be running on one.
The brief
Two constraints. First: no embedded third-party widget may stand between a visitor and me — whoever owns the booking flow owns the relationship. Second: it must not look like every other portfolio generated this year. The default aesthetic of the moment is instantly recognisable and instantly forgettable.
The build
Next.js App Router with Framer Motion, EN and TR served from a single dictionary so no page can drift out of sync with its translation. An in-house booking system instead of a Calendly embed. A lead CRM with status transitions and internal notes, capturing the landing page and UTM parameters on every submission, so a message is not just a message but a traceable source. Admin sits behind auth. Visually it is an industrial terminal — a deliberate rejection of the soft-gradient default look.
The payoff
Every inbound message lands in a pipeline I own, attributed to where it came from. No third-party service decides what happens to a lead, and no monthly subscription holds my client list. The proof is the page you are reading — including this wall of screens.
The scoreboard
- In-house booking replaces the third-party embed
- Leads captured with page and UTM attribution into an owned CRM
- EN/TR from one dictionary — no duplicated, drifting pages
Want a story like this on your side?
Two lines about your problem is enough to start.