Back to all projects
Live production websites — designed and built, and still in service.
Chatwee is a chat widget websites embed on their own pages — software sold to two audiences at once: the site owner deciding whether to buy, and the developer who has to install it. I designed and built the English-language marketing site across both, working inside a flat illustration style the client had already chosen, and shipped it as React with hand-written CSS.
The site is still live today, years after I left the project.
Chatwee is a chat widget websites embed on their own pages — software sold to two audiences at once: the site owner deciding whether to buy, and the developer who has to install it. I designed and built the English-language marketing site across both, working inside a flat illustration style the client had already chosen, and shipped it as React with hand-written CSS.
The site is still live today, years after I left the project.
A website has to keep working. Not on launch day, when everything is fresh and the content is exactly what it was designed for — but three years later, after the company has added pages, changed its pitch, entered new markets and grown past whatever size it was at the start. Most sites don't survive that. They get patched until the patches stop fitting, and then they get replaced.
These projects are the other kind. Both are live production sites for real companies, built years ago and still in service — one for a SaaS product that has since grown tenfold on the frontend I wrote, one for a law firm running in five languages including a right-to-left build. Neither has been rebuilt.
These short loops work well as:
A website is the one asset a company fully owns. Social accounts, marketplaces and ad platforms all lend you an audience on their terms — a site is where a business explains itself in its own words, to anyone who searches for it, at any hour, in whatever language its customers speak. For most companies it's the first thing a stranger checks before deciding whether to take them seriously.
And it does work no one is available to do. It answers questions before a sales call, qualifies people before they reach a form, and reaches audiences a small team could never handle in person.
Design and build in one place. I design the site and write the frontend myself — React, or hand-written HTML and CSS where a framework would be overkill. No handoff where intent gets reinterpreted, no layouts that turn out to be impractical once the code starts, no second contractor to brief and manage.
Decisions made with the build in view. Knowing what a layout costs to code — and what it costs to extend two years later — leads to different choices than designing in isolation. Components that repeat instead of thirty one-off sections. Structure that holds when the content doubles.
Sites that work everywhere. Responsive layouts tested across browsers and devices in BrowserStack, including right-to-left builds where a mirrored layout breaks differently in every rendering engine.
Everything it takes to actually go live. Domain, hosting, on-page SEO, share previews. A site that isn't published is a folder of files.
