The site that wins the enquiry — fast, findable, and written to convert rather than to decorate.
A marketing site earns its keep in two moments: when someone searches for what you do, and in the thirty seconds after they land. Everything else is decoration. So the work goes into speed, structure and clarity — not into effects that delay the first paint.
Built as static pages wherever possible, so there is no server to fall over and nothing to patch on a Friday. You get a site you can hand to anyone.
Software with accounts, permissions and data — the kind people sign in to and use all day.
Once a product has users, roles and records, the hard part stops being the screens. It becomes who may see what, what happens when two people edit the same thing, and whether you can prove afterwards who changed it.
That is the part I build carefully: authentication that fails closed, permissions that are checked on the server rather than hidden in the interface, and an audit trail that exists before you need it.
The operational software your business actually runs on — payroll, attendance, scheduling, admissions.
Most businesses reach a point where the spreadsheet stops holding. Usually it is not the ordinary case that breaks it — it is the exceptions. The overnight shift. The missed punch. The loan instalment due this month. The half-day that is really a holiday.
This is the work I find most interesting, because it cannot be bought off the shelf: your rules are yours. I build the rules engine so it is configurable and can explain how it reached a result, which is what lets a disputed day be answered rather than argued.
Storefronts where the checkout is the thing that gets the attention it deserves.
An online shop is a web application with money in it, which raises the cost of every mistake. Stock that is wrong, a payment that half-completes, an order confirmation that never arrives — each of those is a refund and a lost customer.
So the work concentrates where the risk is: inventory that stays truthful, a checkout that behaves under a dropped connection, and order state that can be reconciled against the payment provider rather than trusted blindly.
What you get
- Product, variant and stock management
- Payment integration with webhook reconciliation, not just a redirect
- Order lifecycle with email confirmations at each stage
- A checkout tested on slow connections and small screens
- An admin your team can operate without training
For sites that already exist and are losing customers to a slow first load or a page nobody can find.
This one is diagnostic before it is constructive. I measure what is actually happening for real visitors — not a score from a lab run on a fast laptop — and report where the time is going and what it is costing you.
Then I fix it: images, fonts, render-blocking scripts, the redirect chains nobody knew were there. Where a rebuild would be cheaper than the fixes, I will tell you that instead of billing for the fixes.
What you get
- Core Web Vitals audit against field data
- Image, font and JavaScript payload reduction
- Technical SEO: canonicals, structured data, sitemap, redirect hygiene
- A written report you keep, whether or not I do the work
How engagements work
Every project starts with a conversation about what you are actually trying to fix — not a quote against a feature list. If what you need is smaller than what you asked for, I will say so.