A small studio, built around one belief: a website is infrastructure, not decoration.

I spent eleven and a half years in revenue cycle management and healthcare operations, starting as a medical coder, later mentoring RCM teams and working in Tier-3 operations. Before that, customer service, hospitality and store operations.

Most of that time went on one underlying problem: a process that should be simple has become complicated. Disconnected tools, manual steps, work redone because information sits in the wrong place. You learn to look for the root cause rather than the symptom, and to write down how something actually works before trying to fix it.

When I started working with reporting, automation and web development, Power BI, Make.com, n8n, Notion and WordPress, I kept seeing the same pattern in how businesses present themselves online. A website gets treated as a visual asset, when it should be doing a job: explaining the business clearly, earning trust, and making the next step obvious.

That is why Sylntra exists. I build websites around how a business actually works and grows, with the longer-term intention of connecting them to the systems behind them.

The part I enjoy most is taking something complicated and making it simpler: understanding how it works, finding what is creating friction, and turning it into something clearer and more useful.

These are the skills the operations work built, and they are the reason I approach a website differently to most designers.

If a visitor has to work out what you do, the design has failed regardless of how it looks.

Structure and message are signed off before design begins.

Fixed structure, clear deliverables, defined revision rounds.

Component-based builds, so next year’s landing page does not need a rebuild.

You talk to the person doing the work, for the whole project.

I never show clients, results or testimonials I do not have.

Published so you know exactly what is real today and what is being built. Nothing below is available until it says so.