Occasional writing on design, automation, and running systems that don’t fall over. Written by the studio, from the studio’s own builds.
Where systems meet: why we build the front and the back together
July 2026 · Alp Şişman
Most websites are built as if the site is the product. It isn’t. The site is the visible edge of a system — behind it sit inboxes, reservation books, catalogues, spreadsheets, and the people who keep them moving. When a studio designs only the edge, the seams show up later: the contact form that emails an inbox nobody watches, the menu PDF that’s three updates behind, the “we’ll reply within 24 hours” promise that depends entirely on whether someone remembered to check.
Seam exists because we kept seeing the same failure from the other side. A manufacturer we work with received requests for quotes by email — multilingual, multi-message threads, some with spreadsheets attached. The website was fine. The system behind it was a person, reading every thread, cross-referencing a catalogue of six hundred items by hand. The bottleneck was never the design; it was the machinery the design was politely hiding.
So the studio’s rule is: design the interface and the workflow as one thing. When we build a hospitality site, the reservation flow, the review replies and the guest messages are part of the brief. When we build for a factory, the quote pipeline is part of the brief. The visible layer and the automation underneath ship together, tested together, owned by one accountable pair of hands.
The name is the thesis. A seam is where two panels are stitched into one piece of work — if it’s done well, you barely see it; if it’s done badly, it’s the first thing that tears.
Draft-first AI: automation with a human approval gate
July 2026 · Alp Şişman
Every automation we ship follows the same pattern: trigger → reason → draft → human gate. The system reads the input, does the thinking, produces a complete draft — and then stops. A person approves before anything leaves the building in the business’s name.
This isn’t caution for its own sake. In our quoting system, Quotewright, the hard rule is that the machine never invents a price. Every number in a draft quote is a real catalogue value; anything uncatalogued is named, flagged, and routed to the sales team. When we validated it against the manufacturer’s real historical quotes, it reproduced them to the cent — and when a test deliberately pushed it to fabricate a surcharge, it refused. That refusal is the feature.
The same gate runs through Misafir, our hospitality concierge. It drafts replies to reviews and guest messages in the guest’s own language, but nothing posts without sign-off. A restaurant’s voice is its reputation; the owner keeps the send button.
What surprised us is that the gate doesn’t slow things down — it speeds them up. Approving a good draft takes seconds. Writing from scratch takes minutes and gets skipped on busy days. The human stops being the bottleneck and becomes the editor, which is where human judgment actually earns its keep.
If you’re automating anything customer-facing, our advice is simple: let the machine do the reading, the matching and the writing — and keep a person on the send button until the system has earned otherwise, line by line.