Client work
How client websites led me to internal tools
I started with websites: pages, forms, content, revisions, and launches. Working with small businesses made me notice that the harder problems often started after the form was submitted.
The work behind the website
Leads need to be tracked, jobs need to move through a process, and someone needs a clear view of what is happening. That pushed me toward dashboards, CRM workflows, and the backend systems that keep those tools useful.
World of Doors is the clearest example in my current work. The public site needs service pages, local proof, and simple contact paths. Behind it, the business still needs a reliable way to follow leads and day-to-day work.
Why I separate the surfaces
The public site and the internal workflow serve different people and should not be treated as one large interface. Keeping them separate makes the public experience easier to use and keeps private operational details private.
Where I am going
I am still building web projects, but I am spending more time on data, APIs, Rust, and systems fundamentals. The client work gives me real problems to connect those skills to.