Systemvelz

Available for freelance projects in the US

Websites that load fast,
built to convert

I help US businesses turn slow, dated websites into fast, mobile-first pages that move a visitor towards a booked call, a form or a sale — not just a nicer looking homepage.

Async-first communication Mobile-first by default Performance measured before launch

About

Reliable delivery,
no guesswork

Most of the work I do starts with the same complaint: the website is not bringing in enough business. Sometimes the page is too slow on a phone. Sometimes the enquiry button is buried three screens down. Sometimes there is no website at all — just a Facebook page and a phone number.

I work in writing and asynchronously, because it fits a different time zone and because it leaves a record you can check later. Every build starts mobile-first, with a page-weight and load-time target agreed before the first line of code: if a later change makes the page heavier for no gain, it does not go in.

You get plain-language updates at each milestone, working software early — something you can click on in week one, not month two — and no surprises at handover. The code and the domain stay yours.

Built around one outcome

Every page has a single job: get the enquiry. Structure, copy order and button placement all follow from that, not from a template.

Mobile-first, seriously

Most local US traffic is a phone on cellular data. That is the case I design and test against first — desktop is the easy part.

Performance with a budget

A page-weight and load-time target is agreed up front and measured before launch. Speed is a requirement, not a nice-to-have to fix later.

Ownership stays with you

No lock-in and no proprietary builder. You own the domain, the hosting account and the code, and you can hand it to any developer later.

Services

Three things
I do well

I would rather do three things properly than twenty adequately. If your project is outside these three, I will say so and point you elsewhere.

High-converting landing pages

One page, one goal, built for paid traffic and local search. Fast on a phone, with the enquiry path visible without scrolling and a form that works even when the visitor is in a hurry.

  • Structure — headline, proof and call to action ordered for scanning, not reading
  • Speed — compressed images, no heavy third-party scripts, measured load time
  • Tracking-ready — clean placeholders for analytics and conversion events

Web systems & dashboards

Custom tools for work that is still running on paper, spreadsheets or WhatsApp messages: bookings, job tracking, internal approvals, simple client portals.

  • Built to your process — we map the flow first, then build it
  • Works on the phone — the people doing the work are rarely at a desk
  • Data you can export — your records stay yours, in a format you can open

Website redesign

For a site that still looks like 2014 and behaves like it. I keep what already works and earns traffic, and rebuild the parts that cost you visitors — starting with whatever is measurably broken.

  • Measure first — page weight, mobile layout and the visit-to-enquiry path
  • Nothing lost — existing URLs kept or redirected, so rankings survive
  • Faster and clearer — a rebuild you can see, on the same content

Work

Examples of the
work itself

The mockups below are original concept prototypes — the kind of layout, structure and enquiry path I build. They are labelled as concepts because that is what they are; client projects are added here only with permission, and never with a result I cannot point to.

Concept prototype

Emergency plumbing landing page

The problem: a single-location contractor buying local ads, sending that traffic to a homepage with a phone number in the footer. Mobile visitors were leaving before the number loaded.

What the build does: one page for one service, the number and the form above the fold, service areas and proof underneath, and a page weight small enough to open on a weak signal.

HTML CSS Vanilla JS Form to email

Before

After

Concept prototype

Contractor website redesign

The problem: eleven pages, none of them answering the visitor's actual question, and a mobile layout that scrolled sideways. The owner wanted to keep the content and lose the weight.

What the build does: keeps the pages that earn search traffic and redirects the rest, rebuilds the layout mobile-first, replaces the image sliders with static optimised images, and puts one clear call to action on every screen.

Redesign 301 redirects Responsive images Core Web Vitals
Concept prototype

Job tracking dashboard

The problem: a small service team tracking jobs across a whiteboard, a spreadsheet and a group chat. Nobody could answer "what is still open today?" without asking three people.

What the build does: one screen that answers that question — jobs by status, assigned to whom, what is overdue — and works on the phone of the person standing in a driveway.

Web system Roles & permissions Dashboard Data export
Concept prototype

Mobile-first booking flow

The problem: a salon taking bookings only by phone during opening hours — which is exactly when the staff are too busy to answer it.

What the build does: three taps from landing to a confirmed slot, no account required, with the available times loaded from the business's real calendar rather than a static list.

Booking Mobile-first Notifications

Tech stack

Tools I use,
and why

No percentages, no skill bars. A bar that says "96%" measures nothing. What matters is which tool fits the job — so here is what I reach for, and what it is for.

Frontend

  • React — interfaces with real state
  • Next.js — sites that need routing or SEO-heavy pages
  • Tailwind CSS — consistent styling at speed
  • TypeScript — fewer bugs in anything that grows
  • Plain HTML & CSS — for landing pages, the fastest option there is

Backend & data

  • Node.js — APIs and server-side logic
  • PHP — when the hosting is shared and it is the right tool
  • REST APIs — connecting the site to the systems you already use
  • Databases — your records, stored once and exportable

Platform & tooling

  • Hostinger — shared hosting, where most local businesses live
  • Hetzner — dedicated servers when a project outgrows shared hosting
  • Cloudflare — DNS, CDN and protection in front of the site
  • Harness — DeepSeek, Claude Code and Codex, with a review on every change
  • Vercel — edge deploys for React and Next.js projects
  • Git — every change tracked and reversible
  • Lighthouse & PageSpeed — measuring before claiming
  • DNS, SSL, e-mail delivery — the unglamorous parts that break quietly

Process

How we work
together

Four steps, in writing, so you always know where the project stands without needing a meeting to find out.

1

Scope, in writing

A short conversation about the goal, then a written scope: what is being built, what it costs and what "done" means. No surprises later.

2

Something clickable, early

You see a working version quickly — a real page on a real URL, not a picture of one. Feedback at this stage is cheap; feedback at the end is not.

3

Build and measure

I build it mobile-first, then measure: page weight, load time, layout at every screen width, and the path from visit to enquiry.

4

Launch and handover

The site goes live on your domain and hosting, and you get the code, the accounts and a plain-language summary of how it all fits together.

Questions I get asked

How do we work together across time zones?
Mostly in writing. You get a short update at every milestone — what is done, what is next and what is blocked. When a call is genuinely useful, we book it inside a window that overlaps your business hours.
What do you need from me to start?
Three things: the goal of the page or system, two or three examples of sites you like, and access to your brand assets and domain. If you do not have brand assets yet, that is not a blocker — we work with a simple type and colour system and refine it later.
How long does a project take?
Timelines are agreed per project, after a short scoping conversation. I do not quote a number before I understand the scope, because a date invented on day one is a date I would have to break later.
Can you work on my existing website?
Yes. Redesigns are a large part of what I do. I start by measuring what is actually slow or broken — page weight, mobile layout, the path from visit to enquiry — and fix the parts that change the outcome first.
What happens after launch?
The site is yours. I stay available for fixes and small changes, and we agree the terms up front in writing rather than leaving it implied.

Contact

Tell me what
is not working

Open for freelance projects in the US. Describe the problem in a few lines — what the site should be doing and what it does instead — and I will reply with an honest read on whether I am the right person for it.

Send a message

Direct is fine too

If a form feels like too much, write to me directly. A sentence about the problem and a link to the current site is enough to start.