Get in touch

WEB APPS& WEBSITES.

Freelance developer with 15 years of experience. I build web apps, interfaces and websites.

Portrait of Marc Mintel
01Hello

I am Marc.

I have been building for the web for 15 years: first in agencies, later as a senior developer, and now on my own.

My strength is the part people see and use: design and interface. I am also at home with what lies behind it, so I can build a complete application and not just its surface.

You work with me directly. Whether you run a product team or are commissioning something like this for the first time.

The path so far

  1. 2011Started in the webApprenticeship
  2. 2014 – 2020AgenciesFrontend developer
  3. 2020 – 2023Product companiesSenior software developer
  4. TodayIndependentWorking directly with clients
02Services

What do you need? Four typical cases.

An experienced developer who joins your project.

You have a product and more work than your team can handle. I work on agreed days of the week on what is next on your list: new features, the interface, or the parts nobody gets around to.

What you get

  • Web apps, dashboards, customer portals and internal tools
  • Interfaces with attention to design and usability
  • Web3 frontends: wallet connection, live data, dashboards
  • Small tools and automation for recurring work

How it runs

A first call, about 20 minutes1 / 4
YouMeabout 20 minutes

What it costs

By effort, for as long as your project runs

I work on your project on agreed days of the week and bill the hours I actually worked. There is no package to buy and no minimum term.

Per hour

100 EUR

net

Per day

800 EUR

8 hours, net

One invoice per month, with the tracked hours. Either side can end it with two weeks notice to the end of a month.

0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1Get in touch
03Process automation

Let the systems do the copying.

In most companies, people move information from one tool to another: read it here, type it in there, send an email about it. Automation connects those tools so that the work passes from one to the next on its own. Three typical examples:

A new order arrives in the shop. The invoice, the customer record and the confirmation follow without anyone typing.

Order to invoicerunning
ShopNew orderRuleIn stock?AccountingCreate invoiceCRMUpdate customerEmailSend confirmation

Log

  1. 01order received
  • Trigger: something happens
  • Rule: a fixed check
  • Action: a system does something

By hand

Someone opens the order, writes the invoice, updates the customer record and sends an email.

Automated

The order triggers everything. People only see the finished result.

Worth automating when

  • The same steps repeat every day or every week
  • Data is typed from one tool into another
  • Mistakes happen because the work is monotonous

What stays with people

  • Decisions and exceptions
  • Anything a customer should hear from a person
  • The final say when the automation is unsure

What I need from you

  • Access to the tools and their interfaces (APIs)
  • Someone who knows the process as it is done today
  • Real examples to test with
04Technology

Which projects I am right for.

A good fit

  • Web apps: dashboards, portals, internal tools
  • Interfaces where design and usability matter
  • Company websites, also in several languages
  • Web3 frontends: wallets, live data, dashboards
  • Automation: connecting systems and their APIs

Also possible

  • The backend an app needs: APIs, login, integrations
  • Command-line tools
  • Taking over and tidying up existing code

Not my field

  • Mobile apps for the app stores
  • Windows software
  • Running servers, specialised database work

What I work with

Interface

  • TypeScript
  • React
  • Next.js
  • Vue.js
  • Tailwind CSS

Behind it

  • Node.js
  • REST APIs
  • PostgreSQL
  • Headless CMS

Web3 and systems

  • Solidity
  • Rust

Delivery

  • Automated tests
  • Docker
  • CI/CD

What happens before a change goes live.

Software is connected: a change in one place can break another. I secure what I build with automated tests, and every change has to pass them before it is released. This is what such a run looks like.

Simulate a change in

  1. A change comes in

    Something is changed in Orders. Before it can go live, the whole project is checked automatically.

  2. A test fails, the release is blocked

    The change broke something in a different place. It is caught here, on my side, and nothing reaches your users.

  3. Fixed, checked again, released

    I repair what broke, the run passes, and only then does the change go live.

change/order-discounts → main
run #481
Lint
Types
Tests
Deploy

$ lint: checking the code style…

Tests 0 passed of 53release pending

An illustration with made-up file names and numbers, modelled on a real test run. Tests do not catch every mistake, but they do catch this kind.

05Working with me

How I work. Nothing unusual.

often: a request is passed alongYouSalesManagerDesignerDeveloperwith me: one direct lineYouMe

One contact

You talk to me, and I am the one who does the work.

Hours you can check

I track my time. The monthly invoice shows what the hours were spent on.

Careful work

I test what I build before I hand it over, and I say so when something is not finished or I am not sure.

What I build is yours

Code and design belong to you. You can hand them to another developer.

06My work

Two sites I built. Both are live.

klz-cables.com
klz-cables.com on a desktop screen
klz-cables.com on a phone

01 · Cable supplier

klz-cables.com

The company website of a supplier of energy cables, in German and English.

  • Product catalogue with categories and detail pages
  • Datasheets generated from the product data
  • Content the client can edit in a CMS
  • Next.js
  • TypeScript
  • Headless CMS
  • Two languages
Open the live site
e-tib.com
e-tib.com on a desktop screen
e-tib.com on a phone

02 · Cable network construction

e-tib.com

The company website of a group in cable network construction, in German and English.

  • Pages for services, references, careers and events
  • The same content in two languages
  • Works on phone, tablet and desktop
  • Next.js
  • TypeScript
  • Headless CMS
  • Two languages
Open the live site

Besides client work I build my own software, among other things a system in Rust and Solidity that runs on seven blockchains.

07Questions

Good to know before we talk.

I am not technical. Is that a problem?

No. I explain what I am doing in plain language, and you can ask at any time. You do not need to read code.

How long am I committed?

Project work is billed by effort. Either side can end it with two weeks notice to the end of a month.

Who owns what you build?

You do. Code and design belong to you, and you can hand them to another developer.

Can you work with our existing team and code?

Yes. I worked in agencies and product teams for years, so joining an existing project is familiar to me.

How do I reach you?

By email or video call. I work remotely and am available during European business hours.

What do you not do?

Mobile apps for the app stores, Windows software and running your servers. If your project needs those, I say so in the first call.

LET'STALK.

Write me a few lines about what you need. We then arrange a short call.

hello [at] mintel [dot] me