Chapter 03

The right tools.
Not the trendy ones.

I choose tools for the job, the budget, and the people who will maintain the result. Here is what I use most, and why.

Start a conversation

What I use most.

Grouped by the job each one does.

Design and everyday work

Where pages and brands take shape, and where the planning happens.

  • Figma
  • VS Code
  • Google Workspace
  • ChatGPT

Websites and stores

Fast sites and editors your team can use.

  • Astro
  • Next.js
  • WordPress
  • Shopify
  • Nuxt

Interfaces

The code behind what people click and read.

  • React
  • Vue
  • Svelte
  • Angular
  • TypeScript
  • JavaScript
  • Tailwind CSS

Apps and data

Accounts, databases, and the logic apps run on.

  • Node.js
  • Python
  • PHP
  • Laravel
  • Django
  • FastAPI
  • PostgreSQL
  • MongoDB
  • Redis
  • Supabase

Hosting and delivery

Where the work lives, and how it ships.

  • Vercel
  • Cloudflare
  • Docker
  • GitHub

How I choose.

Four questions decide the stack for every project.

  1. Does it fit the job?

    A five-page site does not need the same stack as a marketplace. Simpler is better when it does the job.

  2. Does it fit the budget?

    Hosting and licenses are part of the cost, now and every year after, so I keep them sensible.

  3. Does it fit the people?

    If your team will edit the site, the editor matters more than the framework behind it.

  4. Will it stay yours?

    Every account is set up in your name, and the tools are widely used, so you can change providers or developers later.

Common questions.

Short answers about tools i use.

Ask me directly
Can you work with the platform I already have?

Usually, yes. WordPress, Shopify, and most modern frameworks are familiar ground.

Will I be locked in to your tools?

No. The code and accounts are yours, and the tools are widely used, so any capable developer can pick them up.

Good work starts with a conversation.

Tell us about your business, what’s working, and what you’d like to do better.