I DESIGN AND BUILD

CUSTOM WEB

APPLICATIONS

Custom dashboards, internal tools and SaaS products designed around the way your team works. I handle the architecture, development and delivery myself.

icon
Services

Web application development built around your workflow

I build web applications for growing data and teams. Clear module boundaries, tests and documented data contracts make future changes easier to estimate, review and hand over.

Ready to build your dashboard? Get a price & timeline

Case

studies

Vue.js development services — Stelios Kitziris, senior Vue.js and Nuxt engineer
icon
ABOUT ME

Custom applications designed around real work: dashboards, internal tools and SaaS products

I am a Full Stack Engineer. I map messy workflows and turn them into web applications with explicit data, roles and business rules. One person owns the architecture, implementation and handover: the person you talk to is the person writing the code.

0

Years of

Web Development

0+

Years building
web applications

0+

Web Apps
Delivered

0+

Legacy Migrations
Completed

icon
How it works

My 4-step web application process

Step 01

Technical audit

I read through your legacy code and Excel formulas, look at the current infrastructure, and map the migration path before anything else.
Step 02

Architecture & design

Then I design the database schema, API contracts and component structure the new application will be built on.
Step 03

Development & build

I build the frontend and backend in reviewable milestones, with tests running as the code grows.
Step 04

Deployment & warranty

I deploy the app, migrate your data and document the handover. Ongoing support can be scoped separately after launch.
icon
Frequently asked questions

Planning a web application? Start with these questions

The questions I get asked most, answered properly.

I have an old Excel file. Can you really turn it into a web app?

Many business-critical workbooks can become web apps, but not every Excel feature maps directly. I inventory the formulas, macros, links and add-ins first. The result can give several people controlled access to the same records, without passing versioned files around.

Yes. I move older frontends to a supported release in stages. I review the framework and its dependency chain first, then document the migration risk before changing production code.

Audit first, always. I map the codebase and tell you what the work actually costs before anyone commits to it. Then architecture, then the build with testing as it goes, then deployment. You talk to me directly the whole way, not to an account manager.

I specialize in Vue 3 and Nuxt on the frontend, with Node.js or Laravel on the backend. I choose the stack around the application, its data and the team that will maintain it.

icon
Social Proof

Who trusts me

icon
From the blog

Insights from The Frontend

Technical writing about web application architecture and modernizing legacy frontends. Opinions included.